On Mon, Dec 15, 2014 at 1:48 PM, konsolebox konsole...@gmail.com wrote:
Last thing is `declare -x $a_complete_assignment` should not be allowed;
even quoted assignments like `declare -x $one=$two` simply because
they are already a reinterpreted form i.e. they are already evaluated
with a pair
On Mon, Dec 15, 2014 at 4:34 AM, Chet Ramey chet.ra...@case.edu wrote:
It does implement `emulated behavior of normal assignments'. The question
is whether or not it should do that after having had its arguments undergo
one round of word expansion.
After studying the code I realized that
Hello,
I found a bug in bash that results in executing unfinished command when
TTY is closed.
Example: I ssh to remote machine, and start typing a command, lets say I
need to remove files that ends with .log, so I type 'rm *', and before I
can add '.log', my network drops. When that
Hi,
I'm doing research on code reviews and static analysis tools at the SERG group
(http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of
Technology. Currently, we want to give an overview of the usage of code review
and static analysis tools in open source projects.
On 12/17/14, 8:34 AM, Jiri Kukacka wrote:
I understand that this is due to handling EOF from closed TTY as \n, thus
executing the command, and this is standard behavior of readline, but I
think the problem is quite serious, so I have to fix it, and I hope that
you would like this to have
Advance apologies if I'm misunderstanding, but the described bug looks like
reasonable behavior to me.
When a ssh connection drops, which side notices and when depends on the I/O
being done on either side, the state of any keepalive settings, and the
timeouts involved. If there's a long time
On Wed, Dec 17, 2014 at 03:16:53PM -0500, Steve Simmons wrote:
Advance apologies if I'm misunderstanding, but the described bug looks like
reasonable behavior to me.
It would be more reasonable for bash (or ssh, I'm not sure at what level
this handling should occur) to discard the partially
On Dec 17, 2014, at 3:23 PM, Greg Wooledge wool...@eeg.ccf.org wrote:
On Wed, Dec 17, 2014 at 03:16:53PM -0500, Steve Simmons wrote:
Advance apologies if I'm misunderstanding, but the described bug looks like
reasonable behavior to me.
It would be more reasonable for bash (or ssh, I'm not
Hi there,
has this bug already been solved?
http://unix.stackexchange.com/questions/22435/how-to-fix-character-encoding-in-bash-arch-linux
On this version (Debian wheezy), the problem still occurs and is annoying:
GNU bash, Version 4.2.37(1)-release (x86_64-pc-linux-gnu)
Best regards,
Did you test against the current development version?
I'm not seeing that in 4.3:
dualbus@hp ~ % bash --version
GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
10 matches
Mail list logo