Siteshwar Vashisht
Siteshwar Vashisht
fwiw `cat /etc/passwd | head -1 /dev/stdin` works as expected in the last beta release because `head` is enabled as builtin by default.
@etscrivner Thanks for taking on it. We would also appreciate any ideas/contributions to improve testing of parser and lexer.
@etscrivner Are you still interested in working on this issue ?
What is the motivation for this clean up ? Both bash and ksh support these variables and I think they should be retained. They should not be removed without discussions...
These variables are required by POSIX. You can read about them [here](http://pubs.opengroup.org/onlinepubs/9699919799.2008edition/utilities/sh.html).
This change will break POSIX compatibility, backward compatibility and user experience. I am personally against any such change. @krader1961 In general if anything goes against POSIX, it would be a...
Only related change I see in `RELEASE` file is: ``` 1308 10-08-11 Restored sh_fmtq() quoting to not quote NAME= in NAME=VALUE. ```
> > Currently `ksh` uses `vi` as default editing mode. > > That isn't true. It bases the default editing mode on the value of the `VISUAL` env var if...
> I'm okay with such a change but it can't be done until we've managed to make a stable release based on the ksh93v- work in progress code. When it...
> That isn't true. It bases the default editing mode on the value of the VISUAL env var if set else the EDITOR env var. I am one of the...