David T-G ([EMAIL PROTECTED]) wrote:

[snip]

: % : If you can't figure out what's up, try setting mutt's $editor to a
: % : quickie script which calls vim and then waits for a keypress before
: % : exiting so that you can see any error messages that go by.
: % 
: % 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.
: 
: No, make sure that you *first* call vim and you *then* wait.  You need to
: see that vim is really called and see what messages, if any, it returns.

I overlooked the purpose of you suggestion. It doesn't
make any difference. The script doesn't get called.
 
[snip]

: Possbile, but not probable.  I'm still betting on a vim config, though a
: full /tmp as already mentioned might be a good place to start (my vim
: tmpdir is $HOME/tmp; I forget about the defaults sometimes :-)

I'll have a look at that. Thanks.


Regards,


Marc van Dongen

Reply via email to