On Sat, Apr 14, 2012 at 8:31 AM, Pierre Gaston wrote:
>
>
> On Sat, Apr 14, 2012 at 3:44 AM, Linda Walsh wrote:
>
>>
>>
>> Dennis Williamson wrote:
>>
>> Aliases are intended for command line convenience. You should use
>>> functions, which can be exported and are the correct thing to use in
>>>
On Sat, Apr 14, 2012 at 3:44 AM, Linda Walsh wrote:
>
>
> Dennis Williamson wrote:
>
> Aliases are intended for command line convenience. You should use
>> functions, which can be exported and are the correct thing to use in
>> scripts (and even from the command line).
>>
>> "For almost every pu
On Sat, Apr 14, 2012 at 3:44 AM, Linda Walsh wrote:
>
>
> Dennis Williamson wrote:
>
> Aliases are intended for command line convenience. You should use
>> functions, which can be exported and are the correct thing to use in
>> scripts (and even from the command line).
>>
>> "For almost every pu
Chet Ramey wrote:
This is intended. Bash doesn't allow a local copy of a variable to
override a readonly global one. This can be a potential security hole,
---
You can look at it that way, but it also hinders modular programming.
If I declare a variable to be local, I wouldn't expect it t
Dennis Williamson wrote:
Aliases are intended for command line convenience. You should use
functions, which can be exported and are the correct thing to use in
scripts (and even from the command line).
"For almost every purpose, shell functions are preferred over aliases."
But, of course, yo
Aliases are intended for command line convenience. You should use
functions, which can be exported and are the correct thing to use in
scripts (and even from the command line).
"For almost every purpose, shell functions are preferred over aliases."
But, of course, you know that already.
On Apr 1
How can I export an alias so it survives across an exec?
I thought there was a way for them to be exported like vars or functions...
but neither work.
I have a prog that needs an alias defined, if it isn't, it
execs a program to define the alias which re-execs the first --
if the alias isn'
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 fix breaks following case:
bash -c 'printf "x%+10.0fx\n" 123'
x+ 123
Your change is ok for my original test case. But I have realized that
there are several other problems. Please see attached new version of the
patch.
Problem 1:
==
bash -c 'printf "x%-010.0fx\n" 123'
x123000x
where it should be:
x123 x
Fixed in chunk #6.
Problem 2:
===
