On 06/20/2012 07:16 AM, Eric Blake wrote: > do we know which shells suffer from this > POSIX non-compliance bug, and whether they are still in active use
Sorry, I don't know of a list of such shells. The problem is documented in the Autoconf manual, without listing shells. I have verified that the problem exists in Solaris 10 /bin/sh but not Solaris 11 /bin/sh, so it looks like we'll be living with this issue for a while, at least with /bin/sh. A brief but not exhaustive Google search also found zsh 3.1 <http://www.zsh.org/mla/workers/1999/msg00480.html>, ash circa 2002 <http://osdir.com/ml/emacs.devel/2002-04/msg00691.html>, fish circa 2009 <http://www.mail-archive.com/fish-users@lists.sourceforge.net/msg02205.html>. More generally, the problem is that often people use scripts in Perl or Python or whatnot to run a test, or run a test from a shell spawned by a terminal emulator, and these scripts or terminal emulators may execute chdir without updating PWD, so the shell starts up with the wrong PWD.
