| Summary: | KNode composer silently gobbles line-terminal characters in message body | ||
|---|---|---|---|
| Product: | [Unmaintained] knode | Reporter: | Tristan Miller <psychonaut> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Tristan Miller
2004-01-11 17:36:16 UTC
This has been fixed a few months ago. We no longer strip the ending '/'. Either this bug was fixed only for the special case of slash characters, or it has reappeared in KNode 0.8.1. Other non-alphanumeric characters which KNode considers as candidates for soft line breaks get silently gobbled. It's a fairly serious bug, as it prevents people from posting source code into newsgroup messages.
Here's an example of how you can reproduce the behaviour:
0) Settings->Configure KNode->Posting News->Composer->Word wrap at column: 75
1) Article->Post to Newsgroup
2) Enter headers as appropriate
3) Select the following line with the mouse and paste it into the message body:
\def\CC{{C\nolinebreak[4]\hspace{-.05em}\raisebox{.35ex}{\scriptsize\bf++}}}
KNode splits this line between the characters `}{'. Note that KNode will not permit you to cursor to the end of the first line. The furthest you can go is the penultimate character. Clearly a related bug...
4) File->Send Now
5) Retrieve new articles and view the article you just posted, or view it in the `Sent' folder. Note that the last character of the first line (i.e., the `}' of the `}{' is missing.
The bug also seems to be triggered with other characters after which KNode performs soft line breaks, such as `)'.
Confirming bug (as described in Comment #2) still exists in KDE 3.4. Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. |