On Mon, Jun 29, 2015 at 09:28:11AM +0300, Pierre Gaston wrote:
> On Mon, Jun 29, 2015 at 5:54 AM, Braden Best wrote:
> > I noticed it when I tried to branch an xterm off into multiple sessions
> > and mistyped its name:
> >
> > `xter m&`
I'm assuming the backticks are NOT actually part of the com
On 6/26/15 5:42 PM, Klaus Ziegler - owner of sunfreeware.de wrote:
> Bash Version: 4.3
> Patch Level: 39
> Release Status: release
>
> Description:
> Bash 4.3.39 does not compile due to wrong signal.h handling i sig.h
Where does Irix 6.5 define SIG_DFL and what is its definition?
--
``
On 6/27/15 3:48 PM, Nathan Neulinger wrote:
> Bash Version: 4.3
> Patch Level: 39
> Release Status: release
>
> Description:
>
> If $() includes a case statement nested within it, the parser is
> not matching ) as closing the case,
> but rather the $(. This behavior is different
Configuration Information:
Machine: x86_64
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='x86_64-unknown-cygwin'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -
Forwarding to the mailing list:
On Mon, Jun 29, 2015 at 02:28:32PM -0600, Braden Best wrote:
> Yes, the back tick is a quoting mechanism I picked up from stack exchange.
> In those sites, it highlights the text and renders it in a fixed width font.
>
> cnf handle is : command not found
>
> Also,
Reply to the mailing list, and supply the information we requested
(the *exact output* of "type command_not_found_handle", and Pierce's
suggestion to try to duplicate the problem with command_not_found_handle
unset).
On Mon, Jun 29, 2015 at 03:04:03PM -0600, Braden Best wrote:
> Here's the same sc
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' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'
Using LC_ALL=C here is just like hiding your head in the dirt and pretending
nothing is wrong. If the tests break with non-C locales, it means that bash
doesn't compile correctly under that system, and that's worth investigating.
--
Eduardo Bustamante
https://dualbus.me/
On 6/29/15 7:44 PM, Eduardo A. Bustamante López wrote:
> Using LC_ALL=C here is just like hiding your head in the dirt and pretending
> nothing is wrong. If the tests break with non-C locales, it means that bash
> doesn't compile correctly under that system, and that's worth investigating.
That't
On 6/29/15 3:41 PM, Patrick Plagwitz wrote:
> Bash Version: 4.3
> Patch Level: 39
> Release Status: release
>
> Description:
> There's a bug that happens when waiting for a child process to complete
> (via wait_for in jobs.c) that isn't part of a job, like command
> substitution subshells. If a S
On Mon, Jun 29, 2015 at 07:49:24PM -0400, Chet Ramey wrote:
> That't not what he's saying. He's saying -- correctly -- that different
> locales produce different localized error messages (e.g., "command not
> found") and that produces output. The majority of those tests can set
> LC_ALL=C without
11 matches
Mail list logo