unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Bogdan Ruslanovich Drozd <bogdan.ruslanovich.drozd@yandex.com>,
	notmuch@notmuchmail.org
Subject: Re: [Bug] Notmuch Emacs Message Subject Can Be Truncated
Date: Wed, 21 Dec 2022 14:24:18 -0400	[thread overview]
Message-ID: <87sfh8r4x9.fsf@tethera.net> (raw)
In-Reply-To: <87y1r065wl.fsf@yandex.com>

Bogdan Ruslanovich Drozd <bogdan.ruslanovich.drozd@yandex.com> writes:

> In `notmuch-message-mode' subject can be truncated.
>
> How to reproduce:
>
> 1. Send an email message to yourself with the subject “test abcdf fdcba
>    12345 54321 qwerty ytrewq 09876 67890 =- -= zxcv vcxz m,./ /.,m asdf
>    fdsa ';lk kl;' qaz zaq ]'/ /'] йцукен некуцй ъхзщш шщзхъ” via Emacs
>    notmuch.
>
> 2. Get the message sent to yourself and view the message in Emacs
>    notmuch.  (In my case subject is truncated to “test abcdf fdcba 12345
>    54321 qwerty ytrewq 09876 67890 =- -= zxcv vcxz m,./ /.,m asdf fdsa
>    ';lk kl;' qaz zaq ]'/ /'] йцукен некуцй ъх”, i. e. “зщш шщзхъ” part
>    is lost.)
>
> If you couldn’t reproduce the bug, try eval (`M-:') `(setq
> rfc2047-encode-encoded-words nil)' and try to reproduce again.

I guess it is most likely the same bug discussed at

      https://nmbug.notmuchmail.org/nmweb/show/87wn9w4xus.fsf@thb.lt
      https://nmbug.notmuchmail.org/nmweb/show/87r0x8es8e.fsf@tethera.net
      
That one turns out to be a bug in the GMime library, fixed upstream:

    https://github.com/jstedfast/gmime/commit/1a33a55baafc73b0

As far as I know that's not part of any GMime release yet. 
\r

      reply	other threads:[~2022-12-21 18:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 17:08 [Bug] Notmuch Emacs Message Subject Can Be Truncated Bogdan Ruslanovich Drozd
2022-12-21 18:24 ` David Bremner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfh8r4x9.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=bogdan.ruslanovich.drozd@yandex.com \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).