On Fri, May 06, 2011 at 12:46:40PM +0200, Claudio Jeker wrote:
> On Fri, May 06, 2011 at 11:37:53AM +0100, Stuart Henderson wrote:
> > sudo doesn't preserve ENV by default, so any shell settings (e.g.
> > set -o emacs) you might have in your ${ENV} file don't take effect.
> >
> > for people who like EDITOR=vi but also like "set -o emacs" in the
> > shell, this is really annoying; EDITOR/VISUAL are preserved, so the
> > (imo horrible) /bin/ksh "feature" of changing line editing mode
> > depending on setting of these variables takes priority.
> >
> > I'm not entirely convinced it's safe to add ENV to env_keep by
> > default but the only other workaround I've found (i.e. ln -s
> > /usr/bin/{vi,not_emacs} and setting VISUAL=/usr/bin/not_emacs)
> > is messy and annoying to do on multiple machines.
> >
> > anyone have other ideas or comments?
>
> I'm all for killing the ksh autoswitch feature. Whenever I end up on a
> system with EDITOR set to vi and ksh as shell I'm lost. If people like to
> use a specific mode they should add it to .profile.
I would somehow cope if it was removed, but I really like that feature
(which got added to tmux, too).
-0-
--
What this country needs is a good five cent ANYTHING!
