post ur code for review , if u want ..
On Wed, Dec 18, 2024, 7:28 PM Kaz Kylheku wrote:
> On 2024-12-18 06:58, Chet Ramey wrote:
> >> With signals other than SIGALRM, the code has to be careful; if it
> >> ever happens that the signal is delivered without the trap being
> >> in place, Bash will
were my wrong assumptations .. sry .. peace ..
On Wed, Dec 18, 2024, 10:57 PM Kaz Kylheku wrote:
> On 2024-12-18 13:46, microsuxxor wrote:
> > try
> >
> > p=$$ ; while sleep 1 ; do kill -USR1 "$p" ; done &
>
> That's not necessary; my existing repro steps successfully show
> a difference between
On 2024-12-18 13:46, microsuxxor wrote:
> try
>
> p=$$ ; while sleep 1 ; do kill -USR1 "$p" ; done &
That's not necessary; my existing repro steps successfully show
a difference between two signals, that being the only
difference between them.
The $$ parameter is expanded to a decimal numeric
On 2024-12-18 06:58, Chet Ramey wrote:
>> With signals other than SIGALRM, the code has to be careful; if it
>> ever happens that the signal is delivered without the trap being
>> in place, Bash will die.
>
> Same with SIGALRM, too.
OK, that is my mistake. These steps do terminate Bash:
trap -
history -s dummy args
On Wed, Dec 18, 2024, 4:58 PM Dale R. Worley wrote:
> Chet Ramey writes:
> > On 12/17/24 5:19 PM, Dale R. Worley wrote:
> > but it's tough to use programatically: How would
> >> you code a function for use in scripts that adds an entry "foo bar baz"
> >> to the history
On 2024-12-18 12:48, Chet Ramey wrote:
> On 12/18/24 1:27 PM, Kaz Kylheku wrote:
>
>> What remains is the question why I somehow cannot get my
>> stuff to work with a different signal like SIGUSR1 or SIGVTALRM.
>>
>> Bash will not take them while it's sitting in the call to readline.
>
> Somethin
On Wed, Dec 18, 2024, 10:40 PM Kaz Kylheku wrote:
> On 2024-12-18 12:48, Chet Ramey wrote:
> > On 12/18/24 1:27 PM, Kaz Kylheku wrote:
> >
> >> What remains is the question why I somehow cannot get my
> >> stuff to work with a different signal like SIGUSR1 or SIGVTALRM.
> >>
> >> Bash will not ta
On 12/17/24 5:19 PM, Dale R. Worley wrote:
Chet Ramey writes:
What is the point of "history -s args", then? What is it useful for?
To add arbitrary data to the history list, for whatever reason a user
likes. I think the documentation is fairly clear on that.
To be more specific, it adds ar
Date:Wed, 18 Dec 2024 13:56:48 -0800
From:Kaz Kylheku
Message-ID:
| The $$ parameter is expanded to a decimal numeric word
| *before* the while command is executed,
No it isn't.
| so the background process is referencing the correct PID of the parent.
But th
On 2024-12-18 11:02, microsuxxor wrote:
> post ur code for review , if u want ..
It's BSD-licensed freeware: https://www.kylheku.com/cgit/basta/about/
On 12/14/24 6:18 AM, Martin D Kealey wrote:
I'm trying to make sure that my modified version of Bash passes all the
tests, and in the process I'm finding some, erm, oddities.
Firstly, what seems to be a bug:
Looking in tests/printf7.sub it has
INT_MAX=$(getconf INT_MAX 2>/dev/null)
[ -z "$INT_M
Chet Ramey writes:
> On 12/17/24 5:19 PM, Dale R. Worley wrote:
> but it's tough to use programatically: How would
>> you code a function for use in scripts that adds an entry "foo bar baz"
>> to the history list without removing anything already on the history
>> list?
>
> Add a dummy command
On 12/18/24 10:57 AM, Dale R. Worley wrote:
Add a dummy command to the history, or expect the function call to be
removed, or both?
Er... How do you add a dummy command to the history? Admittedly, I'm
not an expert in bash history processing, but I checked over the options
to "history" and no
On 12/15/24 2:16 AM, Kaz Kylheku wrote:
If you do not have "trap : ALRM" then this doesn't happen.
Because SIGALRM is a terminating signal that kills the shell.
But no; I mean the shell keeps running in that case. Try it:
$ kill -ALRM $$
$ # didn't die
Then something about the execu
Was "waiting for process substitutions".
On Sat, Oct 12, 2024 at 10:09 AM Zachary Santer wrote:
>
> On Sun, Jul 14, 2024 at 8:40 PM Zachary Santer wrote:
> >
> > On Tue, Jul 9, 2024 at 2:37 PM Zachary Santer wrote:
> > >
> > > On the other hand, do funsubs give us the answer here?
> > >
> > > s
On Wed, Dec 18, 2024, at 9:39 PM, Zachary Santer wrote:
> $ set -u
> $ unset REPLY
> $ printf '%s\n' "${REPLY}"
> bash: REPLY: unbound variable
> $ printf '%s\n' "${| :; }"
>
> $ printf '%s\n' "${| unset REPLY; }"
FWIW, this agrees with mksh R59 2020/10/31 but not zsh master.
(I'll be raising the
The first beta release of bash-5.3 is now available with the URLs
ftp://ftp.cwru.edu/pub/bash/bash-5.3-beta.tar.gz
https://ftp.gnu.org/pub/gnu/bash/bash-5.3-beta.tar.gz
and from the bash-5.3-testing branch in the bash git repository
(http://git.savannah.gnu.org/cgit/bash.git/log/?h=bash-5.3-testi
i made smth with reserved line for some chat ..
On Wed, Dec 18, 2024, 8:18 PM Kaz Kylheku wrote:
> On 2024-12-18 11:02, microsuxxor wrote:
> > post ur code for review , if u want ..
>
> It's BSD-licensed freeware: https://www.kylheku.com/cgit/basta/about/
>
On 12/18/24 1:27 PM, Kaz Kylheku wrote:
What remains is the question why I somehow cannot get my
stuff to work with a different signal like SIGUSR1 or SIGVTALRM.
Bash will not take them while it's sitting in the call to readline.
Something is indeed messed up in your execution environment.
L
19 matches
Mail list logo
