Bug 315431 - Cursor should be above signature while replying in kmail2
Summary: Cursor should be above signature while replying in kmail2
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.0
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-19 09:26 UTC by Ruchir Brahmbhatt
Modified: 2017-01-07 22:46 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 Ruchir Brahmbhatt 2013-02-19 09:26:04 UTC
When there is a signature configured and it is set to be on top of reply, when replying, cursor is positioned below signature instead of above signature so manually have to move the cursor on top in order to start typing reply.

Workaround:
Modify default identity template and keep reply template as below.
%CURSOR
%SIGNATURE
%REM="Default reply all template"%-
----------  Original Message  ----------
From: %OFROMADDR
%OADDRESSEESADDR
Subject: %OFULLSUBJECT
Date: %ODATE, %OTIMELONG

%TEXT
-----------------------------------------

Reproducible: Always

Steps to Reproduce:
1. Set one default signature.
2. Configure kmail to insert signature before quoted reply.
3. Reply any message.
Actual Results:  
Cursor is below signature.

Expected Results:  
Cursor should be above signature.
Comment 1 Henrik Hudson 2013-12-31 22:22:33 UTC
Can confirm the same problem in 4.12  However, using the %SIGNATURE in the template creates a blank email in 4.12 and the REPLY info is stripped.
Comment 2 Pierre 2014-01-15 14:58:58 UTC
Great. Instead of fixing the old bug a new bug turns up which breaks the workaround to the old bug.
https://bugs.kde.org/show_bug.cgi?id=329995
Comment 3 Denis Kurz 2016-09-24 18:01:31 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:46:42 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.