Re: Next word of alias to alias that end with is not checked for alias

2023-01-17 Thread Greg Wooledge
On Wed, Jan 18, 2023 at 02:45:29AM +0100, alex xmb ratchev wrote: > aliases are major essential part of functionality Disagree. > that u cant , and speak against , all the time , is only enemish nonsense Don't worry. They're not going anywhere. They're shit, but you will still be allowed to pl

Re: Next word of alias to alias that end with is not checked for alias

2023-01-17 Thread alex xmb ratchev
aliases are major essential part of functionality that u cant , and speak against , all the time , is only enemish nonsense On Wed, Jan 18, 2023, 2:43 AM Daniel Douglas wrote: > > Of course, all mention of aliases should really be removed from > > POSIX - aliases are even worse than "set -e". >

Re: Next word of alias to alias that end with is not checked for alias

2023-01-17 Thread Daniel Douglas
> Of course, all mention of aliases should really be removed from > POSIX - aliases are even worse than "set -e". It should be removed because the spec is full of inaccuracies and isn't useful. People that know enough to define the standard properly have other priorities clearly. I think many of u

Re: Possible bug in bash

2023-01-17 Thread Dale R. Worley
Greg Wooledge writes: > On Fri, May 13, 2022 at 10:36:56PM -0400, Dale R. Worley wrote: >> Reading your message, I believe that the rule can be stated as follows, >> and I'd thank you to check it: && and || have the same precedence, and >> they both "associate left". So for example >> x && y

Re: 回复: Possible bug in bash

2023-01-17 Thread Chet Ramey
On 1/17/23 2:21 AM, anonymous4feedb...@outlook.com wrote: I am sorry I made a mistake in the first email. Bash printed foo= bar=v and all other shells printed foo=v bar=. It turns out I am using --posix to enable alias in bash, and that’s what makes the difference. Thanks for the update; I fix