Bug 308226 - Custom message templates for different identities don't work properly
Summary: Custom message templates for different identities don't work properly
Status: RESOLVED INTENTIONAL
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.9.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-11 09:58 UTC by Pal Körössy
Modified: 2012-11-15 20:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pal Körössy 2012-10-11 09:58:30 UTC
I set up custom templates for an identity in KMail by going to Setting/Configure_Kmail/Identities configuration dialog box and choosing Templates tab. Here I enable 'Use custom message templates for this identity' option and set up the following template for New messages:

%REM="Default new message template"%-
Hi %TOLNAME,
%BLANK
%CURSOR
%BLANK
%SIGNATURE

Then I compose a new message with this identity and choose a recipient, the last name of the recipient doesn't appear after 'Hi' in the message body. The cursor also  stands at a wrong position (after the signature).



Reproducible: Always

Steps to Reproduce:
1. Set up a custom New message template to an identity using . 
2. Try to compose a new message using this identity.

Actual Results:  
Neighter the lastname of  'to' field nor the cursor aren't displayed in the correct position.

Expected Results:  
Lastname and cursor should be at the right place according to the template.
Comment 1 Laurent Montel 2012-11-12 07:33:35 UTC
normal it's new message
=> template doesn't know "to" before to create it.
Comment 2 Pal Körössy 2012-11-15 20:43:06 UTC
(In reply to comment #1)
> normal it's new message
> => template doesn't know "to" before to create it.

You're right, the "name inserting" issue should be a wish instead. 
But cursor position is not at the right place, so this bug needs to be reopened.