On Tue, May 29, 2012 at 1:08 AM, Eric Blake wrote:
> On 05/27/2012 07:09 AM, Jon Seymour wrote:
>
>> I understand that the behaviour is unspecitied by POSIX - I didn't
>> know that before, but I know that now - thanks.
>>
>> That said, from the point of view of promoting interoperable scripts,
>>
On Mon, May 28, 2012 at 11:32 PM, John E. Malmberg wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=825751
>
> bash-4.2.24-1.fc16.i686
>
> Steps to Reproduce:
> 1. Activate a terminal running a bash shell
> 2. ls $HOME/
> 3.
>
> Actual results:
> ls \$HOME/
Already discussed for quite a few t
https://bugzilla.redhat.com/show_bug.cgi?id=825751
bash-4.2.24-1.fc16.i686
Steps to Reproduce:
1. Activate a terminal running a bash shell
2. ls $HOME/
3.
Actual results:
ls \$HOME/
I get the directory get expanded result on Bash 1.4.8 (VMS special
build) and on Bash 3.2.25(1)-release.
Rega
On 05/27/2012 07:09 AM, Jon Seymour wrote:
> I understand that the behaviour is unspecitied by POSIX - I didn't
> know that before, but I know that now - thanks.
>
> That said, from the point of view of promoting interoperable scripts,
> my view is that it (in an ideal world**) would be better if
On 05/27/2012 01:15 AM, Jon Seymour wrote:
> Is there a reason why bash doesn't treat == as an illegal test
> operator when running in POSIX mode?
Because POSIX doesn't forbid extensions. Furthermore, POSIX is
considering the standardization of ==:
http://austingroupbugs.net/view.php?id=375
at
