On 2/18/23 2:05 AM, Chet Ramey wrote:
If the shell reads an unquoted word in the right position, it checks
the word to see if it matches an alias name. If it matches, the shell
replaces the word [in the input] with the alias value, and reads that
value as if it had been read [from the input]
Date:Sat, 18 Feb 2023 12:21:49 +1000
From:Martin D Kealey
Message-ID:
| Both of these are clearly wrong,
Yes, which is why POSIX is changing. I am concerned less about
bash (and other shell) doc about the details of all of this,
more useful to suggest that
On 2/14/23 2:58 PM, Dale R. Worley wrote:
> Though I think by "keyword" he means "reserved word".
>
Yes, though in my defense, the bash man page liberally uses the term
"keyword".
On Fri, 17 Feb 2023 at 01:14, Chet Ramey wrote
> I think the issue is that he's applying a grammar interpretation
On 2/17/23 11:36 AM, Dale R. Worley wrote:
I think this change covers the case we're talking about, clarifies the
second sentence a bit, and seems to be well-aligned with the more
detailed truth:
Aliases allow a string to be substituted for a word when it is
used as the first
plus
if an alias definition ends with a space , when in use , further aliases
may get resolved ( substituded , before parsing code further )
On Fri, Feb 17, 2023, 5:37 PM Dale R. Worley wrote:
> Chet Ramey writes:
> > On 2/14/23 2:58 PM, Dale R. Worley wrote:
> Looking at the manual
Chet Ramey writes:
> On 2/14/23 2:58 PM, Dale R. Worley wrote:
Looking at the manual page, it says
ALIASES
Aliases allow a string to be substituted for a word when it is
used as
the first word of a simple command.
>>
>> Martin suggested (but
On Thu, Feb 16, 2023 at 6:31 PM Daniel Douglas wrote:
>
> On Thu, Feb 16, 2023 at 2:42 PM Greg Wooledge wrote:
> >
> > On Thu, Feb 16, 2023 at 07:21:14PM -, Syed Maaz wrote:
> > > Hey Team,
> > >
> > > I am a security researcher,I have found this vulnerability related to
> > > your
