Mike Frysinger wrote:
> seems there's a way to get bash to report exit values greater than 255 ...
>
> since it requires certain key presses, things in between <...> means a key
> press rather than typing literally ...
This will be fixed in the next version.
Chet
--
``The lyf so short, the cr
On Thursday 26 February 2009 03:25:50 Sven Mascheck wrote:
> On Wed, Feb 25, 2009 at 01:20:50PM -0500, Mike Frysinger wrote:
> > seems there's a way to get bash to report exit values greater than 255
> > ...
>
> you will find the special error values
> in shell.h, for instance
> #define EX_SHER
On Wed, Feb 25, 2009 at 01:20:50PM -0500, Mike Frysinger wrote:
> seems there's a way to get bash to report exit values greater than 255 ...
you will find the special error values
in shell.h, for instance
#define EX_SHERRBASE256 /* all special error values are > this. */
#define E
Mike Frysinger wrote:
> $ true
> $ echo '
>
> $ echo $?
> 258
>
> $ true
> $ echo '
>
> $ echo '
>
> $ echo $?
> 386
Just tested it, hopefully it's as easy as changing every
itos (last_command_exit_value)
to
itos (last_command_exit_value & 0xFF)
in subst.c (seems 2 times).
I don't provid
Mike Frysinger wrote:
> $ true
> $ echo '
>
> $ echo $?
> 258
>
> $ true
> $ echo '
>
> $ echo '
>
> $ echo $?
> 386
>
> that doesnt seem right to me :)
>
> the first test seems fine, and older versions of bash would set 258 for the
> second test (not sure if it's correct though), but the t
seems there's a way to get bash to report exit values greater than 255 ...
since it requires certain key presses, things in between <...> means a key
press rather than typing literally ...
$ true
$ echo '
$ echo $?
128
$ echo '
$ echo '
$ echo $?
128
$ true
$ echo '
$ echo $?
258
$ true
$
