On 2018-08-24 18:04:29 -0700, Chris Waters wrote: > Ok, sorry that I can't remember *all* the ways that "su" without a > login option is broken. Even with that, it's still plenty broken, as > you have observed,
No, it had worked very well for *years*, until it got broken by dconf. That's dconf that introduced the breakage. > which is why the man page for su recommends *not using it without > the login option*. Because of the breakage introduced by dconf. The man page under Debian/stable doesn't even recommend that. BTW, the su with the login option is also broken since it keeps the TERM value without the TERMINFO one (most users don't need one, but this is still a bug). > There are simply too many things that can break when you have random > environment variables left around pointing who-knows-where. In general, that's the problem of the end user. The problem here is that environment variables are set behind his back. > Blaming emacs for a problem with su which is documented by the su man > page, though, is simply not reasonable. If you're going to insist on > using su instead of sudo, then it's your job to vet all your > environment variables to make sure you don't get this sort of > well-documented side effect. Which can affect all sorts of > programs--not just emacs. I've reported a bug against su: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907194 so that the environment is cleaned up more to work with these applications that introduced a breakage. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
