Re: bash support for XDG Base Directory spec (~/.config/bash/)
hello, Can I please receive an update? Thank you, Allison On Fri, May 7, 2021 at 11:48 AM Allison Karlitskaya wrote: > > hello, > > Please consider these two patches for inclusion in bash to support > storing shell initialisation files (profile, bashrc) in a subdirectory > of ~/.config/ as most programs do these days. > > I'm happy to make changes to address any feedback. > > Even if you'd prefer not to apply the second patch, applying the first > patch is a nice cleanup and would make it easier for distributions > such as Fedora to apply the second patch for themselves. > > Thank you very much for your consideration, > > Allison
Re: bash support for XDG Base Directory spec (~/.config/bash/)
On 5/25/21 3:36 AM, Allison Karlitskaya wrote: hello, Can I please receive an update? Hi. I don't have an update; I haven't looked at this yet. This is not a high priority issue. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
!(.pattern) can match . and .. if dotglob is enabled
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Linux columbus 4.4.246-gentoo #2 SMP Thu Dec 31 17:31:16 -00 2020 i686 AMD Athlon(tm) XP 2800+ AuthenticAMD GNU/Linux Machine Type: i686-pc-linux-gnu Bash Version: 5.1 Patch Level: 8 Release Status: release Hello, Repeat-By: $ shopt -s dotglob extglob $ echo !(.foo) . .. .other files The doc says: "The filenames '.' and '..' must always be matched explicitly, even if dotglob is set." I would infer that a !(...) should never match '.' and '..', because you cannot match something literally using an operator that means "anything except". The patterns .foo and [.]foo are equivalent under dotglob, therefore I would expect !(.foo) and !([.]foo) to be also equivalent. But . and .. are excluded here already: $ shopt -s dotglob extglob $ echo !([.]foo) .other files $ echo !(foo) .other files Personally I can't imagine how it can be ever useful for a pattern to match . or .. (unless the path component is literally . or ..). Therefore I always work with dotglob enabled and use [.]pattern instead of .pattern to get rid of . and .. But I don't think it makes much sense with the !(...) operator. Also the pattern !(.foo) didn't match . and .. before version 4.3.0. Regards, NP
Re: [patch #10070] toggle invert flag when reading `!'
On Mon, May 24, 2021 at 11:47:32AM -0400, Chet Ramey wrote: > On 5/22/21 2:45 PM, Vincent Menegaux wrote: > > > Details: > > > > Previously, these commands: > > > >[[ ! 1 -eq 1 ]]; echo $? > >[[ ! ! 1 -eq 1 ]]; echo $? > > > > would both result in `1', since parsing `!' set CMD_INVERT_RETURN > > instead of toggling it. I will try this as: $ [ 1 -eq 1 ]; echo $? 0 $ ! [ 1 -eq 1 ]; echo $? 1 $ ! ! [ 1 -eq 1 ]; echo $? 0 -- Félix Hauri -- http://www.f-hauri.ch
