On Mon, Dec 03, 2007, Jonathan Guthrie wrote: > > Perhaps we shouldn't read these files and simply spawn the user's shell > > instead, or perhaps we should force bash. > > I don't know because I don't know why those files are read. While it > seems odd to me that aliasing ls would have an effect like that, that > implies that it's getting used by the login process somewhere and > perhaps replacing a raw "ls" with "/bin/ls" in whichever script it is > would be appropriate because it would bypass the aliasing.
The files are read to allow users to define stuff during their Xsession; it's the default upstream behavior and mimics RedHat distros. Perhaps the "alias" causes an error because the shell isn't interactive, but I don't think it would be used in Xsession itself. And even would it be, it's not a problem as ls --color or whatever only enables terminal control chars if run on a tty, not when the output is redirected to a file / pipe / whatever. -- Loïc Minier
