[Bug 211492] switching identity in composer window does not switch signature

[Brice Hunt]

https://bugs.kde.org/show_bug.cgi?id=211492


Brice Hunt <shoalcreek5 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shoalcreek5 at gmail.com




--- Comment #1 from Brice Hunt <shoalcreek5 gmail com>  2009-10-23 02:05:34 ---
UPDATE: I have determined more specifically when the behavior is exhibited.
Whenever using direct input from the "fortune" program to create the signature,
KMail gets stuck on that signature and won't change when the identity changes.
It also seems to exhibit the behavior when getting input from a bash script.
This has nothing to do if the identity is the default or not. Test this by
calling fortune directly for an identity's signature. Load the compose window
and try to change to and from the identity that call's fortune. Follow this up
by calling fortune from the command line and redirecting the output to a file,
like this:

$ fortune > sig.txt

Then change the identity to read the file or even run "cat sig.txt". Kmail
stops exhibiting the erratic behavior when changing identities. This tells me
that there is probably something in the direct output of the fortune program
(e.g. a stream control character) that KMail is picking up and inserting into
the signature, causing it to no longer recognize the signature properly. It
also seems to exhibit the behavior whenever running a bash script to extract
the signature.

I am not sure if this is something new with a more recent version of fortune or
if it is something that has changed with KMail. The workaround that I use is to
set a cron job that outputs a fortune cookie to a signature file every so
often. Then, from KMail, load the signature file for the identity that uses the
fortune cookie.

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