thank you sir dale, while i was cleaning up the code for another paste with
more details i came across that when i add a empty newline before the first
for, the bug line disappears
small conclusion: . code works, eval "$( < file )" worked, but alias
version not without empty newline
..
im sorry
Date:Mon, 16 Nov 2020 13:52:55 +0100
From:Alex fxmbsw7 Ratchev
Message-ID:
| small conclusion: . code works, eval "$( < file )" worked, but alias
| version not without empty newline
Dale's point, with which I agree, is that you shouldn't even be attempting
On Mon, Nov 16, 2020 at 08:37:05PM +0700, Robert Elz wrote:
> Dale's point, with which I agree, is that you shouldn't even be attempting
> using aliases for things like that. If there is some bug there, I don't
> care, and I doubt anyone else does either.
If a bug can actually be pinpointed and
Date:Mon, 16 Nov 2020 08:49:21 -0500
From:Greg Wooledge
Message-ID: <20201116134921.gn...@eeg.ccf.org>
| If a bug can actually be pinpointed and demonstrated,
| I'm sure Chet would care.
Chet might. I don't. I doubt many others do.
| It's too convoluted.
On Mon, Nov 16, 2020 at 9:38 PM Robert Elz wrote:
>
> Personally I'd go further and suggest that no-one should ever use aliases
> for anything, ever ...
>
I don't understand why people "hate" aliases so much. :) For me it's much
simpler/shorter than functions. And the "alias" command (without
I must say, having increasingly elaborate forms of variable substitution
to do things like this seems like poor design. I would favor
constructions like
$ BAZ=$( <<<$FOO some_program args )
Although I must say, I can't recall off the top of my head what Un*x
utility best capitalizes the
On 2020/11/16 11:02, Alex fxmbsw7 Ratchev wrote:
on my way for a new paste
Anytime you start going over multiple lines in an alias, you
need to consider the use of a function, where 'need' would ideally
increase in proportion to the number of lines you are including.
For increased readability,
you instruct the subshell to set -e, ..
On Fri, Nov 13, 2020, 17:16 Aron Griffis wrote:
> GNU bash, version 5.0.17(1)-release (x86_64-redhat-linux-gnu)
>
> $ (set -e; false; echo BANG) || echo whimper
> BANG
>
> $ (set -e; false; echo BANG); echo whimper
> whimper
>
> The || after the subshell
on my way for a new paste, i came over more such unexpected ';' token
errors, yet i seemed for workaround\compatibility to work around em by not
using ; at all, also on end of final done cause that error would appear
im still working on making my code acceptable
On Sat, Nov 14, 2020, 20:29 Alex
