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. I have read respective paragraphs in several Linux (and bash) books & docs and tried these commands in command line: EDITOR=/usr/bin/uemacs export EDITOR VISUAL=/usr/bin/uemacs export VISUAL FCEDIT=...etc ..and also in this form: export EDITOR=/usr/bin/uemacs And done this: set -o allexport And this: shopt -o emacs and set -o emacs ..to no avail. It is vim that starts every time. The above stuff I have tried first as a user, then also as root. I have also made in my home dir a .bashrc file and entered the export EDITOR=/usr/bin/uemacs (and so on) there. AND in my home dir's '.profile'file, before the "test -z [etc]" line there . Reboted, even. No help. in /etc I have (as root) made a file 'bash.bashrc.local' and entered the stuff there, too. So Where should one put these preferences (and the noclobber thing and the command to prevent CTRL-D closing the konsole window, and the possible commands for the prompt to automatically show pwd) ..in order them to work? The 'set' command tells that my shell is bin/bash, and that (!) my editor=/usr/bin/uemacs (and that the same editor is used for visual and fcedit). The uemacs editor does work, when started with the uemacs command from a console. A while a go I changed my login name in KDE - could that have made some mess? If I remove vim (=uninstall it) the 'edit foofile' command does nothing. The command 'shopt -o emacs' produces this response: emacs on whether I run it as root or in a user's terminal. Thanks on any hints on this supernaturalish thing! I'd like to learn vim but do not like a gun being put to my head this way... DW / Mike