Summary: | kmail with emacs as external editor: text in emacs doesn't make it into composer (is lost) when emacs is closed | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Ben Barrowes <barrowes> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kollix |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ben Barrowes
2009-07-30 16:23:14 UTC
Confirmed with gvim. Does also not work. I'm going to see why. With gvim you need to pass the extra option "-f" which tells it not to fork into the background. If that option is not given, gvim starts another subprocess and terminates the just started one, which is why kmail thinks the editor has already been closed. Can you check if emacs, gedit has a similar commandline option, please ? Perhaps this isn't much help, but, gedit has a very brief man/--help that says nothing about forking. The emacs man also doesn't mention forking or running in the background. Both processes execute in the foreground from a shell. ok, I now installed emacs and xemacs, and when configuring "emacs %f" or "xemacs %f" the editing works as expected. I tried with KDE-4.3 RC3 and with KDE4.4/current trunk. Didn't test gedit (too much gnome libs to install). As it works for me, I'll close it for now. If you can see the problem still with 4.3, please reopen. |