On Thu, 20 Jan 2005 11:50:43 -0600, Danny Sauer
Randall wrote regarding 'Re: [SLE] Vim kidnapped my bash editor - pls help me get (u)emacs back' on Thu, Jan 20 at 11:34:
Danny,
On Thursday 20 January 2005 09:20, Danny Sauer wrote:
Dumb wrote regarding '[SLE] Vim kidnapped my bash editor - pls help me get (u)emacs back' on Thu, Jan 20 at 10:03:
Hi,
How does one force bash to use emacs (or uemacs) for editing, in Suse 9.2? (I mean in a KDE's konsole window.)
A while ago I installed some VIM and emacs packages and uemacs; among them kvim. (Kvim I later uninstalled.)
Now, for some reason, when I try to edit anything and type in bash for example 'edit myfile', the editor that starts is vim 6.3.
[...]
Must... ignore.. urge to suggest that your computer is telling you that the bloated pig of an editor is crushing it, and that vim is clearly much more friendly to the hardware... ;)
Now, now. Emacs is a venerable editor. I wish I could say I knew how to use it, but I'm a Vi / Vim guy from way back.
Back when there wasn't enough memory / CPU available to get emacs into memory *and* have room for another open filehandle? ;)
[...]
vim". Therefore, you probably want to fix that by typing ln -sf `which emacs` /usr/bin/edit Though you'll have to run that as root in order to write to /usr/bin.
This is not advisable, I'd say. Witness:
% rpm -qf /usr/bin/edit vim-6.2-233
So, "/usr/bin/edit" is part of the Vim package and altering it is, in effect, breaking that package installation and will get put right the next time that package is updated or repaired.
Probably he should simply not use "edit" to invoke his own editor. That, or he should put an alias in his "~/.bashrc" or create a different script or symlink in his "~/bin/" directory.
That's weird. How in the heck was "edit" working before, then? I went through and dumped the contents of all the packages in my 9.2 ftp mirror (I'm not real busy right now), and the file only exists in the vim package. I suppose that's as expected, so there aren't file conflicts, but I wonder how it was working before? You're right, though - the alias probably is a better fix. ...
Thanks for you input, Making an alias was the thing to do. Now I know how to choose the editor myself and lot be forced to use anything. Both vim and emacs (or uemacs or em) are interesting. (But I guess I'll have to cut the wires to my PC's speaker as the beeping of vim or emacs drives me up the wall.) Thank you guys! dw