$ alias u=uname
$ >&2 a=b u
Linux
$ >&2 u
Linux
$ a=b >&2 u
No command u found, did you mean:
...
In all three cases `u' is in a position where a command name may appear,
and should be subjected to alias substitution.
This is reproducible on devel too
--
Oğuz
Greg Wooledge writes:
> Partly true. seq(1) is a Linux thing, and was never part of any
> tradition, until Linux people started doing it.
Huh. I started with Ultrix, and then SunOS, but don't remember learning
seq at a later date.
> (Before POSIX, it involved using expr(1) for every increment,
On 3/22/21 9:38 PM, Dale R. Worley wrote:
> Greg Wooledge writes:
>> Now, the big question is WHY you thought something which is not correct.
>>
>> The most common reasons that people think something which is wrong are:
>
> In my experience, a common reason is that the documentation does not
> co
Greg Wooledge writes:
> Now, the big question is WHY you thought something which is not correct.
>
> The most common reasons that people think something which is wrong are:
In my experience, a common reason is that the documentation does not
concentrate in one place that users are certain to read
On 3/16/21 8:04 AM, Michael Felt wrote:
Decided to give bash-5.1 a try. I doubt it is major, but I get as far as:
"../../../src/bash-5.1.0/lib/sh/tmpfile.c", line 289.11: 1506-068 (W)
Operation between types "char*" and "int" is not allowed.
ld: 0711-317 ERROR: Undefined symbol: .mkdtemp
l
On 3/22/21 10:43 AM, Ilkka Virta wrote:
The lowercase 'ignoreeof' variable appears to act as a sort of a synonym to
the uppercase 'IGNOREEOF'. Both seem to call into 'sv_ignoreeof', and the
latter one set takes effect. I can't see the lowercase one documented
anywhere, is this on purpose?
It ex
The lowercase 'ignoreeof' variable appears to act as a sort of a synonym to
the uppercase 'IGNOREEOF'. Both seem to call into 'sv_ignoreeof', and the
latter one set takes effect. I can't see the lowercase one documented
anywhere, is this on purpose?
On 3/22/21, Greg Wooledge wrote:
> On Mon, Mar 22, 2021 at 09:50:06AM +, Budi wrote:
>> in a function k() in ~/.bashrc
>>
>> k(){ unset u;h=0; o=(${h:+ ! -path "./*.txt"}) ;u=($u "${o[@]}"); c=(.
>> -regextype posix-extended "${b[@]}" -print); find "${c[@]}"
>> }
>>
>> in output set -x:
>>
>
On 3/20/21 3:15 PM, Michael Felt wrote:
Scraping through this - thanks for the lessons aka explanations.
On 18/03/2021 16:08, Chet Ramey wrote:
On 3/18/21 5:53 AM, Michael Felt wrote:
Yes, something to test. Thx. The ojdk scenario is: /usr/bin/printf >
>(tee -a stdout.log) 2> >(tee -a stderr.
On Mon, Mar 22, 2021 at 09:50:06AM +, Budi wrote:
> in a function k() in ~/.bashrc
>
> k(){ unset u;h=0; o=(${h:+ ! -path "./*.txt"}) ;u=($u "${o[@]}"); c=(.
> -regextype posix-extended "${b[@]}" -print); find "${c[@]}"
> }
>
> in output set -x:
>
> + unset u
> + h-0
This is clearly a fal
The conditional variable not work in function in a script ie ~/.bashrc
while works in shell term.
$ unset u;h=0; o=(${h:+ ! -path "./*.txt"}) ;u=($u "${o[@]}"); c=(.
-regextype posix-extended "${b[@]}" -print); find "${c[@]}"
or type
$ k(){ unset u;h=0; o=(${h:+ ! -path "./*.txt"}) ;u=($u "${o[@
im sorry to not be able to reply to all your stuffs
you didnt make it easy
im happy it works for me now
On Mon, Mar 22, 2021 at 3:43 AM Greg Wooledge wrote:
>
> On Mon, Mar 22, 2021 at 03:12:25AM +0100, Alex fxmbsw7 Ratchev wrote:
> > i realize its somewhat of a big limitation, to have only globa
12 matches
Mail list logo
