> Even the venerable BASH shell still has room for modernization
> and improvement. Thank you for your interest and consideration.
How is $((10#${data_line:12:2})) not modern?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA
On Aug 29 2024, Andrey Kovalev wrote:
> - for (fmt = format; *fmt; fmt++)
> + for (fmt = format; fmt - format < strlen(format); fmt++)
How is that different (apart from turing a linear runtime into quadratic
runtime)?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fi
The wrong thing is that the history contains commands that were never
executed: echo 13456 and echo 21234.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Jul 01 2024, Chet Ramey wrote:
> On 7/1/24 3:54 AM, Andreas Schwab wrote:
>
>> So what did change in 5.3 that this is now broken?
>
> If you want to report a bug, report one. Be specific about what you
> think is wrong and what you think the correct behavior is.
The corre
which happens to
> leave the `echo 3456' unchanged -- coincidentally the first history entry
> changed by moving around the history list and editing.
So what did change in 5.3 that this is now broken?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4
4 echo 1234
5 history
bash-5.3$ echo 2345
2345
bash-5.3$ history
1 echo 1234
2 echo 2345
3 echo 13456
4 echo 21234
5 history
6 echo 2345
7 history
bash-5.3$ exit
$ cat history
echo 1234
echo 2345
echo 3456
echo 21234
history
echo 2345
history
--
Andreas S
Why do you think this is a bug in bash? You are telling the shell to
export any modified variable, and you get what you asked for.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
is wider than int, it can
return a wrong value even if the subtraction doesn't overflow.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
thing like SIGHUP.
But leaving it in the process group of the parent shell does not
accomplish that, which is actually the point of this thread. A process
substitution is similar to a pipeline; it really belongs to the process
group of the command that reads from it.
--
Andreas Schwab, SUSE Labs,
In 5.3-alpha, it is no longer possible to quote the special % and #
characters in a pattern replacement expansion.
$ a=1/%2/%3
$ echo "${a/\%/##}"
1/%2/%3##
$ echo "${a/\/%/##}"
1##2/%3
The second example shows that quoting still works as expected for
${PARAMETER//PATTERN/S
bash switches the terminal process group back before the
background process starts reading from the terminal (won't happen in
this example since the cat command blocks on reading the process
substitution file).
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69
from a terminal.
Since the redirection fails and the cat command is never started, bash
doesn't switch the terminal process group, and the background wc command
goes on competing with bash for the terminal.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Apr 28 2024, Chet Ramey wrote:
> On 4/27/24 8:09 AM, Andreas Schwab wrote:
>> On Apr 27 2024, Kerin Millar wrote:
>>
>>> At some point after upgrading to bash-5.3-alpha, the following message
>>> appeared in my kernel ring buffer.
>>>
>>> [
?aa'
> # touch 'something-else'
> # rmdir :
>
> ... produces nothing until pressing the tab key a second time, after which
> both entries are listed while the content of readline's input buffer remains
> unchanged.
':' is in $COMP_WORDBREAKS.
--
Andrea
n later kernels, but nevertheless,
bash should pass MFD_NOEXEC_SEAL (if defined) when it calls
memfd_create.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
nary data doesn't work if you're reading newline-terminated
> records, because you cannot store the NUL character in a shell
> variable. But you can delimit your records on NULs, and use printf to
> reproduce them.
Though that will likely add a spurious null at EOF.
--
Andreas Schwab,
On Apr 15 2024, Greg Wooledge wrote:
> And that's a bug. That code is wrong, and it should be written this way
> instead:
>
> [ -z "$var1" ] && [ -z "$var2" ] && continue
Or just [ -z "$var1$var2" ] && continue
--
And
On Apr 08 2024, Greg Wooledge wrote:
> Now imagine what happens if the shell is killed by a SIGKILL, or if
> the system simply crashes during the script's execution. The script
> is left with altered permissions.
Or the script is executed by more than one process at the same time
not performed,
> because the "$2 is a binary primary" check comes first. This is how
> POSIX documents it.
FWIW, ksh parses it the other way round:
$ ksh93 -c '[ ! -a /tmp ]; echo $?; [ . -a /tmp ]; echo $?; [ - -a /tmp ]; echo
$?'
1
0
ksh93: [: -: unknown operator
2
--
And
On Feb 29 2024, Martin D Kealey wrote:
> Should octal or hexadecimal be allowed (since they're easier to express
> powers of two)?
For this, $(( )) already provides enough support.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D
On Feb 21 2024, Christian Convey wrote:
> E.g., for limiting virtual memory to 8 gigabytes, the invocation is "ulimit
> -v 8388608", rather than something like "ulimit -v 8gb".
Or ulimit -v $((8*1024*1024))
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerp
ion
further.
> I think that escaping is needed after quote removal in shell-expand-line.
The function is called shell-expand-line, not
shell-expand-and-requote-line.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"An
s doing exactly what it is documented to do, that is do all
of the shell word expansions.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Jan 29 2024, Robert Elz wrote:
> I always wondered why the option was 'n'
n = next?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Dez 21 2023, Britton Kerin wrote:
> But if I do `complete git' at a new shell
That overwrites the completion spec for git (with the empty set, ie. no
completions at all). If you want to print existing completions, use
complete -p [NAME...].
--
Andreas Schwab, sch...@linux-m68k.org
t; content in a single string variable, which is a questionable idea in
> most programs.
For interactive use, $(< ...) is convenient and less verbose than the
alternatives.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
et the $0 special parameter.
$ bash -c 'echo $0 $2 $1' foo bar mumble
foo mumble bar
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Nov 25 2023, Emanuele Torre wrote:
> But the bash executable still does not contain the legal_ symbols:
If bash does not reference any of the symbols in lib/sh/compat.c there
is nothing pulling it in.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2
es) works fine in the original pipeline, without
> needing the redirect to /dev/null:
>
> $ echo foo | tee >(xsel -i) | tr o x
> fxx
That's because xsel is properly daemonizing itself, disconnecting from
its stdin/out/err.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprin
rrors only (default)
-quiet show informational messages on the terminal and run in the fore-
ground
-verbose
provide a running commentary of what xclip is doing
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
for multi-line commands that happen to contain matches for
re.
$ (sleep 100; printf $'\n[100]\n') &
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Nov 06 2023, Chet Ramey wrote:
> If nullglob is set, the non-matching pattern expands to the null string,
> which is removed by word splitting.
Since filename expansion happens after word splitting, this cannot be
true.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint
affect EOF
processing if the file is a pipe.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Aug 08 2023, Dale R. Worley wrote:
> More troublesome, I think, are several variable substitutions which
> include "!" followed by a name. But I doubt they're used much in
> interactive mode.
The history expansion is smart enough to not interfere with ${!var}.
; Actual output: bash: foo: unbound variable
This is expected. If the array is an indexed array, the subscript is an
arithmetic expression. When bash tries to evaluate the subscript, it
finds that foo is unbound.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 B
are implementing POSIX wrong.
> Except zsh.
Note that zsh by default is not a POSIX shell, and even in sh
compatibilty mode it doesn't strive to be POSIX compliant.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
sense when you want to know the
> time since the script started.
Even CLOCK_MONOTONIC can jump forward. The only requirement is that it
doesn't jump backward.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Mär 08 2023, Grisha Levit wrote:
> I think it might make sense to change code that looks at the value of
> PATH to explicitly treat an empty value as `.' so that all such
> behavior is consistent.
But an unset PATH is *not* the same as PATH=.
--
Andreas Schwab, SUSE Labs, sch.
According to
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/chmod.html
the symbolic mode can contain more than one action concatenated, for
example "g+r-x", which is the same as "g+r,g-x".
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196
On Feb 10 2023, Godmar Back wrote:
> It appears to be mistaking the wait status for the exit status if your
> hypothesis is correct.
Easy to verify:
$ sleep 10 && echo yes || echo $?
^Z
[1]+ Stopped sleep 10
148
--
Andreas Schwab, sch...@linux-m68k.org
GPG K
was that two divides are more costly than a
divide and a multiply (although nowadays, compilers will try to combine
the two divides if the target architecture has a divmod insn).
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC
On Jan 07 2023, Martin Schulte wrote:
> Hello!
>
> Am Sat, 07 Jan 2023 19:08:06 +0100 schrieb Andreas Schwab
> :
>
>> On Jan 07 2023, Greg Wooledge wrote:
>> ...
>> I think the original overflow can only happen if the argument of
>> intrand32 is bigger th
overflow, because if l
and h are unsigned, the computed value can never be negative, but it
becomes bigger than INT_MAX if 2836 * h is bigger than 16807 * l (the
unsigned result is computed modulo UINT_MAX+1).
I think the original overflow can only happen if the argument of
intrand32 is bigger th
On Dez 30 2022, Steffen Nurpmeso wrote:
> Not me!! Bash does it right for x=++x,
There is no right answer.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Dez 30 2022, Steffen Nurpmeso wrote:
> Andreas Schwab wrote in
> <87358xambe@igel.home>:
> |On Dez 29 2022, Alain D D Williams wrote:
> |> On Thu, Dec 29, 2022 at 10:30:09PM +0100, Steffen Nurpmeso wrote:
> |>
> |>> only clang warns on sequencing
t.c:7:11: warning: operation on ‘i’ may be undefined [-Wsequence-point]
i += j += i += j;
^~
t.c:11:11: warning: operation on ‘i’ may be undefined [-Wsequence-point]
i += j += i += i;
^~
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 E
On Dez 17 2022, ks1322 ks1322 wrote:
> When for loop output is piped to less and Ctrl+C is pressed, bash creates
> unexpected stopped job
That's because the process group receives SIGTTIN because less tries to
read from the terminal while it doesn't own it.
--
Andreas Schw
h from 1 to 10
>
>
> example:
>
> source test.sh
> sa 10 20
The function ignores the second argument.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
interruptable while running the
exit trap.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
o stop if from being interpreted as an assignment.
$ \a=b foo
hi
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
46d82c4c95423fb7e10e68eba52050e30ba3/vscode-remote-lock.root.899d46d82c4c95423fb7e10e68eba52050e30ba3)
> leaked on pvs invocation. Parent PID 3789: /usr/bin/bash
That looks more like the FD leak is in vscode (and bash just hands them
through).
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fin
string//\"/"}"
> printf '%s' "$string"
>
> previously outputs:
> xdotool type "sudo apt update"
>
> but now outputs:
> xdotool type "quot;sudo apt update"quot;
shopt -u patsub_replacement
--
Andr
EXIT
while :; do :; done
$ bash trap.sh | :
^C++ echo trap
trap.sh: line 1: echo: write error: Broken pipe
++ case a in
++ echo done
done
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Sep 05 2022, Julian Gilbey wrote:
> neither did using \(
> instead of (, and neither did putting spaces around the parentheses.
You need to do both.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now fo
; int c;
>> procenv_t oevalbuf;
>>
>> val = 0;
>> noeval = 0;
>> already_expanded = (flags&EXP_EXPANDED);
>
> You're mistaken. What you're seeing is the "K&R" coding style, which
> predates C89.
Note that the next revi
use a perl or python module in your program, you need a version of that
module that has been ported to the perl or python version in use.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Jul 09 2022, Steffen Nurpmeso wrote:
> $ bash -c 'I=3; echo "$((1?(I*=I):I+=I))";echo $I'
The third operand of ?: cannot contain an assignment expression, thus,
like in C, this is parsed as `(1?(I*=I):I)+=I'.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG
quot;<$(( +10+++I ))>"'
> <21>
A C compiler would parse all those expressions as post-increment applied
to a non-lvalue.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Jul 06 2022, Brad Hayes wrote:
> Perhaps something similar to PHP's __DIR__ and __FILE__ constants?
You can get that from $0.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
On Jun 30 2022, Constantine Bytensky wrote:
> 1. Make PS1="\[\e[K\]"
CSI K clears the whole line, clobbering the display region controlled by
readline, so that is not a valid use of control sequences.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D
s line, which I do not understand:
>
> .TH BASH_BUILTINS 1 "2004 Apr 20" "GNU Bash 5.0"
>
> The version number and the date stamp do not match each other at all.
The date has never been updated between commit 61deeb13 and f188aa6a.
--
Andreas Schwab, sch...@linu
On Jun 03 2022, Anna (cybertailor) Vyalkova wrote:
> 1. export CPPFLAGS="-DSYS_BASHRC='/home/sysrq/bash2/etc/bash/bashrc'"
SYS_BASHRC must be a string, not a multi-character constant.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D
performance.
Don't use the shell for performance critical tasks.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
#8 0x555b74bd in gen_compspec_completions (
cs=cs@entry=0x5588e0d0, cmd=cmd@entry=0x55640771 "compgen",
word=word@entry=0x556410e7 "", start=start@entry=0, end=end@entry=0,
foundp=foundp@entry=0x0) at pcomplete.c:1333
#9 0x555cbdb2 in
On Apr 15 2022, Martin Schulte wrote:
> I would either have expected to get PS2 and no error messages after
> entering the line starting with sleep
That's what I get when trying this in 5.2-beta.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510
history-search-backward? Hit the `echo 1' and accept-line?
Yes. Afterwards, I see this history:
1 echo 1
2 echo 24
3 echo 3
4 history
5 echo 1
6 history
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
).
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
e resposible for them.
$ sleep 1000 < <(cat /dev/null) &
[1] 10418
10418 pts/13 S 0:00 | \_ sleep 1000
10419 pts/13 Z 0:00 | | \_ [cat]
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
&q
because I moved over it.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Mär 20 2022, Michaelll Lee wrote:
> 1) $ PS1='---Test \\ \e[0m ---\\$ '
Read the manual about non-printing characters in the prompt.
https://www.gnu.org/software/bash/manual/html_node/Controlling-the-Prompt.html
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7
3
3
bash-5.2$ history
1 echo 1
2 echo 2
3 e
4 history
5 echo 2
6 history
7 echo 3
8 history
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Mär 11 2022, Ángel wrote:
> On 2022-03-09 at 20:35 +0100, Andreas Schwab wrote:
>> On Mär 09 2022, Chet Ramey wrote:
>>
>> > Ultimately, this comes down to gaps in the release engineering.
>>
>> That won't help, the container image often comes f
On Mär 09 2022, Chet Ramey wrote:
> Ultimately, this comes down to gaps in the release engineering.
That won't help, the container image often comes from a different source
than the docker package.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 25
sh
> assumed that access returning EPERM meant that the binary wasn't
> executable.
This is a recurring problem with docker, and all comes down to the
syscall filter returning a bogus errno. It happens every time a new
syscall is introduced.
--
Andreas Schwab, sch...@linux-m68k.org
1* echo 1
2 history
3 history
Type *2 (move to line 1), -> crash
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
ferent line instead.
bash-5.2$ history
1 echo 1
2 echo 2
3 echo 3
4 history
Now type e, , , 4,
, .
bash-5.2$ history
1 echo 1
2 echo 2
3* echo 34
4 history
5 echo 2
6 history
Now type *4 (move to line 3), -> crash
--
Andreas Schwab
On Feb 10 2022, Chet Ramey wrote:
> On 2/10/22 9:53 AM, Andreas Schwab wrote:
>> On Jan 21 2022, Chet Ramey wrote:
>>
>>> i. The non-incremental history searches now leave the current history offset
>>> at the position of the last matching history entry, like
ed by a single space character and followed by a
newline, on the standard output.
Options:
-ndo not append a newline
-eenable interpretation of the following backslash escapes
-Eexplicitly suppress interpretation of backslash escapes
--
Andreas Schwab, sch..
code
> foo="$(testCode)" || { echo "foo";} # --> Finished
There is no forgotten space in the latter line.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
use yank-last-arg to copy arguments from the preceding
line.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
y should it treated
differently in here-documents?
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
bash --posix -c 'read -t1
On Jan 21 2022, Lawrence Velázquez wrote:
> Depends what you consider to be an issue. Personally, I would be
> less than pleased if my whole terminal turned red just because I
> changed into a directory that happened to have a weird name.
Put $(tput sgr0) in PS1.
--
Andreas Sc
rectory stack, as it
would be displayed by the 'dirs' builtin invoked with the characters
following tilde in the tilde-prefix as an argument (*note The Directory
Stack::). If the tilde-prefix, sans the tilde, consists of a number
without a leading '+' or '-',
On Dez 17 2021, Jack Pearson wrote:
> PS1='$(tput sgr0)' # emit exit_attribute_mode capability string
Non-printable characters in the prompt must be bracketed by \[ \].
PS1='\[$(tput sgr0)\]'
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4
On Nov 17 2021, Michael J. Baars wrote:
> When -N stands for NEW, and touch (-am) gives you a new file
It doesn't. The file hasn't been modified after it was last read.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E
gt; "relatime" option. Which is documented thus:
AFAIK the "relatime" option has only an effect when the atime update is
triggered as a side effect of reading a file. Explicit inode
modifications via utime et.al. are always carried out independent of
that option.
Andreas.
--
Andre
FILE1 -nt FILE2 True if file1 is newer than file2 (according to
modification date).
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Nov 12 2021, Mischa Baars wrote:
> Using Fedora 32 (bash 5.0.17) this returns a true, while on Fedora 35 (bash
> 5.1.8) this returns a false:
> touch test; if [[ -N test ]]; then echo true; else echo false; fi;
What does `stat test' print respectively?
Andreas.
--
Andre
e considered a bug either way. Either command -p is
seen to modify PATH, then the hash should be reset afterwards, or
command -p is seen to not search PATH, then the hash should be left
alone.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 D
On Okt 11 2021, Alex fxmbsw7 Ratchev wrote:
> a sync in hope it syncs pipes
It doesn't. It just alters the timing.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
# NOT WORK!
>
> sh$ date | myfunc # NOT WORK!
>
>
> if i change like this. then this time work well
>
> sh$ date | { date > /dev/null; myfunc ;}
> yes
This depends on the left side of the pipe producing output faster than
the right side performing
ize 1
==31974==at 0x4006ED: main (in /home/andreas/a.out)
==31974== Address 0x521318a is 0 bytes after a block of size 218 alloc'd
==31974==at 0x4C338CF: realloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==31974==by 0x4006DE: main (in /home/andreas/a.out)
Andreas
ut the bash malloc
> because the default libc malloc probably doesn't do the bounds checking
> the bash malloc does, even without malloc debugging turned on.
If it's a buffer overflow, then valgrind should be able to catch it
(when bash is configured --without-bash-malloc). valgrind
e free function. The latter is seen by valgrind, the former
isn't, so it didn't track it. Thus the xmalloc, xrealloc, xfree macros
need to be disabled if valgrind is used.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9
nd everything works correctly.
Nope, it's undefined behaviour, as pointed out by valgrind.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
On Okt 04 2021, Chet Ramey wrote:
> On 10/4/21 4:34 AM, Andreas Schwab wrote:
>> On Okt 04 2021, Julien Moutinho wrote:
>>
>>> - bash crashes inside valgrind too,
>>> but apparently something different is happening
>>> because it crashes even wit
ic void
parse_prologue (string, flags, tag)
char *string;
@@ -247,7 +253,7 @@ parse_prologue (string, flags, tag)
add_unwind_protect (parser_restore_alias, (char *)NULL);
if (orig_string && ((flags & SEVAL_NOFREE) == 0))
-add_unwind_protect (xfree, orig_string);
+add_unwind_protec
"bash-builtins.7" is newer, and includes builtins like
> mapfile, which are not listed in the synopsis.
That's a bug with debian's packaging. The manpage from the bash sources
doesn't have that bug. Note that the bash sources do not contain any
section 7 manpages.
and to get the list of builtins to come up with the man command.
This happens automagically.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
1 - 100 of 711 matches
Mail list logo
