kmail doesn't respect cursor position in templates

Bug #149818 reported by Robin Sheat
6
Affects Status Importance Assigned to Milestone
KDE PIM
Fix Released
Medium
kdepim (Ubuntu)
Fix Released
Low
Unassigned
Declined for Gutsy by Henrik Nilsen Omma
Nominated for Hardy by Diwaker Gupta

Bug Description

kmail (4:3.5.7enterprise20070926-0ubuntu1 - from gutsy) seems to ignore the position of the cursor in templates. My reply-to template is the default:
%REM="Default reply template"%-
On %ODATEEN %OTIMELONGEN you wrote:
%QUOTE
%CURSOR

however, when you reply to a message (with content from that message selected or not), the cursor is always on the top line.

Revision history for this message
Pete (pete123) wrote :

I have a similar problem where the cursor can not be placed on the top line, I wish quoted text to appear at the end. In my case the cursor always appears on the second line down with %CURSOR defined at the top or left out completely.

Revision history for this message
Diwaker Gupta (diwaker) wrote :

I can confirm this problem. It's quite annoying. In fact I can't get the cursor to go ANYWHERE but the first line. I want to have the cursor at the bottom of the quoted message by default but it does NOT work.

Revision history for this message
Diwaker Gupta (diwaker) wrote :

Update: The bug only manifests itself if "Automatically insert signature" is checked in KMail preferences. Otherwise the templates honor cursor position. For some reason, while inserting the signature, the cursor position is reset and it is returned to the beginning of the first line, irrespective of %CURSOR in the template.

Changed in kdepim:
status: New → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined.
According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .
The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage .

Changed in kdepim:
importance: Undecided → Low
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This bug is fixed in KDE4.

Changed in kdepim:
status: Confirmed → Fix Released
Changed in kdepim:
status: Unknown → Fix Released
Changed in kdepim:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.