Re: Strange-Dangerous behaviour in Cygwin (and/or RXVT)

> I have tried your code "stty erase ^H" in .bash_profile and as I thinked > it works for standard bash shell and xterm BUT NOT for RXVT in which, now, > BKSPACE is dead. In others words RXVT wants "stty erase ^?" as in > /etc/profile. The trick is to set `stty erase' to whatever your current shel

Re: Strange-Dangerous behaviour in Cygwin (and/or RXVT)

On 5/14/2005 6:13 AM, Angelo Graziosi wrote: I have tried your code "stty erase ^H" in .bash_profile and as I thinked it works for standard bash shell and xterm BUT NOT for RXVT in which, now, BKSPACE is dead. In others words RXVT wants "stty erase ^?" as in /etc/profile. WFM with rxvt and xterm, b

Re: Strange-Dangerous behaviour in Cygwin (and/or RXVT)

I have tried your code "stty erase ^H" in .bash_profile and as I thinked it works for standard bash shell and xterm BUT NOT for RXVT in which, now, BKSPACE is dead. In others words RXVT wants "stty erase ^?" as in /etc/profile. I have tried also the code (

Re: Strange-Dangerous behaviour in Cygwin

I have never touched /etc/profile which is a copy of /etc/defaults/etc/profile dated Dec 7 20:53 and I think it belongs to 3.2-1 version of base-file which is dated Dec 7 19:52 (I upgrade Cygwin continuously). I want to underline that until some weeks ago the problems with BKSPACE were absent.

Re: Strange-Dangerous behaviour in Cygwin

On Fri, 13 May 2005, Eric Blake wrote: > According to Angelo Graziosi on 5/12/2005 5:20 PM: > > Summarizing I want to know if the problems I described > > > > are bugs of some Cygwin packages (should I wait for new upgrades?) > > If you don't mind the wait, you can wait for the upgrade of base-f

Re: Strange-Dangerous behaviour in Cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Angelo Graziosi on 5/12/2005 5:20 PM: > Summarizing I want to know if the problems I described > > are bugs of some Cygwin packages (should I wait for new upgrades?) If you don't mind the wait, you can wait for the upgrade of base-file

Re: Strange-Dangerous behaviour in Cygwin

Eric, can you answer to this mail ? Summarizing I want to know if the problems I described are bugs of some Cygwin packages (should I wait for new upgrades?) or are the normal behaviour of Cygwin, so that if I do not like them I shou

Strangerous behavior in Cygwin (was: RE: Strange-Dangerous behaviour in Cygwin)

[snip] Sorry, I just felt I needed make the obvious contraction in the subject line there. -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ:

Re: Strange-Dangerous behaviour in Cygwin

On Wed, 11 May 2005, Christopher Faylor wrote: > On Wed, May 11, 2005 at 02:47:42AM -0400, Igor Pechtchanski wrote: > >On Tue, 10 May 2005, Christopher Faylor wrote: > > > >> On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote: > >> >Now my question - why can't cygwin have sane defaults for

Re: Strange-Dangerous behaviour in Cygwin

On Wed, May 11, 2005 at 02:47:42AM -0400, Igor Pechtchanski wrote: >On Tue, 10 May 2005, Christopher Faylor wrote: > >> On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote: >> >Now my question - why can't cygwin have sane defaults for the tty, so that >> >this question doesn't continue to po

Re: Strange-Dangerous behaviour in Cygwin

On Tue, 10 May 2005, Christopher Faylor wrote: > On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote: > >Now my question - why can't cygwin have sane defaults for the tty, so that > >this question doesn't continue to pop up? > > Because we hate everyone and want them to suffer? Hmm, BWHEAW

Re: Strange-Dangerous behaviour in Cygwin

I have not changed anything in configuration (I have not "touched" any thing in " /etc/profile " etc.) Until some days ago all worked fine. With some upgrades or i do not know "what" the BACKSPACE does not work correctly in answering at command like rm -i: it works as a LEFT arrow key. This happ

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

On May 10 18:53, John Morrison wrote: > On Tue, May 10, 2005 6:25 pm, Corinna Vinschen said: > > Can we stop this discussion and just do it right in /etc/profile by > > just not setting it? > > Humm, sorry I've just started reading this thread, does the > /etc/skel/.inputrc have any (appologies fo

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

On Tue, May 10, 2005 6:25 pm, Corinna Vinschen said: > On May 10 11:18, Warren Young wrote: >> Corinna Vinschen wrote: >> >> >Can anybody tell me what the `stty erase' setting is good for in >> >/etc/profile? I'm using tcsh, so I'm not bothered by this stuff... >> >> This is fine as long are you'r

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

On May 10 11:18, Warren Young wrote: > Corinna Vinschen wrote: > > >Can anybody tell me what the `stty erase' setting is good for in > >/etc/profile? I'm using tcsh, so I'm not bothered by this stuff... > > This is fine as long are you're within your shell, or another program > that is tolerant

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

Corinna Vinschen wrote: Can anybody tell me what the `stty erase' setting is good for in /etc/profile? I'm using tcsh, so I'm not bothered by this stuff... This is fine as long are you're within your shell, or another program that is tolerant of the two different ways of saying 'backspace'. If y

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

> I get ^H in a cmd window, an rxvt window, and an xterm window. > Hmm, it's been more than 1.5 years since I got cygwin working how I like it, so I don't remember exactly what I did, but these lines in /etc/profile are helpful: # Consistent BackSpace and Delete Configuration: # http://www.i

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[responding to no one in particular] On Cygwin when you hit Backspace you get a ^H. Cygwin has been doing this for many years and it is duly recorded in terminfo and termcap that way. Changing this would require updating terminfo and termcap not just on cygwin but on every system which has a cygw

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

On May 10 15:47, Eric Blake wrote: > /etc/profile (actually etc/defaults/etc/profile) needs to be updated like so, > to match the current default behavior of the cygwin terminal settings: > > --- /etc/defaults/etc/profile.orig 2005-03-25 08:50:00.003125000 -0700 > +++ /etc/defaults/etc/profi

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

On 5/10/2005 8:47 AM, Eric Blake wrote: I think I may have a culprit. When I run bash in a cmd window: $ [ctrl-v][backspace] ^H $ echo $TERM cygwin When I run it in an rxvt or xterm window: $ [ctrl-v][backspace] ^? $ echo $TERM xterm I get ^H in a cmd window, an rxvt window, and an xterm window. -

RE: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

> > Actually, it would be nicer if $TERM of cygwin could treat [backspace] as > > ^? [0x255] (ASCII delete) > > > ITYM 0x7f [/me blushes] yep - thanks for spotting my typo -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin

RE: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

Original Message >From: Eric Blake >Sent: 10 May 2005 16:47 > Actually, it would be nicer if $TERM of cygwin could treat [backspace] as > ^? [0x255] (ASCII delete) ITYM 0x7f cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygw

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

> > Now my question - why can't cygwin have sane defaults for the tty, so that > > this question doesn't continue to pop up? > > What's a sane setting? When I open a standard bash console window, this > simply doesn't happen. Is $TERM set to "cygwin"? That's the default > setting and, as noted,

Re: Strange-Dangerous behaviour in Cygwin

On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote: >Now my question - why can't cygwin have sane defaults for the tty, so that >this question doesn't continue to pop up? Because we hate everyone and want them to suffer? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-sim

Re: Strange-Dangerous behaviour in Cygwin

On May 10 06:56, Eric Blake wrote: > According to Angelo Graziosi on 5/9/2005 1:50 PM: > > > > WHY an "xterm setup" if, as I wrote, the problems are present in standard > > bash shell, i.e. that launched with cygwin.bat. > > Chris apologized for misreading your email and misleading this > convers

Re: Strange-Dangerous behaviour in Cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Angelo Graziosi on 5/9/2005 1:50 PM: > > WHY an "xterm setup" if, as I wrote, the problems are present in standard > bash shell, i.e. that launched with cygwin.bat. Chris apologized for misreading your email and misleading this conversat

Re: Strange-Dangerous behaviour in Cygwin

>On Sun, 8 May 2005 18:52:58 -0400, Christopher Faylor wrote: >>On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: >>The problems described prviously exist in standard bash shell (that is >>launched with the link on Desktop) and in the shell launched by xterm >>(with startxwin.bat)

Re: Strange-Dangerous behaviour in Cygwin

On Mon, May 09, 2005 at 10:17:34AM +0100, Dave Korn wrote: >Original Message >>From: Christopher Faylor >>Sent: 08 May 2005 23:53 > >> On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: >>> The problems described prviously exist in standard bash shell (that is >>> launched wit

Re: Strange-Dangerous behaviour in Cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Carlo Florendo on 5/8/2005 9:30 PM: > Ooops. Sorry, I've read earlier discussions on this issue just a few > seconds ago by Erik Blake et al. So, it's not an xterm issue. It's a I spell it Eric. > bug with coreu

RE: Strange-Dangerous behaviour in Cygwin

Original Message >From: Christopher Faylor >Sent: 08 May 2005 23:53 > On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: >> The problems described prviously exist in standard bash shell (that is >> launched with the link on Desktop) > Again: This means that IT IS an xterm

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

On Mon, May 09, 2005 at 12:06:11AM -0400, Christopher Faylor wrote: >On Mon, May 09, 2005 at 11:44:53AM +0800, Carlo Florendo wrote: >>Does this patch also fix the issue of arrow keys wrongly being enabled >>like a text editor (e.g. during "rm -i ", a user can navigate >>through the screen.) > >T

RE: [Fwd: Strange-Dangerous behaviour in Cygwin]

Yo.. Keen! > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Christopher Faylor > Sent: Monday, 9 May 2005 2:06 PM > To: cygwin@cygwin.com > Cc: Paul Eggert > Subject: Re: [Fwd: Strange-Dangerous behaviour in Cygwin] > >

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

On Mon, May 09, 2005 at 11:44:53AM +0800, Carlo Florendo wrote: >Does this patch also fix the issue of arrow keys wrongly being enabled >like a text editor (e.g. during "rm -i ", a user can navigate >through the screen.) This is not a bug in coreutils. You can get the same behavior in windows b

Re: Strange-Dangerous behaviour in Cygwin

reply and thought that it was the same problem that I was having. I hope this helps... josé - Original Message - From: "Carlo Florendo" <[EMAIL PROTECTED]> To: ; Sent: Sunday, May 08, 2005 11:14 PM Subject: Re: Strange-Dangerous behaviour in Cygwin Christopher Faylor wr

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

Paul Eggert wrote: Jim Meyering <[EMAIL PROTECTED]> writes: Alternative opinions (or patches to yesno.c) welcome. In the POSIX locale we don't have any choice; we have to accept any answer with a leading "y" as "yes". See: http://www.opengroup.org/onlinepubs/95399/basedefs/xbd_chap07.h

Re: Strange-Dangerous behaviour in Cygwin

Carlo Florendo wrote: Christopher Faylor wrote: On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: The problems described prviously exist in standard bash shell (that is launched with the link on Desktop) and in the shell launched by xterm (with startxwin.bat). THEY DO NOT exist in

Re: Strange-Dangerous behaviour in Cygwin

Christopher Faylor wrote: On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: The problems described prviously exist in standard bash shell (that is launched with the link on Desktop) and in the shell launched by xterm (with startxwin.bat). THEY DO NOT exist in dos box (with C\:cygw

Re: Strange-Dangerous behaviour in Cygwin

On Sun, May 08, 2005 at 03:02:17PM +0200, Angelo Graziosi wrote: >The problems described prviously exist in standard bash shell (that is >launched with the link on Desktop) and in the shell launched by xterm >(with startxwin.bat). > >THEY DO NOT exist in dos box (with C\:cygwin\bin in W2KSP4 path)

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

Jim Meyering <[EMAIL PROTECTED]> writes: > Alternative opinions (or patches to yesno.c) welcome. In the POSIX locale we don't have any choice; we have to accept any answer with a leading "y" as "yes". See: http://www.opengroup.org/onlinepubs/95399/basedefs/xbd_chap07.html#tag_07_03_06_01 C

Re: Strange-Dangerous behaviour in Cygwin

The problems described prviously exist in standard bash shell (that is launched with the link on Desktop) and in the shell launched by xterm (with startxwin.bat). THEY DO NOT exist in dos box (with C\:cygwin\bin in W2KSP4 path) and in the shell launched with RXVT: in these cases the BACKSPACE key

Re: Strange-Dangerous behaviour in Cygwin

I have not understand what I should to do. In any case, I am conforted that there is someone who oberve the some symptoms! I think that the problems arise from recent upgrades that now I cannot single out. It is as if something has changed in the configuration. The problems are not specific t

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

Eric Blake <[EMAIL PROTECTED]> wrote: > Relevant clips from this cygwin bug report. When tty settings are weird > (I'm not sure whether the bug is in cygwin, xterm, or just bad tty > settings that could be reproduced elsewhere), backspace only repositions > the cursor on screen, so that the actual

Re: Strange-Dangerous behaviour in Cygwin

You can us stty erase "^H" (or what ever might be appropriate for the terminal) to get this to work. I was able to observe the exact symptoms you reported and correct do the above. -- Mark Angelo Graziosi wrote: Not only in xterm but also in standard bash shell. I have always used xterm and unt

[Fwd: Strange-Dangerous behaviour in Cygwin]

---- Subject: Strange-Dangerous behaviour in Cygwin Date: Sat, 07 May 2005 17:52:10 +0200 (MET DST) From: Angelo Graziosi <[EMAIL PROTECTED]> To: cygwin@cygwin.com, [EMAIL PROTECTED] I discovered the following strange behaviour in bash and xterm (startxwin) shells: Suppose having alias r

Re: Strange-Dangerous behaviour in Cygwin

Not only in xterm but also in standard bash shell. I have always used xterm and until today I never have discovered those problems. What about the fact that when "rm" command (or cp or mv) ask to confirm something, I can move the (box) cursor along the window as in a Editor? Thanks angelo. O

Re: Strange-Dangerous behaviour in Cygwin

On Sat, May 07, 2005 at 05:52:10PM +0200, Angelo Graziosi wrote: >I discovered the following strange behaviour in bash and xterm (startxwin) >shells: > >BACKSPACE does not delete "y" as aspected but it only shifts the cursor on >"y" and when I type "n" and then RETURN the file foo.txt is REMOVED!

Strange-Dangerous behaviour in Cygwin

After upgrading some packages (tetex-3.0.0-3.tar.bz2, man-1.5p-1.tar.bz, doxygen-1.4.2_20050421-1.tar.bz2, yesterday 06 May 2005 and subversion-1.1.4-1.tar.bz2, subversion-devel-1.1.4-1.tar.bz2, _update-info-dir-00232-1.tar.bz2, tzcode-2005h-1.tar.bz2, xemacs-21.4.17-1.tar.bz2, xemacs-tags, xem