On Mon, 25 Nov 2024 at 00:21, Oğuz wrote:
> In another document, not the manual.
>
If my suggested addition does not belong in the manual, then neither does
*any* mention of "character class", nor indeed the entire existing
description of "regular expression". Please provide a patch that removes
On 11/24/24 12:59 PM, Bastien Roucariès wrote:
From debian:
https://lists.debian.org/debian-cross/2023/11/msg0.html
Hello,
While cross-building hurd-amd64 from linux, I got a subtle issue with
bash, that was leading to perl FTBFS very oddly.
The issue essentially was in bash/builtins/Mak
On Monday, November 25th, 2024 at 5:49 PM, Chet Ramey
wrote:
> On 11/23/24 9:29 PM, marcel.plch via Bug reports for the GNU Bourne Again
> SHell wrote:
>
> > Thank you for clarifictaion.
> >
> > Maybe adding an extra clarification to the bash manpage
> > in the Pattern Matching section would
On Mon, Nov 25, 2024, at 2:18 PM, marcel.plch via Bug reports for
the GNU Bourne Again SHell wrote:
> Not in one place the pattern "[[:space:]]" is mentioned.
Why should the "space" character class be called out in particular?
It's not special.
> If adding just one sentence containing "[[:space:]
On 11/25/24 2:18 PM, marcel.plch wrote:
On Monday, November 25th, 2024 at 5:49 PM, Chet Ramey
wrote:
On 11/23/24 9:29 PM, marcel.plch via Bug reports for the GNU Bourne Again
SHell wrote:
Thank you for clarifictaion.
Maybe adding an extra clarification to the bash manpage
in the Patte
On Mon, Nov 25, 2024, at 3:18 PM, Lawrence Velázquez wrote:
> $ unset IFS
Sorry, this is from an earlier draft in which I used $* to generate
the string of space-separated letters. I just forgot to remove it;
it isn't relevant for the example I actually sent.
--
vq
On 11/23/24 9:29 PM, marcel.plch via Bug reports for the GNU Bourne Again
SHell wrote:
Thank you for clarifictaion.
Maybe adding an extra clarification to the bash manpage
in the Pattern Matching section would be a good idea?
I can add some clarifying text, but I figure that the since this t
On 11/25/24 3:18 PM, Lawrence Velázquez wrote:
I'm not opposed to modest clarification, but mentioning "[[:class:]]"
would be misleading because it would give the impression that
character class expressions must occur alone within their bracket
expressions.
I added an example illustrating thi
When running 'help command' in the shell, the output contains:
> -vprint a description of COMMAND similar to the `type' builtin
> -Vprint a more verbose description of each COMMAND
This seems to be opposite to the actual behaviour of 'command', in which
'-V' (capital V) produc
On 11/25/24 2:35 PM, Andrew Davis wrote:
When running 'help command' in the shell, the output contains:
-vprint a description of COMMAND similar to the `type' builtin
-Vprint a more verbose description of each COMMAND
This seems to be opposite to the actual behaviour of
On Mon, Nov 25, 2024 at 5:07 AM Martin D Kealey wrote:
>
> How about this for a concrete proposal: let's split the current man page
> into a page per topic. The following list is alphabetical, though I should
> probably put it in some kind of narrative order.
>
>[...]
You mostly just reinvent
On 11/21/24 9:59 AM, Michael Tosch wrote:
Bash Version: 5.1
Patch Level: 16
Release Status: release
Description:
In bash I do
bash-5.1$
bash-5.1$ shopt| grep hist
cmdhist on
histappend off
histreedit off
histverify off
lithist on
bash-5.1$ echo $HISTTIMEFORMAT
%F %
On Tue, 26 Nov 2024 at 12:43, Lawrence Velázquez wrote:
> On Mon, Nov 25, 2024, at 9:03 PM, Martin D Kealey wrote:
> > I keep "similar" there because ‘type -a COMMAND’ shows all possible
> matches
> > for COMMAND, whereas ‘command -V’ only does that when COMMAND is NOT an
> > alias.
>
> I'm not s
Date:Tue, 26 Nov 2024 16:23:56 +1000
From:Martin D Kealey
Message-ID:
| I'm not convinced that ‘command’ should mention aliases at all, since
| ‘command -v "$var"’ should tell you what ‘"$var"’ will do.
| What it *won't* do is be expanded as an alias.
Absolut
On Mon, Nov 25, 2024, at 9:03 PM, Martin D Kealey wrote:
> I keep "similar" there because ‘type -a COMMAND’ shows all possible matches
> for COMMAND, whereas ‘command -V’ only does that when COMMAND is NOT an
> alias.
I'm not seeing that "command -V" behavior.
$ type -a bash
bash
On Mon, 25 Nov 2024 at 22:22, Zachary Santer wrote:
> On Mon, Nov 25, 2024 at 5:07 AM Martin D Kealey
> wrote:
> >
> > How about this for a concrete proposal: let's split the current man page
> > into a page per topic. The following list is alphabetical, though I
> should
> > probably put it in
~ $ 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
On Mon, Nov 25, 2024, at 9:47 PM, #!microsuxx wrote:
> V adds english text
That's not what I'm talking about.
--
vq
How about a counter-proposal: when not in POSIX mode, arguments that
correspond to numeric conversions in printf could be subject to normal
arithmetic evaluation, so that « printf %d '6*7' » will output “42”.
(Yes of course they should be subject to the single evaluation limit,
regardless of any s
On Tue, 26 Nov 2024 at 05:35, Andrew Davis wrote:
> When running 'help command' in the shell, the output contains:
>
> > -vprint a description of COMMAND similar to the `type' builtin
> > -Vprint a more verbose description of each COMMAND
>
> This seems to be opposite to the a
On Tuesday, November 26, 2024, Martin D Kealey
wrote:
> How about a counter-proposal: when not in POSIX mode, arguments that
> correspond to numeric conversions in printf could be subject to normal
> arithmetic evaluation, so that « printf %d '6*7' » will output “42”.
>
What's the point? Just wr
On Tuesday, November 26, 2024, Martin D Kealey
wrote:
>
> Would anyone object to adjusting the output of ‘command -V’ to be identical
> to ‘type -a’?
>
https://pubs.opengroup.org/onlinepubs/9799919799/utilities/command.html
--
Oğuz
22 matches
Mail list logo
