Re: small fix for lib/sh/snprintf.c

On 4/13/12 9:57 AM, Petr Sumbera wrote: > On 04/13/12 03:18 PM, Petr Sumbera wrote: > >> Problem 2: >> == >> >> bash -c 'printf "x%+010.0fx\n" 123' >> x00+123x >> >> where it should be: >> x+00123x >> >> Fixed in chunk #3 (but the problem is there also for other types!). > > My fi

Re: Input line of a terminal is messed and broken

On 4/15/12 9:21 AM, "유병석(Byeongseok Yu)" wrote: > Bash Version: 4.2 > Patch Level: 24 > Release Status: release > > Description: > Input line is messed and broken. > > Repeat-By: > 1. $export PS1=\e[34;40m[\u@\h \w]\e[m > 2. #cd subfolders successively until PS1 echoes go over the half portion >

Re: how are aliases exported?

Pierre Gaston wrote: 2) non-interactive bash Aliases are off by default. So given that you need to run something at the beginning of your new bash instance anyway, you could define your aliases in a function together with the mandatory shopt, eg: function start_aliases { shopt -s exp

Re: how are aliases exported?

Pierre Gaston wrote: On Sat, Apr 14, 2012 at 8:31 AM, Pierre Gaston > wrote: On Sat, Apr 14, 2012 at 3:44 AM, Linda Walsh mailto:b...@tlinx.org>> wrote: Dennis Williamson wrote: Aliases are intended for command line convenience.

Re: inconsistency with "readonly" and scope

Andreas Schwab wrote: Maarten Billemont writes: On 15 Apr 2012, at 03:21, Chet Ramey wrote: If I declare a variable readonly at global scope, I wouldn't expect it to be overridden by some local namespace pollution. I think that's fine; in the local context, your variable has a different m

Input line of a terminal is messed and broken

Configuration Information [Automatically generated, do not change]: Machine: i386 OS: darwin11.3.0 Compiler: /usr/bin/clang Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='darwin11.3.0' -DCONF_MACHTYPE='i386-apple-darwin11.3.0' -DCONF_VENDOR='apple' -DLOCALEDIR='/opt/loca

Re: inconsistency with "readonly" and scope

Maarten Billemont writes: > On 15 Apr 2012, at 03:21, Chet Ramey wrote: >> >> If I declare a variable readonly at global scope, I wouldn't expect it >> to be overridden by some local namespace pollution. > > I think that's fine; in the local context, your variable has a > different meaning; it's

Re: inconsistency with "readonly" and scope

On 15 Apr 2012, at 03:21, Chet Ramey wrote: > > If I declare a variable readonly at global scope, I wouldn't expect it > to be overridden by some local namespace pollution. I think that's fine; in the local context, your variable has a different meaning; it's another variable with the same name.