[Bug 169092] text entered in external editor not passed to composer window

Garry Williams gtwilliams at gmail.com
Sat Apr 11 17:04:04 CEST 2009


--- Comment #10 from Garry Williams <gtwilliams gmail com>  2009-04-11 17:04:01 ---
This bug is not fixed for me.  Perhaps I have a version different from the
version you tested against.

I strace-d my kontact process and I can confirm that the E-mail program opens
the editor file before fork()ing the editor and then reads the contents of that
file to place in the composer screen.  Since the editor renames the file it was
passed and then creates a new file with the original name in which to write its
changes, the E-mail program simply reads the original contents without the
changes that the editor made.

I am using gvim as my external editor (and calling it with the -f option to
force it to run in the foreground without fork()ing).  I don't think this is
new behaviour for gvim -- it has always rename()ed the original file then
open()ed the original file name, creating a new file, to write its changes.

The fix is to assume that an external editor will create a new version of the
file and open it *after* the child process exits.  Kmail in KDE 3.5 did not
have this bug.

Here's my version information:

    $ kmail --version
    Qt: 4.5.0
    KDE: 4.2.2 (KDE 4.2.2)
    KMail: 1.11.2
    $ kontact --version
    Qt: 4.5.0
    KDE: 4.2.2 (KDE 4.2.2)
    Kontact: 1.4.2
    $ rpm -q kdepim

Please let me know what other information you require.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Kdepim-bugs mailing list