Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-18 Thread burning shadow
Works ok, thanks. ;) On 2/18/08, Kostya Altukhov <[EMAIL PROTECTED]> wrote: > On Feb 17, 2008 11:48 PM, burning shadow wrote: > > > Ok, less doesn't work when TERM set to "putty". > > OK, here's another solution: > > 1) use TERM=xterm > 2)

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-17 Thread burning shadow
Ok, less doesn't work when TERM set to "putty". On Feb 16, 2008 3:30 AM, burning shadow <[EMAIL PROTECTED]> wrote: > Looks like it works. ;) But I still wonder why my irssi build worked > fine with cygwin as TERM.. > > On 2/16/08, Kostya Altukhov <[EMAIL PRO

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-16 Thread burning shadow
Sat, Feb 16, 2008 at 11:05 AM, burning shadow > <[EMAIL PROTECTED]> wrote: > > Ok, this gonna be an offtopic, but how to make numpad keys work in vim > > when TERM set to xterm? It works perfect when TERM is cygwin. > > > -- > Unsubscribe info: http:

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-16 Thread burning shadow
Ok, this gonna be an offtopic, but how to make numpad keys work in vim when TERM set to xterm? It works perfect when TERM is cygwin. On 2/16/08, Brian Dessent <[EMAIL PROTECTED]> wrote: > burning shadow wrote: > > > Nope. Everything works fine only when TERM set to c

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-15 Thread burning shadow
: I checked it with TERM set to xterm and glitch gone, but I still hope to see a real fix. On 2/16/08, Václav Haisman <[EMAIL PROTECTED]> wrote: > burning shadow wrote, On 16.2.2008 2:08: > > > I'm running it in PuTTY via SSH connection. TERM set to "cygwin". Ye

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-15 Thread burning shadow
I'm running it in PuTTY via SSH connection. TERM set to "cygwin". Yes, first 2 or maybe 3 lines. All packages are up to date. And I have never seen that with my own compiled irssi. I have made screenshots of my own compiled irssi and irssi from package windows right after startup: http://home.sha

Re: [ANNOUNCEMENT] New package: irssi-0.8.12-1

2008-02-15 Thread burning shadow
Thanks! Finally irssi got into cygwin distribution. :) I though have noticed some glitches when irssi starts: Irssi: Looking up irc.mimi.net.ru 2 2:33 -!- IIrssi: Connecting to irc.mimi.net.ru [82.146.61.3] port 6667 22:33 -!-

Re: [ANNOUNCEMENT] New package: screen-4.0.3-1

2007-07-12 Thread burning shadow
I too want to say BIG THANKS for this release. I waited for SCREEN from the first day I installed cygwin. :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: outdated setup.ini on all mirrors

2007-06-21 Thread burning shadow
to be up to date. Setup.ini timestamp is 1182409206. My own public mirror pulls straight from sourceware.org daily so it shouldn't of been out of date. On 6/21/07, burning shadow <[EMAIL PROTECTED]> wrote: > What happened to all the mirrors? All have outdated setup.ini. I have &g

outdated setup.ini on all mirrors

2007-06-21 Thread burning shadow
What happened to all the mirrors? All have outdated setup.ini. I have more recent distributions from last update. Now after downloading setup.ini installer sais that it is older than ini from last install. I tried mirrors.kernel.org, ftp.chg.ru, ftp.easynet.be and many other mirrors and all of the

problems with bash and latest readline

2007-01-17 Thread burning shadow
After installing latest readline I have problems in bash. I have PS1 set to '\[\e]0;[EMAIL PROTECTED]:[EMAIL PROTECTED]:\w\$ ' and this gives me prompt with 1 extra space. If I change PS1 to '\[\e]0;[EMAIL PROTECTED]:[EMAIL PROTECTED]:\w\$', I get 2 '$' signs in prompt: '[EMAIL PROTECTED]:~$$'.

Re: ssh asks for key passphrase every time

2006-12-21 Thread burning shadow
Thank you very much. You were right. :) On 12/20/06, Robert McKay <[EMAIL PROTECTED]> wrote: On 12/20/06, burning shadow <[EMAIL PROTECTED]> wrote: > I have created identification key with passphrase (id_dsa). Now every > time I try to open ssh connection to any host, ssh a

ssh asks for key passphrase every time

2006-12-20 Thread burning shadow
I have created identification key with passphrase (id_dsa). Now every time I try to open ssh connection to any host, ssh asks for passphrase for this key. I believed, ssh should ask for a passphrase only if host wants to accept key. FreeBSD's ssh, for example, does it this way. -- Unsubscribe inf

Re: "Connection closed by [host]" when ssh to Cygwin sshd

2006-11-30 Thread burning shadow
Uninstall sshd service using `cygrunsrvd -R sshd` then install it using ssh-host-config and allow script to create sshd_server user when it will ask for it. It will help. On 12/1/06, Brian Kasper <[EMAIL PROTECTED]> wrote: I am *still* having problems getting ssh and sshd to work under WinXP 200

Re: Screen 4.0.2 for cygwin

2006-09-07 Thread burning shadow
Thanks a lot! On 9/7/06, Loic Grenie <[EMAIL PROTECTED]> wrote: If anybody is interested, screen-4.0.2 compiles without too much trouble. Get the source from four favorite gnu mirror, apply the followin short patch and screen is yours. -- Unsubscribe info: http://cygwin.com/ml/#u

Re: bash processes after ssh session disconnection

2006-09-06 Thread burning shadow
I figured out this happens only if something was run from bash. For example, irssi. If disconnection occured when there was only bash active, it does not become but stays forever with flag 'I' in processes. On 8/30/06, burning shadow <[EMAIL PROTECTED]> wrote: Since cygwin1.dl

RE: bash processes after ssh session disconnection

2006-09-04 Thread burning shadow
Is there a chance this issue will be solved? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/

bash processes after ssh session disconnection

2006-08-30 Thread burning shadow
Since cygwin1.dll version 1.5.20 I get bash processes became sometimes after SSH session disconnects. For example, today there was a network problem and my SSH session got broken, after I reconnected, there was 1 process. Sometimes this does not happen. All components I am using are updated to l

ping ignores ^C when host is not responding

2006-07-12 Thread burning shadow
I cannot interrupt ping when host is not responding. I have to kill it from another session. If host is responding, I can interrupt ping with ^C. Look: [EMAIL PROTECTED]:~$ which ping /usr/bin/ping [EMAIL PROTECTED]:~$ cygcheck ping Found: D:\tools\cygwin\bin\ping.exe D:/tools/cygwin/bin/ping.ex

RE: bash 3.x path completion problems

2006-07-10 Thread burning shadow
I figured out it happens only with colored command prompt. Probably, I have some errors in ansi codes, I tried different variants, here are some of them: PS1='\[\033]0;\w\007\033[32m\]\u\[\033[0m\]:\[\033[33m\]\w\[\033[0m\]\$ ' PS1='\[\033[32m\]\u\[\033[0m\]:\[\033[33m\]\w\[\033[0m\]\$ ' If I re

Re: ps -a does not show wget running in background

2006-07-10 Thread burning shadow
Yes, you were right. It wasn't a cygwin binary. It's a mystery to me how could it get there. I had cygwin wget package installed, and reinstall placed the right binary there. Like cgf, I can't reproduce. It looks like the wget binary D:\tools\cygwin\bin\wget.exe is not a Cygwin binary, despite

ps -a does not show wget running in background

2006-07-10 Thread burning shadow
This is a slightly corrected report with more info included. :) shadow:~/dl$ wget -b 'http://openoffice.bouncer.osuosl.org/?product=OpenOffice.org&os=win&lang=en&version=2.0.3' Continuing in background, pid 568. Output will be written to `wget-log'. shadow:~/dl$ ps -a PIDPPIDPGID

ps ux does not show wget running in background

2006-07-09 Thread burning shadow
shadow:~/dl$ wget -b 'http://openoffice.bouncer.osuosl.org/?product=OpenOffice.org&os=win&lang=en&version=2.0.3' Continuing in background, pid 348. Output will be written to `wget-log'. shadow:~/dl$ ps ux PIDPPIDPGID WINPID TTY UIDSTIME COMMAND 138015121380

Re: bash 3.x path completion problems

2006-05-30 Thread burning shadow
Like I said, it's unlikely that this is the thing that makes the difference, but you could always have a quick try with the latest snapshot just in case: http://cygwin.com/snapshots. It might also be trying the different cygwin terminals, xterm and rxvt as well as plain old dos console. Oh,

Re: bash 3.x path completion problems

2006-05-30 Thread burning shadow
Since version 3, bash has had problems with readline causing spurious 'ghost' characters to echo to the screen, particularly when scrolling through the history buffer or using a prompt with non-printing chars in it. It may affect completion too. Is there any solution? The real question

bash 3.x path completion problems

2006-05-30 Thread burning shadow
Since version 3 bash has problems with path completion. For example, here's directory listing: shadow:~/tmp$ ls -la total 1 drwxr-xr-x+ 4 shadow None 0 May 30 20:41 . drwxr-xr-x+ 10 shadow root 0 May 29 20:34 .. drwxr-xr-x+ 8 shadow None 0 Apr 26 22:16 games drwxr-xr-x+ 5 shadow None 0

cygwin-1.dll long-time bug

2006-04-18 Thread burning shadow
There is a bug in all cygwin processes which leads to 100% CPU usage and locking another processes. For example, there was a windows update (installed automatically using Automatic Updates) from Microsoft, which couldn't be installed until all cygwin processes are stopped. It happens with some util