Igor Pechtchanski wrote:
On Thu, 29 Apr 2004, Buchbinder, Barry (NIH/NIAID) wrote:
-Original Message-
From: Andrew DeFaria
Sent: Thursday, April 29, 2004 1:18 PM
To: cygwinatcygwindotcom
Subject: Re: Line breaks in bash
When I type a long line in the bash shell it seems to get
When I type a long line in the bash shell it seems to get confused when
it passes the first 80 character barrier and does a newline. Below is an
example.
C09-272-A:# why is it in bash that when I get close to typing 80
characters bash
does som
ething like this?
Now set my prompt to the
.)
-Original Message-
From: Andrew DeFaria
Sent: Thursday, April 29, 2004 1:18 PM
To: [EMAIL PROTECTED]
Subject: Re: Line breaks in bash
When I type a long line in the bash shell it seems to get confused when
it passes the first 80 character barrier and does a newline. Below is an
example.
C09-272
On Thu, 29 Apr 2004, Buchbinder, Barry (NIH/NIAID) wrote:
-Original Message-
From: Andrew DeFaria
Sent: Thursday, April 29, 2004 1:18 PM
To: cygwinatcygwindotcom
Subject: Re: Line breaks in bash
When I type a long line in the bash shell it seems to get confused when
I get the behaviour even if I comment out all the complex PS1 definitions in
/etc/profile. To see it, open a bash (windows console, I don't know about rxvt)
and resize it to be larger than the 80x25 (mode.com con lines=50 cols=120).
Then type away (at a prompt) and see that the text will wrap at
Which OS? Win9x console is pretty much braindead. Cygwin's programs
(notably bash) have code for processing a SIGWINCH, which they should
receive whenever a window (console or otherwise) that they're running in
gets resized. However, the code for sending this signal will only detect
a *window*
It was XP in my case. The stty -a followed by a kill -WINCH my-bash-pid works
(even with a mode.com based resize). Thanks for the insight. I hope the
original poster gets something out of this too.
On Fri, Apr 23, 2004 at 11:13:05AM -0400, Igor Pechtchanski wrote:
Which OS? Win9x console is
From: Ashok Vadekar
Sent: Friday, April 23, 2004 5:13 PM
It was XP in my case. The stty -a followed by a kill -WINCH
my-bash-pid works (even with a mode.com based resize).
Thanks for the insight. I hope the original poster gets
something out of this too.
Trying to add some more
When I type a long line in the bash shell it seems to get confused when
it passes the first 80 character barrier and does a newline. Below is an
example.
C09-272-A:# why is it in bash that when I get close to typing 80
characters bash
does som
ething like this?
Now set my prompt to the
At 06:34 PM 4/22/2004, you wrote:
When I type a long line in the bash shell it seems to get confused when it passes the
first 80 character barrier and does a newline. Below is an example.
C09-272-A:# why is it in bash that when I get close to typing 80 characters bash
does som
ething like this?
--- Andrew DeFaria wrote:
When I type a long line in the bash shell it seems to get confused when
it passes the first 80 character barrier and does a newline. Below is an
example.
C09-272-A:# why is it in bash that when I get close to typing 80
characters bash
does som
ething like
11 matches
Mail list logo