[Users] [Bug 4798] New: Quoting wrong in at least format=flowed
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Wed Apr 17 17:30:26 UTC 2024
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4798
Bug ID: 4798
Summary: Quoting wrong in at least format=flowed
Product: Claws Mail
Version: 4.2.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: UI/Message View
Assignee: users at lists.claws-mail.org
Reporter: jazz_fan_ts at arcor.de
Created attachment 2476
-->
https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=2476&action=edit
screenshot of rendered text
It has become quite frequent that I see quoting errors. The symptom is that in
a message the line breaks of a previous message are incorrect, i.e., the line
is not broken before the quoting character. Consider this example. The message
header says:
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
The source code viewer shows this perfectly quoted snippet followed by a
response:
[Quote]
> Yet another point brought to light by the bcalc example relates to the
> coproc pid variable. The reset() function first closes the coproc pipe
> fds, then sleeps for a second to give the BC coproc some time to finish.
>
> An alternative might be to 'wait' for the coproc to finish (likely faster
> than sleeping for a second).
If the coproc has some problem and doesn't exit immediately, `wait' without
options will hang. That's why I opted for the sleep/kill-as-insurance
combo.
[/Quote]
I'll attach a screenshot of how it is rendered. Note that part of the response
is still rendered as a quotation even though there is an empty line between
quotation and response.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list