Hello.
In section “3.2.4.2 Conditional Constructs” of Bash docs (both in ‘man’ and in
the web), at the end, there is an explanation on combining expressions,
starting with the use of brackets.
There it would be worth to mention that:
1. you must escape the brackets, also inside script files
2.
From: v...@posteo.org
To: bug-bash@gnu.org,b...@packages.debian.org
Subject: bash displays strange characters after base64 decoding
Configuration Information:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCO
On Thu, Aug 06, 2015 at 04:13:30PM +0200, Juanma wrote:
> In section ???3.2.4.2 Conditional Constructs??? of Bash docs (both in
> ???man??? and in the web), at the end, there is an explanation on combining
> expressions, starting with the use of brackets.
>
> There it would be worth to mention t
On Thu, Aug 6, 2015 at 12:45 PM, Valentin Schmidt wrote:
> From: v...@posteo.org
> To: bug-bash@gnu.org,b...@packages.debian.org
> Subject: bash displays strange characters after base64 decoding
>
> Configuration Information:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:
Valentin Schmidt wrote:
> Subject: bash displays strange characters after base64 decoding
> Bash displays strange characters (including command prompt) (see attached
> png file) after the execution of the base64 (GNU coreutils 8.21) command
> like described as follows:
> base64 -d base64.txt
This
