Mikko Hänninen ([EMAIL PROTECTED]) wrote:
: Marc van Dongen <[EMAIL PROTECTED]> wrote on Wed, 27 Sep 2000:
: > I changed the editor setting to a script that prints something,
: > reads a line and then starts to edit. It doesn't seem to be
: > called when I press `e.' I still get the `unmodified' message.
:
: What doesn't get called when you press e, the script? (Just making
: sure I got that right..)
The script to which the editor setting in my .muttrc points doesn't
get called.
: correct. If it's correct, you can check that Mutt can execute it, with
: the ! command:
:
: !/path/to/your/editor/here
Good one. I hadn't thought of trying that. It fails....
Other shell commands fail as well....
: You don't say what the values are, so something to try (if you haven't
: yet) is to put full paths into the settings. Maybe our PATH setting
The path is set up properly. As a matter of fact, the editor
setting in the .muttrc is an absolute pathname.
: isn't set up the way you think it is, if you're launching Mutt via some
: graphical shell for instance. This shouldn't be a problem if it's
I'm launching mutt from the command-line prompt in a ``regular''
window.
Thanks.
Regards,
Marc van Dongen
