> Errexit (a.k.a. set -e) is horrible,
> and you should not be using it in any new shell scripts you write.
> It exists solely for support of legacy scripts.
Wow. For those of us who don't know this, what should we be using instead? Is
using a trap on ERR any better? Is your suggestion that || ex
[I am terribly sorry that my In-Reply-To is wrong :/]
- "Eric Blake" wrote:
> ... Remember, the security hole of
> Shell Shock is NOT what the function is named, but the fact that
> arbitrary variable contents were being parsed. ...
Not quite: the point of exploit can be in the variable nam
- "Ángel González" wrote:
> The patch seems straightforward:
>
> diff --git a/variables.c b/variables.c
> index 92a5a10..6552e69 100644
> --- a/variables.c
> +++ b/variables.c
> @@ -361,7 +361,7 @@ initialize_shell_variables (env, privmode)
...
> - if (legal_identifier (name))
> +
- "Eduardo A. Bustamante López" wrote:
> Well, what did you expect? You're relying on undocumented features.
...
> So, fix your scripts, perhaps?
I am sorry I seem to have offended you so much to have warranted this form of
response :(.
> It's common knowledge that if you rely on undocumen
-A 1
std:echo=() { echo "$@"
}
$ bash --norc
bash: error importing function definition for `std:echo'
$ std:echo hello world
bash: std:echo: command not found
Sincerely,
Jay Freeman (saurik)
sau...@saurik.com
that have
been functioning without issue for almost a decade.
$ bash --norc
$ function std:echo() { echo "$@"; }
$ std:echo hello world
hello world
$ export -f std:echo
$ printenv | grep std:echo -A 1
std:echo=() { echo "$@"
}
$ bash --norc
bash: error importing function definition for `std:echo'
$ std:echo hello world
bash: std:echo: command not found
Sincerely,
Jay Freeman (saurik)
sau...@saurik.com
ried to do a 32-bit build of bash (using
CFLAGS='-O2 -m32 -g') and mkbuiltins.o was compiled without -m32 (as it uses
CCFLAGS_FOR_BUILD, which bypasses CFLAGS to use BASE_CCFLAGS) but was being
linked with -m32. I do not yet have a correct fix for this unrelated issue.
Sinc
e's configure.in: they break autoconf's gcc -g
detection, if nothing else.
http://svn.telesphoreo.org/trunk/data/readline/cflags.diff
Sincerely,
Jay Freeman (saurik)
sau...@saurik.com
http://www.saurik.com/
On Mar 18, 6:55 pm, m...@ice.filescope.com, zy...@ice.filescope.com
wrote:
...
> When I type a long string of text and start pressing ctrl-W to
> backwards-kill words, bash deletes the words but doesn't visually refresh
> (the words still appear on the command line). This was not occurrin
