Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security
uname output: Linux ginger 4.18.0-240.15.1.el8_3.x86_64 #1 SMP Mon Mar 1
17:16:16 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ export vim=$HOME/.GVim-v8.2.2451.glibc2.15-x86_64.AppImage
$
$ vimV=$($vim --version)||echo handle error here #without
export, error is captured
fuse: failed to exec fusermount: No such file or directory
open dir error: No such file or directory
handle error here
$
$ export
>
> > . and .. are excluded from @(?|.?) in
> > bash 4.2.46(2)-release (CentOS 7.8), but are included in
> > bash 4.4.19(1)-release (CentOS 8.2) and
> > bash 5.0.17(1)-release (Ubuntu 20.04/focal).
>
According to the manual, "[t]he filenames ‘.’ and ‘..’ must al
ew from...
On Mon, Jan 25, 2021 at 3:36 PM gregrwm wrote:
> 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
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 out
On Feb 22, 2015 7:57 PM, "Chet Ramey" wrote:
> On 2/22/15 5:57 PM, gregrwm wrote:
> > On Feb 13, 2015 7:38 AM, "Chet Ramey" > <mailto:chet.ra...@case.edu>> wrote:
> >> On 2/12/15 9:06 AM, gregrwm wrote:
> >> > i now susp
On Feb 13, 2015 7:38 AM, "Chet Ramey" wrote:
> On 2/12/15 9:06 AM, gregrwm wrote:
> > i now suspect bash does not properly handle EINTR while handling
history.
>
> Maybe. There's not enough information here to say.
>
> > this just happened:
> > bash:
from you if you have questions, or even if you
don't. many thanks for all your bashing.
greg
On 16 January 2014 at 16:42, gregrwm wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLA
using break breaks simple usability of loop exit status, eg:
for f in "$@";do
mv "$f" "$x$f$y"||break
done
if break would preserve the exit status of the preceding command then the
above loop would have a useful exit status.
an option analogous to pipefail could request the better break behav
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/loc
uname output: Linux
> @(foo)
> !()
> ..sounds like what you're looking for to me.
ty! @ had escaped my notice, and seems indeed what i wanted, craft a
selection of files eg /@(?|??|??.*|los*|ne*), and then move the inverse
selection /!(?|??|??.*|los*|ne*). thanks again.
>> > echo !(??|foo|bar)
>>
>> precisely where i started this thread, !(??)
>
> +(??) and !(??) are completely different things. !(??) was never
mentioned in the original question, and should work as expected.
yow, truly, you're saying +(??) selects *any multiple* of 2chars, but !(??)
excludes 2cha
> echo !(??|foo|bar)
precisely where i started this thread, !(??)
>> i wanted to move a bunch of files & directories, all except a certain
>> few, so i figured i'd use !(this|or|that). so first i looked to see
>> if +(this|or|that) isolated what i expected...
>
> you would want /@(??) or simply /??, since there's no need for extglob for
> that.
well what i act
i wanted to move a bunch of files & directories, all except a certain
few, so i figured i'd use !(this|or|that). so first i looked to see
if +(this|or|that) isolated what i expected. well perhaps i don't
understand what it's supposed to do.. shouldn't /+(??) capture 2
letter files only?
$ echo
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
-
e&c-
thanks for clarifying.
-g
"No culture can live, if it attempts to be exclusive." —*Gandhi*
a function invoking an alias works, unless they are defined within the same
conditional, eg:
$ if true;then
>alias aseparate='echo aseparate'
> fi
$ if true;then
> fseparate()(aseparate)
> fi
$ if true;then
>alias atogether='echo atogether'
> ftogether()(atogethe
> OK, thanks for the clarification. I see the problem. It's an incorrect
>
> calculation of the `next history line' in operate_and_get_next() that
> mishandles this particular case.
>
> By default, bash limits the size of the history to 500 commands, which
> means you get the commands you execute
> > Repeat-By:
> > rm $HISTFILE #start with no history file
> > exec -cl bash --norc --noprofile #start with no history in memory
> > pm=1.2.3.4 #do some commands
> > sb='echo sudo -uboo'
> > ssb="$sb ssh -p1234 $pm cd boo;"
> > $ssb 'e
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
-
23 matches
Mail list logo
