Hi,
the docs for basenc --base16 says "hex encoding (RFC4648 section 8)".
The referenced section in that RFC says
Essentially, Base 16 encoding is the standard case-insensitive hex
encoding and may be referred to as "base16" or "hex".
I think it would be both more useful, and consistent wit
On 23/10/2023 10:37, Niels Möller wrote:
Hi,
the docs for basenc --base16 says "hex encoding (RFC4648 section 8)".
The referenced section in that RFC says
Essentially, Base 16 encoding is the standard case-insensitive hex
encoding and may be referred to as "base16" or "hex".
I think it w
Pádraig Brady writes:
> Will apply the attached later.
> Marking this as done.
Thanks! It would make some sense to me to also have options
--upper/--lower; on encoding, they would specify case of the output, on
decoding, they would reject the other case (with default being to accept
either). But
On 23/10/2023 13:50, Niels Möller wrote:
Pádraig Brady writes:
Will apply the attached later.
Marking this as done.
Thanks! It would make some sense to me to also have options
--upper/--lower; on encoding, they would specify case of the output, on
decoding, they would reject the other case (
Greetings,
I'm not sure if this is the intended UNIX/POSIX behaviour, but on:
< expr substr a 1 2
, I get:
> a
, which is right, but on:
< expr substr + 1 2
I get:
> expr: syntax error: missing argument after ‘2’
On expr "$line_of_text" 1 2, this error is thrown if the line is a
simple '+'.
A re
NEVERMIND, IT'S ON 'INFO EXPR'.
Could you folks please add it to 'man expr'?
XXX
Greetings,
I'm not sure if this is the intended UNIX/POSIX behaviour, but on:
< expr substr a 1 2
, I get:
a
, which is right, but on:
< expr substr + 1 2
I get:
expr: syntax error: missing argument after ‘2’
On
On 10/23/23 12:58, petabaud51 wrote:
Could you folks please add it to 'man expr'?
Man pages are supposed to be terse
