Summary: | "Add Quote Characters" disrespects >%_ setting, always adds literal > | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Ronny Multrus <kde> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kde |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ronny Multrus
2009-02-02 20:01:17 UTC
Confirmed in kmail 1.11.90 (kde 4.2.62) svn trunk r923448. When I use "Add Quote Characters", it uses the Standars Template Quote Indicator, configured in the Message Composer Settings, instead of the Identity quote indicator, because I have checked the "Use custom Templates" in the identity. Both the default template's and the custom template's quote identicators are set to ">%_" for me and it still only indents with ">" rather than with "> "... This bug is still valid in KDE 4.2.3 and Qt 4.2.2 on Gentoo. SVN commit 1002105 by jarmond: Use correct quote prefix when replying, respecting global and identity settings. Also move formatString from kmmessage.cpp to stringutil.cpp Also create TemplatesConfiguration::configIdString function for obtaining custom template identifier. BUG: 182911 M +2 -2 identitydialog.cpp M +22 -6 kmcomposewin.cpp M +5 -0 kmcomposewin.h M +1 -57 kmmessage.cpp M +0 -3 kmmessage.h M +52 -0 stringutil.cpp M +7 -0 stringutil.h M +1 -1 templateparser.cpp M +8 -4 templatesconfiguration.cpp M +5 -0 templatesconfiguration.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1002105 I don't think this bug is fixed as I still have this in KDE 4.3.2 and Qt 4.5.3 on Gentoo. I enter "foo" into the mail text editor, select "foo" with the mouse, then select "Edit" > "Add Quote Characters" from the menu and the text becomes ">foo", though it should become "> foo". I have set my quote string to >%_ in all templates (grep QuoteString kmailrc|uniq yields QuoteString=>%_) so I think this bug is still valid. Now running KDE 4.4.5, this bug no longer appears for me, all is working fine. Thank you! |