Jay Berkenbilt <[EMAIL PROTECTED]> writes: > I don't actually see why this would make a difference -- I'd think > using the regular next-line function would still result in the same > buffer contents before sending. The buffer contents look right to me > before I send the message. It's only after I get my copy back that I > see the problem.
Gnus munges text properties before passing the message to sendmail, in particular it does things with hard newlines if it finds any. In this snapshot, if `next-line' needs to insert a newline character, it will insert a hard newline (i.e. a propertized newline character) instead of a regular newline. Message had been changed to do that as well and it so happened it made paragraph formatting disappear (the changes in Message were reverted, those in simple are still there). This is why I suspected the `next-line' function and related callers. > Maybe this bug is like the last one: something in my environment that > gets triggered over time breaks it. I'll have to keep an eye out for > this. If my hunch is correct, then it only happens if you insert newlines by moving in the buffer. Just inserting text wouldn't trigger it; it's possible that in some buffers, you don't get to insert hard newlines unintentionally. > I've wrapped paragraphs here with "p tags" to indicate where my > paragraph boundaries are in case this is the lucky message that gets > mangled. This message looks OK. -- ,''`. : :' : Romain Francoise <[EMAIL PROTECTED]> `. `' http://people.debian.org/~rfrancoise/ `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
