workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gal Pressman <gal@nvidia.com>
To: Vincent Mailhol <mailhol@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Sotir Danailov" <sndanailov@gmail.com>,
	"Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>,
	"Paul McQuade" <paulmcquad@gmail.com>,
	"Jan Kiszka" <jan.kiszka@web.de>,
	"Randy Dunlap" <rdunlap@infradead.org>
Subject: Re: [PATCH v2] docs: process: email-client: add Thunderbird "Toggle Line Wrap" extension
Date: Tue, 6 Jan 2026 18:42:21 +0200	[thread overview]
Message-ID: <ce4af5ab-5dcf-4b67-b1af-f2288797e342@nvidia.com> (raw)
In-Reply-To: <20251226-docs_thunderbird-toggle-line-wrap-v2-1-aebb8c60025d@kernel.org>

On 26/12/2025 1:46, Vincent Mailhol wrote:
> While reading the git-format-patch manpages [1], I discovered the existence
> of the "Toggle Line Wrap" extension for Thunderbird which I found rather
> convenient.
> 
> Looking at the history, the ancestor of this extension was added to the
> documentation in commit e0e34e977a7c ("Documentation/email-clients.txt:
> update Thunderbird docs with wordwrap plugin") but then removed in commit
> f9a0974d3f70 ("Documentation: update thunderbird email client settings").
> 
> Extend the paragraph on Thunderbird's mailnews.wraplength register to
> mention the existence of the "Toggle Line Wrap" extension. The goal is not
> to create a war on what is the best option so make it clear that this is
> just an alternative.
> 
> [1] man git-format-patch -- §Thunderbird
> Link: https://git-scm.com/docs/git-format-patch#_thunderbird
> 
> Signed-off-by: Vincent Mailhol <mailhol@kernel.org>

I also use this extension and find it useful, good to have it documented.
Reviewed-by: Gal Pressman <gal@nvidia.com>

Btw, there are some tricks for when you want to wrap parts of the mail,
and leave other parts unwrapped. Useful when drafting a reply that
contains code snippets.

I don't remember the exact steps, but if you know it then it's good to
have it in here as well :).

  parent reply	other threads:[~2026-01-06 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25 23:46 Vincent Mailhol
2025-12-26  2:11 ` Randy Dunlap
2026-01-06 10:00 ` Sotir Danailov
2026-01-06 16:42 ` Gal Pressman [this message]
2026-01-06 17:04   ` Jan Kiszka
2026-01-06 21:38 ` Jonathan Corbet

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

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

  git send-email \
    --in-reply-to=ce4af5ab-5dcf-4b67-b1af-f2288797e342@nvidia.com \
    --to=gal@nvidia.com \
    --cc=corbet@lwn.net \
    --cc=giedrius.statkevicius@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol@kernel.org \
    --cc=paulmcquad@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=sndanailov@gmail.com \
    --cc=workflows@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox