RE: SIGINT to bash behaves differently in rxvt as compared to console

2003-01-22 Thread duncan . loveday
Igor, Cheers - but I just tried that and it didn't have any effect. That variable is not set by default in either the console or rxvt. Bummer. Duncan. -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]] Sent: 21 January 2003 19:25 To: Loveday,DAH,Duncan,YEE24 R Cc:

RE: SIGINT to bash behaves differently in rxvt as compared to console

2003-01-22 Thread duncan . loveday
David, Yes - I did try that just now and still no effect. The key question iswhy does it behave differently in rxvt ? It's as if rxvt launches bash with some different settings. Duncan. -Original Message- From: David Starks-Browning [mailto:[EMAIL PROTECTED]] Sent: 22 January 2003

RE: SIGINT to bash behaves differently in rxvt as compared to console

2003-01-22 Thread duncan . loveday
Igor, I run rxvt from a .bat file :- @echo off D: chdir \cygwin\bin rem set CYGWIN=tty rem set TERM=cygwin D:\cygwin\bin\rxvt -ls -fg green -bg black -cr red -sl 1000 -sr -fn 'Lucida Console-20' -e bash --login -i ...and no matter what I do I can't make the ^C do what I want ! I'm more or

SIGINT to bash behaves differently in rxvt as compared to console

2003-01-21 Thread duncan . loveday
I find on a Windows NT4 (SP6) platform with the latest versions (downloaded today) of cygwin1.dll, rxvt, bash etc that if I run a windows command script, say a.cmd, which in turn runs some other process (e.g. a pause), if I hit ^C then the behaviour is different in rxvt as compared to the cygwin