On Tue, Nov 22, 2022, at 2:20 AM, Ulrich Windl wrote:
> AFAIK, bold means "literal" and non-bold or specifically italics means
> "placeholder".
> From man-pages(7):
>
> "(...) boldface is used for as-is text and italics are used to indicate
> replaceable arguments. Brackets ([]) surround optional
>>> Lawrence Velázquez schrieb am 22.11.2022 um 05:06 in
Nachricht
:
[...]
>> Despite of that only ":-" is typeset in bold; shouldn't "${" and "}" be
>> typeset in bold, too?
>
> I don't know. It seems like boldface is used to highlight the parts
> that are unique to each form.
AFAIK, bold mea
On Mon, Nov 21, 2022, at 4:38 AM, Ulrich Windl wrote:
> But from the syntax "${parameter:-word}" it's not really obvious that the
> colon may be omitted.
You're not wrong.
> Should it be "${parameter[:]-word}" (with non-bold square brackets) instead
> (as for "name=[value]")?
No, that would be e
On 11/21/22 9:32 PM, Koichi Murase wrote:
`git bisect' finds the following commit (2022-01-31) which introduced
the behavior:
commit b325b0e96bd05c76bbfc4d60d0707fc93d58f03f (HEAD, refs/bisect/bad)
execute_cmd.c
- execute_in_subshell: call optimize_subshell_command for (list)
2022年11月22日(火) 9:36 Emanuele Torre :
> No, actually later, I said that it has probably been introduced earlier
> since I tried running 'time (sleep 1)' in a version of bash that
> preceeds that change (namely 6711d2dc7793ed3d35e91b2bd4ecbdfccfcf469f
> (2022-10-24)), and it still didn't print the ti
On 11/21/22 7:36 PM, Emanuele Torre wrote:
On Mon, Nov 21, 2022 at 07:07:08PM -0500, d...@dabe.com wrote:
emanuele6 suspects it has to do with
https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00107.html
No, actually later, I said that it has probably been introduced earlier
sinc
On Mon, Nov 21, 2022 at 07:07:08PM -0500, d...@dabe.com wrote:
> emanuele6 suspects it has to do with
> https://lists.gnu.org/archive/html/bug-bash/2022-10/msg00107.html
No, actually later, I said that it has probably been introduced earlier
since I tried running 'time (sleep 1)' in a versi
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin22.1.0
Compiler: clang
Compilation CFLAGS: -DSSH_SOURCE_BASHRC
uname output: Darwin triton.parabon.com 22.1.0 Darwin Kernel Version 22.1.0:
Sun Oct 9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_6
On 11/20/22 8:02 AM, Ralf Oehler wrote:
Bash Version: 5.2
Patch Level: 2
Release Status: release
Description:
I want to read an associative array. Like so: y="${aa[$i]}"
If aa contains the element queried, then everything works as expected
If aa does not contain such an
On Mon, Nov 21, 2022 at 3:45 PM Chet Ramey wrote:
> On 11/19/22 3:08 PM, Frode Nordahl wrote:
>
> >>> For some reason, when the 'ovn-controller incremental processing' test
> is
> >>> executed using bash 5.2 on Debian experimental or Ubuntu
> Kinetic/Lunar, the
> >>> `eval` [0] in the `counter_de
On 11/19/22 3:08 PM, Frode Nordahl wrote:
For some reason, when the 'ovn-controller incremental processing' test is
executed using bash 5.2 on Debian experimental or Ubuntu Kinetic/Lunar, the
`eval` [0] in the `counter_delta_` function misinterprets successful execution
of commands [1], leading
Sorry, I actually miussed it, as the typical usage pattern for lengthy manual
pages is like searching for ":-" and looking what is standing there:
${parameter:-word}
Use Default Values. If parameter is unset or null, the
expan-
sion of word is substituted. Ot
12 matches
Mail list logo
