is there plans to add / handle multiple redirection-procs in one cmd in the
jobs table
On Thu, Oct 17, 2024, 23:15 Chet Ramey wrote:
> On 9/22/24 1:48 PM, Zachary Santer wrote:
> > If you're not going to make 'wait -n' without id
> > arguments pull something from the bgp list, then the 'set -o p
i doubt its 'bminor'
he talks about bash git on savannah .. i think ..
On Mon, Nov 4, 2024, 09:21 Christoph Zimmermann
wrote:
> Hi Chat,
>
> As I can't seem to find this: You are referring to the 'devel' branch at
> https://github.com/bminor/bash (files doc/bash.info and doc/bash.1)?
>
>
u can just try the BASH_XTRACEFD=3 line w/o else ... and where u need set
-xv output u capture the fd 3
or u can set -xv to 2 but apps to stderr use 3
On Sun, Nov 3, 2024, 13:45 Christoph Zimmermann
wrote:
> Thanks for all the quick reactions on that issue (including microsuxx's
> suggestion whi
~ $ bash mb.test.3stderr
+ echo foo
exec 3<&2
BASH_XTRACEFD=3
set -x
{
echo foo >&2
} 2>&-
On Sat, Nov 2, 2024, 19:25 wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: aarch64
> OS: darwin24.0.0
> Compiler: clang
> Compilation CFLAGS: -DSSH_SOURCE_BASHRC
>
exec 3<&2
BASH_XTRACEFD=3
set -x
{
echo foo >&2
} 2>&-
replace &- with file to out log the echo
On Sat, Nov 2, 2024, 20:37 wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: aarch64
> OS: darwin24.0.0
> Compiler: clang
> Compilation CFLAGS: -DSSH_SOURCE_BASH
i think ..
BASH_XTRACEFD=3
.. alone may also do ..
u try ..
On Sat, Nov 2, 2024, 20:55 #!microsuxx wrote:
> exec 3<&2
> BASH_XTRACEFD=3
> set -x
> {
> echo foo >&2
> } 2>&-
>
> replace &- with file to out log the echo
>
> On Sat, No
On Thu, Nov 7, 2024, 21:10 Chet Ramey wrote:
> On 11/6/24 9:38 PM, David Linden wrote:
>
> > Bash Version: 4.4
> > Patch Level: 20
> > Release Status: release
> >
> > Description:
> > This errors in 4.4, did not in 4.2: set -u; declare -A foo; echo
> ${#foo[@]}
>
> Yes, this was a bug in ba
On Thu, Nov 7, 2024, 23:36 #!microsuxx wrote:
>
>
> On Thu, Nov 7, 2024, 21:10 Chet Ramey wrote:
>
>> On 11/6/24 9:38 PM, David Linden wrote:
>>
>> > Bash Version: 4.4
>> > Patch Level: 20
>> > Release Status: release
>> >
>> &g
oc+=( 2foo 2bar )'
c unset -v assoc
On Thu, Nov 7, 2024, 23:36 #!microsuxx wrote:
>
>
> On Thu, Nov 7, 2024, 21:10 Chet Ramey wrote:
>
>> On 11/6/24 9:38 PM, David Linden wrote:
>>
>> > Bash Version: 4.4
>> > Patch Level: 20
>> > Release Statu
there is still code fault $n is supposed to be 'assoc' im sorry bye
On Thu, Nov 7, 2024, 23:44 #!microsuxx wrote:
> sorry code cleaned up : it was more and stuff
>
> c() {
> eval -- "$@"
> l
> }
>
> l() {
> r [[ -v $n ]]
> r "(( \${#$n[@
the printf %d gets to be no print_out at all
u specify a % but no arg
means it wont try printf at all smth
printf %d '' we can talk about
returns 0
and looks normal so to me
On Tue, Nov 19, 2024, 8:46 PM Paul Eggert wrote:
> Configuration Information [Automatically generated, do not change]:
>
On Tue, Nov 19, 2024, 10:04 PM #!microsuxx wrote:
> the printf %d gets to be no print_out at all
> u specify a % but no arg
> means it wont try printf at all smth
>
> printf %d '' we can talk about
> returns 0
> and looks normal so to me
>
sorry i missed u alr
ah and to save and have it
copy it into .bash_profile or .profile
On Sat, Nov 16, 2024, 9:15 PM #!microsuxx wrote:
> so , this is using the logic that vim returns a specific code 148 on
> control-z
> checking $? for it is what i did , for your request ..
>
> that thats a bit more
And where/when to run
> it?
>
> Den lör 16 nov. 2024 16:48#!microsuxx skrev:
>
>> trap ' t=$? ; [[ $BASH_COMMAND != *'$'bashcmd* ]] &&
>> bashcmd=$BASH_COMMAND ' debug ; PROMPT_COMMAND=' [[ $t == 148 && $bashcmd
>> ==
back to
tty , or restore from saved
u can also
eval " &( < a.bash ) "
and anotherone is using $LINENO or some similiar value , on error
On Thu, Nov 14, 2024, 12:09 AM #!microsuxx wrote:
> source is not tty dependand , so try ..
>
> tee -a log < <(
> exec 2
-x
. mybash
vars_code
) |& tee -a log
On Thu, Nov 14, 2024, 12:19 AM Yuri wrote:
> On 11/13/24 14:48, #!microsuxx wrote:
> > 1st source cmd , no extra cmds 2. { . foo ; code ; code ; } | tee 3rd
> > tee < <( . foo ; cmds )
>
>
> I need to (1) source the user scr
if u dont need stderr even simpler
On Thu, Nov 14, 2024, 12:36 AM #!microsuxx wrote:
> what u need to do with the vars
> include all code in tee
> or try
>
> exec > >( tee -a log ) 2>&1
> set -x
> . my.bash
> ...
>
> what i firstly meant :
>
&g
depending on actual purpose instead bs demo code , there are serval
approaches to code running code
On Wed, Nov 13, 2024, 11:13 PM Yuri wrote:
> On 11/13/24 14:02, Greg Wooledge wrote:
> > The commands within a pipeline are executed in subshells (child
> > processes), so all variable changes are
24, 11:45 PM #!microsuxx wrote:
> depending on actual purpose instead bs demo code , there are serval
> approaches to code running code
>
> On Wed, Nov 13, 2024, 11:13 PM Yuri wrote:
>
>> On 11/13/24 14:02, Greg Wooledge wrote:
>> > The commands within a pipel
source is not tty dependand , so try ..
tee -a log < <(
exec 2>&1
set -x
. user.bash
)
On Wed, Nov 13, 2024, 11:52 PM Yuri wrote:
> On 11/13/24 14:45, #!microsuxx wrote:
> > depending on actual purpose instead bs demo code , there are serval
> > approaches to
i agree
its hard to , say , comm clearly together
i suggest for next times more real life true examples
op's msgs werent so much detailed , more bla-neric :))
greets all
On Thu, Nov 14, 2024, 1:35 AM Robert Elz wrote:
> Date:Wed, 13 Nov 2024 15:18:58 -0800
> From:Yuri
On Thu, Nov 14, 2024, 12:57 AM Yuri wrote:
> On 11/13/24 15:44, Greg Wooledge wrote:
> > If the "user script" runs quickly enough, then: source userscript
> > >logfile 2>&1 cat logfile
>
>
> This would fail to save the user script's output in case it would
> execute "exit 1"
>
the >logfile makes
wrote:
> Hi !microsuxx,
>
>
> But I need to save the output of the user script into a dedicated log file.
> This script should run, should save its output into a dedicated log, and
> then many other commands should use these environment variables.
>
> Their logs ca
try ..
exec 3> >( tee -a log ) # or 3>>
. user.bash >&3
cmds ; cmds ; vars ; cmds
On Thu, Nov 14, 2024, 12:56 AM #!microsuxx wrote:
> u need to , save out of . script1 to log1 but what was your second
> sentense alike of this first one ?
> u run source over log1 to
maybe ur email formats it wrong
those are two lines , by greg
not one
anyway if u append more than one cmd to logfile
more than one source cmd
u need to use >>logfile instead of >logfile
On Thu, Nov 14, 2024, 1:00 AM #!microsuxx wrote:
>
>
> On Thu, Nov 14, 2024, 12:57 AM Yu
also u need to $log
may i ask what criteria ur scripts are about
a $log can be
log=/tmp/my.log.$USER.$SRANDOM
On Thu, Nov 14, 2024, 1:04 AM #!microsuxx wrote:
> maybe ur email formats it wrong
> those are two lines , by greg
> not one
>
> anyway if u append more than one cmd to
maybe set -a 'd help ?
if it can backwards export the vars
On Thu, Nov 14, 2024, 3:01 PM Chet Ramey wrote:
> On 11/13/24 4:48 PM, Yuri wrote:
>
> > The first 'source' command didn't set variables set or exported in the
> > child.sh script, even though 'source' is executed in the current
> script
aidd , thxx .. ++
On Thu, Nov 14, 2024, 8:45 PM Chet Ramey wrote:
> On 11/14/24 2:28 PM, #!microsuxx wrote:
> > maybe set -a 'd help ?
> > if it can backwards export the vars
>
> No. A child process can't affect its parent's environment without inventing
&g
another code is
if u wanna not use . or eval or bash cmd
( . is source )
shopt -s expand_aliases
alias script=" $( < user.bash ) "
script
On Thu, Nov 14, 2024, 1:10 AM #!microsuxx wrote:
> also u need to $log
> may i ask what criteria ur scripts are about
>
> a $log c
PROMPT_COMMAND=' [[ $? == 148 ]] && stty sane '
On Sat, Nov 16, 2024, 11:29 AM David Moberg wrote:
> Ok, is there anything I can do on my user side to get desired behavior?
> (similar to running `stty sane` every time I send vim to the background.)
>
> Den tis 12 nov. 2024 16:49Chet Ramey skrev
trap ' t=$? ; [[ $BASH_COMMAND != *'$'bashcmd* ]] && bashcmd=$BASH_COMMAND
' debug ; PROMPT_COMMAND=' [[ $t == 148 && $bashcmd == vim* ]] && echo ye
&& stty sane '
On Sat, Nov 16, 2024, 4:40 PM #!microsuxx wrote:
> PROMPT_COMM
~ $ command -v bash
/data/data/com.termux/files/usr/bin/bash
~ $ command -V bash
bash is /data/data/com.termux/files/usr/bin/bash
V adds english text
On Tue, Nov 26, 2024, 3:44 AM Lawrence Velázquez wrote:
> On Mon, Nov 25, 2024, at 9:03 PM, Martin D Kealey wrote:
> > I keep "similar" there bec
e wrote:
> On 2025-02-03 22:19, microsuxx wrote:
>
> > ~ $ p=~:~:~ ; declare -p p
> > declare --
> >
> p="/data/data/com.termux/files/home:/data/data/com.termux/files/home:/data/data/com.termux/files/home"
> >
> > ~ $ cp $( type -P bash ) sh
&
dude u cant whitelist it or smth .. ?
On Tue, Feb 4, 2025, 3:00 AM Zeffie via Bug reports for the GNU Bourne
Again SHell wrote:
> Thank you for your thoughts. While I appreciate your perspective on DKIM
> and spam filtering, I expect the list maintainers to handle these issues
> properly. I've b
SHell wrote:
> On 2025-02-03 18:14, microsuxx wrote:
> > i suggest u be some kinder ..
> >
>
> I have a long history on various Linux forums and always strive to
> remain polite and respectful. However, I have a very low tolerance for
> practices like top posting and resp
with all i mean freebsd ones
On Tue, Feb 4, 2025, 4:12 AM microsuxx wrote:
> look dude ,
> i looked at the link flying by
> by long texts and no clear examples this n that
>
> try , providing _all_ _exact_ cmds to reproduce it , in once , here and on
> ur other list
>
>
~ $ p=~:~:~ ; declare -p p
declare --
p="/data/data/com.termux/files/home:/data/data/com.termux/files/home:/data/data/com.termux/files/home"
~ $ cp $( type -P bash ) sh
~ $ ./sh
sh-5.2$ x=~:~:~:
sh-5.2$ declare -p x
declare --
x="/data/data/com.termux/files/home:/data/data/com.termux/files/home:/d
i suggest u be some kinder ..
On Mon, Feb 3, 2025, 11:43 PM Zeffie via Bug reports for the GNU Bourne
Again SHell wrote:
> Thank you for taking the time to not review the FreeBSD bug report (Bug
> 284513) in full before responding. Your willingness to speculate on
> behaviors without testing in
a bit unrelated .. cheap numbers filter ..
gimme_num( ) { declare -n b=BASH_REMATCH\[1] ; local o m=[0-9,.] s=$n i t ;
t="(-?$m+)" ; unset -v o ; for n ; do unset -v i ; while [[ $n =~ $t ]] ;
do n=${n/"$b"} i= o+=$b$s ; done ; [[ -v i ]] && o+=$s ; done ; [[ -v o ]]
&& printf %s "$o" ; }
gimme_n
ur subst version is best and fastest
, the my last version seems buggy
its to filter out numbers
.. just a bit related to the topic sorry ..
++ greets ++
On Tue, Feb 11, 2025, 10:23 AM Phi Debian wrote:
>
> Can follow that fast, the n-1 version gives
>
> gimme_num( ) { local y o m='[0-9,.]' s=
On Tue, Feb 11, 2025, 7:13 AM Phi Debian wrote:
>
>
> On Mon, Feb 10, 2025 at 11:46 PM microsuxx wrote:
>
>> a bit unrelated .. cheap numbers filter ..
>>
>> gimme_num( ) { declare -n b=BASH_REMATCH\[1] ; local o m=[0-9,.] s=$n i t
>> ;
>> t=&quo
;
[[ -v o ]] && printf %s "$o" ; }
On Tue, Feb 11, 2025, 10:11 AM microsuxx wrote:
> ah , cool
>
> .. my bash 5.3 dev seems to have declare -n arr\[elem] while i think the
> old 5.2x that didnt work
>
> try plzz ..
>
> gimme_num( ) { local y o m='[0
TCH[1]}
n=${n/"$y"} i= o+=$y$s ; done ; [[ -v i ]] && o+=$s ; done ; [[ -v o ]] &&
printf %s "$o" ; }
On Tue, Feb 11, 2025, 10:07 AM Phi Debian wrote:
>
>
> On Tue, Feb 11, 2025 at 9:37 AM microsuxx wrote:
>
>> how does it output strings .. ?
&g
!!:$ null
!$ null
$_ echo
On Sat, Jan 18, 2025, 7:29 AM Martin Schulte
wrote:
> Hello,
>
> in 9.3.2 of https://www.gnu.org/software/bash/manual/bash.html we find:
>
> !!:$ designates the last argument of the preceding command. This may be
> shortened to !$.
>
> Shouldn't this be "the last word"
~ $ set -f
~ $ foo=$(printf "%*s\n" 80 " " | tr " " "*") ; echo $foo
~ $ printf -v v '%*s' 200 ' ' ; v=${v// /\*} ; echo $v
*
the \* to * works also
leftover of testing
.. needs set -f
On Sat, Jan 25, 2025, 3:34 PM microsuxx wrote:
> ~ $ set -f
> ~ $ foo=$(printf "%*s\n" 80 " " | tr " " "*") ; echo $foo
>
> **
On Mon, Jan 13, 2025, 4:46 AM Greg Wooledge wrote:
> On Mon, Jan 13, 2025 at 08:42:39 +0700, Robert Elz wrote:
> > It is unexpected, because users believe (from other experience)
> > that the delimiters separate fields, but in sh they don't, they
> > terminate fields.
>
> At the risk of going a b
does the output @ https://0x0.st/8-Fv.txt
make it into the race
by cmd @ https://0x0.st/8-Ft.txt
i can be as well fully off the topic
excuse me then , and plz lemme know ..
On Mon, Jan 13, 2025, 9:03 AM Félix Hauri wrote:
> Le Sun, Jan 12, 2025 at 04:10:03PM -0500, Chet Ramey a écrit :
> >
those bugs have old lib versions around ..
On Fri, Jan 17, 2025, 3:32 PM Chet Ramey wrote:
> On 1/15/25 4:08 PM, Grisha Levit wrote:
> > Another undo list UAF. Related, I think, to edit-and-execute-command.
> >
> > HISTFILE= INPUTRC=/ bash --norc -in <<< $' \n\cP \cN\cP\cU\cX\cE\n\e<'
>
> I can'
to use ~ as file ..
'~' n "~"
or ./~
On Wed, Feb 12, 2025, 5:21 PM Andrés Rodríguez Reina wrote:
> Subject: [Suggestion] Add warning/error when using the tilde expansion in
> a folder where the tile-named file/folder exists
>
> Configuration Information [Automatically generated, do not change]:
or \~
On Wed, Feb 12, 2025, 9:05 PM microsuxx wrote:
> to use ~ as file ..
>
> '~' n "~"
> or ./~
>
> On Wed, Feb 12, 2025, 5:21 PM Andrés Rodríguez Reina
> wrote:
>
>> Subject: [Suggestion] Add warning/error when using the tilde expansion in
&
is that if fifo or if nonormal file ..
.. is that another story from history .. ?
that it doesnt accept them ..
On Fri, Feb 14, 2025, 1:36 PM Greg Wooledge wrote:
> On Fri, Feb 14, 2025 at 05:19:48 -0600, MacBeth wrote:
> > On Fri, Feb 14, 2025 at 4:31 AM MacBeth
> wrote:
> > > # fails:
> > > $
it looks me cause such as it isnt a file , yes ..
On Fri, Feb 14, 2025, 12:20 PM MacBeth wrote:
> On Fri, Feb 14, 2025 at 4:31 AM MacBeth wrote:
> >
> > Ummm, isn't this supposed to work? I'm guessing there's a technical
> > reason why it doesn't...?
> >
> > # fails:
> > $ history -r <(echo 'ec
what u wanna fix on it
On Mon, Feb 24, 2025, 3:13 PM rjuliuscezar--- via Bug reports for the GNU
Bourne Again SHell wrote:
> usage: command-not-found
>
> ╭─u0_a440@localhost ~
> ╰─🍄💨➤➤
>
>
++bugfixes++
On Wed, Feb 26, 2025, 3:15 PM Chet Ramey wrote:
> On 2/23/25 12:20 PM, Max Bowsher wrote:
>
> > Bash Version: 5.2
> > Patch Level: 37
> > Release Status: release
> >
> > Description:
> >
> > When using $BASH_COMMAND in an EXIT trap to tell the user what failed, I
> > came across a p
{0} is no expansion
{0,} is
it must be 2+
On Thu, Mar 6, 2025, 7:40 PM Trond Endrestøl via Bug reports for the GNU
Bourne Again SHell wrote:
> $ bash --version
> GNU bash, version 5.2.37(0)-release (amd64-portbld-freebsd14.1)
> Copyright (C) 2022 Free Software Foundation, Inc.
> License GPLv3+:
when bash reads exit cmd it will exit
so bash reads rc and exits ..
also .. u may have a ';exit' alias ..
On Tue, Mar 25, 2025, 22:15 microsuxx wrote:
> dude if u tell bash to exit it will exit ..
>
> On Tue, Mar 25, 2025, 20:41 Ethan Gascoigne wrote:
>
>> From: e
dude if u tell bash to exit it will exit ..
On Tue, Mar 25, 2025, 20:41 Ethan Gascoigne wrote:
> From: ethan
> To: bug-bash@gnu.org
> Subject: ;exit in bash history causes bash to exit
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Com
ah bash history file ..
.. yea i tried , bash dev doesnt segfault or anything , with it on a line
and without an ending newline
warm greetings .. :))
On Tue, Mar 25, 2025, 22:56 Greg Wooledge wrote:
> On Tue, Mar 25, 2025 at 22:16:15 +0100, microsuxx wrote:
> > when bash reads exit cm
yea make bug report
.. in my experience , such bash codes on github have very low code quality
..
peace .. ++
On Wed, Mar 26, 2025, 15:09 Ethan Gascoigne wrote:
> I do have an alias with `&& exit` in it, but removing that alias
> doesn't get rid of the bug. I've tested it on another system (Xub
one small addition , <<'foo' ( with quotes is used ) ..
.. should tell bash expliciply preserve data ..
On Mon, Apr 7, 2025, 23:51 microsuxx wrote:
> i dunno what lithist is , but remaining data one to one is a big bug thats
> gotta be fixed
> its like u write foo &quo
i dunno what lithist is , but remaining data one to one is a big bug thats
gotta be fixed
its like u write foo "$1" "$2" and it sends foo $1 $2
.. if data , in case heredoc content , which is highly underrated and
underused , is not remained .. its nothing else than a big broken cmd
plz fixx
greets
++
On Sun, Mar 16, 2025, 12:10 AM MacBeth wrote:
> On Sat, Mar 15, 2025 at 12:33 PM Greg Wooledge wrote:
> > On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for
> the GNU Bourne Again SHell wrote:
> > > How do you end the heredoc with a multiline delimiter such as the
> fol
[[ -d /proc/"$!" ]]
On Tue, Apr 8, 2025, 16:33 Andreas Schwab wrote:
> On Apr 08 2025, MacBeth wrote:
>
> > while ((dur /dev/null; do
>
> You can use kill -0 $! to check if the process still exists.
>
> --
> Andreas Schwab, SUSE Labs, sch...@suse.de
> GPG Key fingerprint = 0196 BAD8 1CE9 197
same error as eof i'd say ..
On Fri, Apr 11, 2025, 01:53 A. James Lewis wrote:
> I'm not quite sure about that, I would be trying to get back the file
> descriptor to use for a period and then close it... so if it fails to
> open, then I don't know if "redirection error" makes sense, but then
>
++
On Fri, Apr 11, 2025, 17:21 Chet Ramey wrote:
> On 4/11/25 11:03 AM, microsuxx wrote:
> > same error as eof i'd say ..
>
> No. The file descriptor is invalid. There is a difference between a read
> error (-1/EINVAL) and EOF (0).
>
> --
> ``The lyf so s
++
On Mon, Apr 14, 2025, 16:46 Chet Ramey wrote:
> On 4/13/25 11:37 AM, microsuxx wrote:
> > seems to cycle between lc : parts one loose ..
>
> No, these are all translated strings.
>
> >> hobbit:~$ LANGUAGE=en_US:es_ES bash --version
> >> GNU bash, versió
seems to cycle between lc : parts one loose ..
On Sun, Apr 13, 2025, 16:46 Greg Wooledge wrote:
> On Sun, Apr 13, 2025 at 16:06:46 +0200, Kaulkwappe wrote:
> > > bash --version
> > > GNU bash, Version 5.2.32(1)-release (x86_64-redhat-linux-gnu)
> > > Copyright (C) 2022 Free Software Foundation,
68 matches
Mail list logo
