> From: Pengji Zhang <m...@pengjiz.com> > Date: Thu, 29 Aug 2024 18:44:36 +0800 > > I found that function `fill-flowed-encode' would not fill texts > after the last hard newline in a buffer. To reproduce, run 'emacs > -Q' and then evaluate the following snippet: > > --8<---------------cut here---------------start------------->8--- > (with-current-buffer (get-buffer-create "*tmp-f=f*") > (use-hard-newlines) > (insert "1\n2") > (fill-flowed-encode) > (display-buffer (current-buffer))) > --8<---------------cut here---------------end--------------->8--- > > The expected output should be '1 2', but the actual is '1\n2'. > > The first patch changes this. > > Besides, I found that the test case > 'fill-flow-tests-fill-flowed-encode' in 'fill-flow-tests' does not > actually test the function 'fill-flowed-encode', which requires > 'use-hard-newlines'[1], and the test input does not cover some > behaviors of the function. The second patch improves it a bit. > > The second patch depends on the first one, without which the new > test will fail. So I decided to submit both together. Please let > me know if it is better to file another report.
Thanks. AFAICT, this function exists for the special case of decoding email messages. Can email messages have flowed-encoded text without a hard newline at the end? > PS I have sent an email to ass...@gnu.org, but have not got a > response yet. I think I have not finished the copyright assignment > process? No. Please ping them and CC me, so we could get your paperwork process going.
