On Wed, Jun 02, 2021 at 03:54:34PM -0600, v...@it4us.top wrote:
> --first script where declare -x -g works
> bar(){
>
> [[ $cnt == 1 ]] && declare -g -x nestedbug="not a nested variable-bug
> !!"
> }
>
> foo(){
> [[ $cnt == 1 ]] && bar && echo ${nestedbug:?"va
On 6/2/21 6:06 PM, jonasxavier wrote:
> Hi.
>
> I would like to know why bash does not follow FHS 3.0 (Filesystem
> Hierarchy Standard) suggestions. FHS 3.0 says
>
> "... 3.8.2. Requirements ... If an application needs to create more
> than one dot filethen they should be placed in a subdirectory
Hi.
I would like to know why bash does not follow FHS 3.0 (Filesystem Hierarchy
Standard) suggestions. FHS 3.0 says
"... 3.8.2. Requirements ... If an application needs to create more than one
dot filethen they should be placed in a subdirectory ..."
Bash uses ~/.files instead of ~/.bash/files
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-a6qmCk/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname o
On 5/31/21 11:23 AM, Nora Platiel wrote:
How would you improve the wording? What do you think is most important to
cover?
Here is the full paragraph for reference:
When a pattern is used for filename expansion, the character `.' at the
start of a filename or immediately following a slash must
