Bug 320280 - External Editor Launched Prematurely and Without Signature
Summary: External Editor Launched Prematurely and Without Signature
Status: RESOLVED DUPLICATE of bug 320111
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-25 23:56 UTC by Garry Williams
Modified: 2013-05-26 17:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Garry Williams 2013-05-25 23:56:29 UTC
Selecting Message -> New Message results in the composition window and immediately starts the external editor.  This is different from all previous releases.  I used to have to place the cursor into the edit area and hit any key to launch my editor.

Furthermore, the edit buffer I get omits my signature.  I have to type it in by hand.

If I save and exit my editor and then press a key in the composer area again, the full edit buffer, including my signature is loaded in my editor.

Reproducible: Always

Steps to Reproduce:
1.  Configure an external editor for the composer
2.  Either reply to a message or create a new message
3.
Actual Results:  
Composer window is displayed and the external editor is started immediately.  The editor's buffer does not contain the signature that appears in the composer window.

Expected Results:  
The composer window is started and the focus is in the headers.  I can complete the subject and headers and then move to the edit area and hit a key to start the external editor.  The external editor will contain my signature.

Platform Version 4.10.3

$ kmail --version
Qt: 4.8.4
KDE Development Platform: 4.10.3
KMail: 4.10.3
$ uname -a
Linux vfr 3.8.9-200.fc18.x86_64 #1 SMP Fri Apr 26 12:50:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$
Comment 1 Laurent Montel 2013-05-26 17:09:38 UTC

*** This bug has been marked as a duplicate of bug 320111 ***