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 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
On Dec 9, 2014, at 9:47 AM, Stephane Chazelas stephane.chaze...@gmail.com
wrote:
It's a bit confusing that ${VAR:-} should be treated
differently from ${VAR:=}. Was there a rationale for changing
the behaviour other than strict POSIX conformance? AFAICT, ksh
and mksh behave differently
On Dec 2, 2014, at 4:24 AM, bijay pant bijaypa...@gmail.com wrote:
From: root
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu'
On Nov 23, 2014, at 2:08 PM, Chet Ramey chet.ra...@case.edu wrote:
On 11/23/14 5:54 AM, Xie Yuheng wrote:
we should add .bash/ along with .bashrc as the default init dir.
this will make things more flexible, and will not break any existed code.
to be default is important, people who right
On Nov 6, 2014, at 10:14 AM, Ian Jackson ijack...@chiark.greenend.org.uk
wrote:
Chet Ramey writes (Re: Shellshock-vulnerable version still most obvious on
ftp.gnu.org):
On 11/6/14, 7:47 AM, Ian Jackson wrote:
But in the current environment it's looking rather quaint. We could
probably
On Oct 15, 2014, at 9:38 AM, lorenz.bucher@rohde-schwarz.com wrote:
Hello,
in refer to
http://lists.gnu.org/archive/html/bug-bash/2014-09/msg00278.html variables
with suffix %% can't be set/exported.
This makes problems restoring environments which where saved by external
programs
On Oct 9, 2014, at 9:34 PM, TODD TRIMMER todd.trim...@gmail.com wrote:
If I compile from bash-4.2 from source, cumulatively applying patches through
52, things work fine. If I start from scratch and apply through 53, it errors
out:
gcc -L.. . .
./builtins/libbuiltins.a(evalstring.o): In
On Sep 27, 2014, at 2:19 AM, Eric Blake ebl...@redhat.com wrote:
The prefix is nice for quick identification, but what is ESSENTIAL is
something that puts shell functions in a namespace that is untouchable
by normal shell variables (the () suffix in Florian's patch). If all
you do is add a
On Sep 27, 2014, at 6:51 PM, Eric Blake ebl...@redhat.com wrote:
On 09/27/2014 04:21 PM, Chet Ramey wrote:
2) build a 'real' /bin/sh without those compiled in. This begs the
definition of 'real', but IMHO if it's not in POSIX, it shouldn't be in
'real' /bin/sh
This is dash's niche.
On Sep 25, 2014, at 2:47 PM, lolilolicon loliloli...@gmail.com wrote:
On Fri, Sep 26, 2014 at 2:28 AM, Ángel González an...@16bits.net wrote:
[...]
On the other hand, this approach would be much more interesting if bash
delayed parsing of exported functions until they are used (ie. check
On Sep 25, 2014, at 5:42 PM, Alexandre FERRIEUX - SOFT/LAN
alexandre.ferri...@orange.com wrote:
On 25/09/2014 22:51, Eric Blake wrote:
On 09/25/2014 08:48 AM, Alexandre Ferrieux wrote:
Is the response (workarounds and patch) being discussed elsewhere ?
Thanks. Like thousands of people I
On Sep 24, 2014, at 4:06 PM, lolilolicon loliloli...@gmail.com wrote:
On Thu, Sep 25, 2014 at 3:53 AM, Greg Wooledge wool...@eeg.ccf.org wrote:
So, if Chet removes the feature, it would probably break something that
someone cares about. Maybe there could be a compile-time option to
On Sep 10, 2014, at 4:58 AM, Vincent Lefevre vinc...@vinc17.net wrote:
In error messages, raw non-printable characters from arguments should
not be output without transformation, at least if this is on a terminal.
If stderr has been redirected, this is more a matter of choice.
An example:
On Aug 28, 2014, at 12:37 PM, Chris Down ch...@chrisdown.name wrote:
I really don't understand -- why is this unexpected? It's exactly what I'd
expect to happen if you try to do something like that. It should not be
disallowed to source yourself, that prevents people from doing things when
On Aug 12, 2014, at 4:36 PM, Chet Ramey chet.ra...@case.edu wrote:
On 8/9/14, 7:07 AM, Steve Simmons wrote:
It would be nice to have ganged file test switches. As an example, to test
that a directory exists and is properly accessible one could do
if [[ -d foo ]] [[ -r foo ]] [[ -x
On Aug 13, 2014, at 2:31 PM, Ken Irving ken.irv...@alaska.edu wrote:
I like the idea, but switch negation would need to be supported, and
I don't think that's been covered sufficiently. Using ! as a switch
modifier might be possible, and I like it, but would then also apply to
single
Advance apologies if this has already been discussed and rejected.
It would be nice to have ganged file test switches. As an example, to test that
a directory exists and is properly accessible one could do
if [[ -d foo ]] [[ -r foo ]] [[ -x foo ]] ; then . . .
but
if [[ -drx foo ]] ;
On Aug 9, 2014, at 11:16 AM, Andreas Schwab sch...@linux-m68k.org wrote:
Steve Simmons s...@umich.edu writes:
Advance apologies if this has already been discussed and rejected.
It would be nice to have ganged file test switches. As an example, to test
that a directory exists
19 matches
Mail list logo
