This message was cancelled from within Mozilla.
And for the same reason some people hardcode the dot or the comma as
thousands separator in their code, ignoring locale settings. "Never seen
something different."
what's the best?
hardcoding, improving efficiency, and putting another brick on the wall
of standardization..
...or i18n/TERM
Antonio Macchi wrote:
>>> commands like "ls --color" does not use terminfo capabilities...
>>
>>> ...use instead fixed strings (without regards about TERMinal)
>>> is this a good (and safe) choice too?
>>
>> IMHO not. Too many assumptions. GNU ls seems to always assume an ANSI
>> terminal, regardle
Chet Ramey wrote:
> HISTFILESIZE doesn't exist until bash tries to load the history
> list from the history file (taken from $HISTFILE). At that point,
> if it doesn't have a value, it's set to $HISTSIZE. That doesn't
> happen until after the startup files are read, as you guessed.
>
> If you w
Hi,
The autocd option is a long awaited bash feature.
Unfortunately I dislike the noisy impementation
which prints every time "cd ".
Due to the fact that autocd is off by default
everyone who actives the option should know what s/he
is doing and does not need a nanny.
If it is not accecptable
Eric Blake wrote:
> The portability bug I am referring to is the use of double-quoted
> back-ticks containing a double quote. Some (buggy) shells require you to
> use \" instead of " inside backticks if the overall backtick expression is
> double-quoted.
Hence this statement in Posix:
Eithe
> Actually, what I want is to prevent writing to the history file
> at all when bash exits. (Not all the time, just in certain cases
> that other logic in .bashrc will be able to detect. Unsetting
> HISTFILESIZE unconditionally was a simplified test case.)
>
> Should I unset HISTFILE, or set it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Angel Tsankov on 2/16/2009 2:26 AM:
>> There are some contexts, such as variable assignments, where double
>> quotes are not necessary.
>>
>> foo="`echo "a b"`"
>> bar=`echo "a b"`
>>
>> only the setting of bar is guaranteed to parse corre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Frysinger on 2/15/2009 9:44 PM:
>> ctime is the time when the inode was last modified, not (necessarily)
>> the time when the file was created.
>
> if op is worried about that, then there is no place where the exact creation
> time
Dave B wrote:
> Angel Tsankov wrote:
>> Eric, thanks for youy replay. If double quotes are not that
>> portable, then how am I suppose to assign the output from some
>> command to a variable when the output contains a space?
>
> Word splitting doesn't happen on assignments, so:
>
> $ var=$(echo "f
Angel Tsankov wrote:
> Eric Blake wrote:
>> According to Angel Tsankov on 2/15/2009 3:02 PM:
>>> I tried CPATH="${CPATH}${CPATH:+:}"~usr1/blah/blah. (I quote
>>> expansions just to be on the safe side, though I think home
>>> directories may not contain spaces.)
>> There are some contexts, such as
Eric Blake wrote:
> According to Angel Tsankov on 2/15/2009 3:02 PM:
>> I tried CPATH="${CPATH}${CPATH:+:}"~usr1/blah/blah. (I quote
>> expansions just to be on the safe side, though I think home
>> directories may not contain spaces.)
>
> There are some contexts, such as variable assignments, whe
12 matches
Mail list logo
