* BUGS list
@ 1995-11-04 4:41 Geoff Wing
1995-11-05 2:43 ` Zoltan Hidvegi
0 siblings, 1 reply; 5+ messages in thread
From: Geoff Wing @ 1995-11-04 4:41 UTC (permalink / raw)
To: zsh-list
Heyla, how much of Etc/BUGS is still valid?
>From BUGS:
"single_line_zle does not go to the next line after return."
What machine is this on? Works fine for me.
"Only waste is stored in the variable given to read -k if there is a
character immediately avaible for reading. In this case that character
is not even removed from the input buffer. Try
% sleep 1 ; read -k ch
and press a key while it's sleeping then examine $ch."
What machine? What situations? Also works fine for me.
--
Mason [G.C.W] mason@werple.mira.net.au "Hurt...Agony...Pain...LOVE-IT"
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: BUGS list
1995-11-04 4:41 BUGS list Geoff Wing
@ 1995-11-05 2:43 ` Zoltan Hidvegi
1995-11-05 2:49 ` Richard Coleman
0 siblings, 1 reply; 5+ messages in thread
From: Zoltan Hidvegi @ 1995-11-05 2:43 UTC (permalink / raw)
To: zsh-workers
Geoff Wing wrote:
> >From BUGS:
> "single_line_zle does not go to the next line after return."
>
> What machine is this on? Works fine for me.
>
>
> "Only waste is stored in the variable given to read -k if there is a
> character immediately avaible for reading. In this case that character
> is not even removed from the input buffer. Try
> % sleep 1 ; read -k ch
> and press a key while it's sleeping then examine $ch."
>
> What machine? What situations? Also works fine for me.
These bugs are already fixed. I have posted several updates to the BUGS file
but they did not find their way to the distribution.
Bye,
Zoltan
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: BUGS list
1995-11-05 2:43 ` Zoltan Hidvegi
@ 1995-11-05 2:49 ` Richard Coleman
0 siblings, 0 replies; 5+ messages in thread
From: Richard Coleman @ 1995-11-05 2:49 UTC (permalink / raw)
To: Zoltan Hidvegi; +Cc: zsh-workers
> > What machine is this on? Works fine for me.
> >
> > "Only waste is stored in the variable given to read -k if there is a
> > character immediately avaible for reading. In this case that character
> > is not even removed from the input buffer. Try
> > % sleep 1 ; read -k ch
> > and press a key while it's sleeping then examine $ch."
> >
> > What machine? What situations? Also works fine for me.
>
> These bugs are already fixed. I have posted several updates to the BUGS file
> but they did not find their way to the distribution.
oops... sorry about that. I'll update it now. Sometimes it difficult
to keep all this straight.
rc
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bugs list
2001-06-11 18:38 ` Bugs list Andrej Borsenkow
@ 2001-06-12 9:24 ` Bart Schaefer
0 siblings, 0 replies; 5+ messages in thread
From: Bart Schaefer @ 2001-06-12 9:24 UTC (permalink / raw)
To: Andrej Borsenkow, zsh-workers
On Jun 11, 10:38pm, Andrej Borsenkow wrote:
} Subject: Bugs list
}
} Bart Schaefer wrote:
}
} > The known bugs in zsh are listed in the file Etc/BUGS.
Bart Schaefer quoted the README file, just so it's clear ...
} This one is gone AFAIK:
}
} When interrupting code like the following with ^C:
} while true; do
} sh -c '...'
} done
} if the `sh' is executing, zsh does not know that the sh received a ^C and
} continues with the next iteration.
It still happens for me on RH5.2 where /bin/sh is bash. The loop
while true; do
sh -c 'more /etc/termcap'
done
can only be interrupted if you happen to hit bash with the signal before
"more" gets started.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
^ permalink raw reply [flat|nested] 5+ messages in thread
* Bugs list
2001-06-11 16:53 Suggested PATCH: Reorder README a little Bart Schaefer
@ 2001-06-11 18:38 ` Andrej Borsenkow
2001-06-12 9:24 ` Bart Schaefer
0 siblings, 1 reply; 5+ messages in thread
From: Andrej Borsenkow @ 2001-06-11 18:38 UTC (permalink / raw)
To: zsh-workers
Bart Schaefer wrote:
> The known bugs in zsh are listed in the file Etc/BUGS.
This one is gone AFAIK:
When interrupting code like the following with ^C:
while true; do
sh -c '...'
done
if the `sh' is executing, zsh does not know that the sh received a ^C and
continues with the next iteration. This happens for any program which
handles the interrupt, then exits after tidying up; it does not happen for
zsh, which exits directly from the signal handler. The workaround is to
use ^Z which forks the shell and makes the loop a separate job, then kill
the suspended loop.
-andrej
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-06-12 9:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1995-11-04 4:41 BUGS list Geoff Wing
1995-11-05 2:43 ` Zoltan Hidvegi
1995-11-05 2:49 ` Richard Coleman
2001-06-11 16:53 Suggested PATCH: Reorder README a little Bart Schaefer
2001-06-11 18:38 ` Bugs list Andrej Borsenkow
2001-06-12 9:24 ` Bart Schaefer
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).