From: sndanailov@gmail.com
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Sotir Danailov <sndanailov@gmail.com>
Subject: [PATCH] Documentation: process: Update email client instructions for Thunderbird
Date: Thu, 14 Jul 2022 00:50:37 +0200 [thread overview]
Message-ID: <20220713225037.1201-1-sndanailov@gmail.com> (raw)
From: Sotir Danailov <sndanailov@gmail.com>
The instructions don't match with the current Thunderbird interface.
Signed-off-by: Sotir Danailov <sndanailov@gmail.com>
---
Documentation/process/email-clients.rst | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/Documentation/process/email-clients.rst b/Documentation/process/email-clients.rst
index 16586f6cc888..243203d73272 100644
--- a/Documentation/process/email-clients.rst
+++ b/Documentation/process/email-clients.rst
@@ -280,10 +280,10 @@ to coerce it into behaving.
- Allow use of an external editor:
The easiest thing to do with Thunderbird and patches is to use an
"external editor" extension and then just use your favorite ``$EDITOR``
- for reading/merging patches into the body text. To do this, download
- and install the extension, then add a button for it using
- :menuselection:`View-->Toolbars-->Customize...` and finally just click on it
- when in the :menuselection:`Compose` dialog.
+ for reading/merging patches into the body text. To do this, download
+ and install the extension, then open :menuselection:`Write` and add a button
+ for it using :menuselection:`View-->Toolbars-->Customize...` and finally
+ just click on the new button when you wish to use the external editor.
Please note that "external editor" requires that your editor must not
fork, or in other words, the editor must not return before closing.
@@ -297,7 +297,8 @@ to coerce it into behaving.
To beat some sense out of the internal editor, do this:
- Edit your Thunderbird config settings so that it won't use ``format=flowed``.
- Go to :menuselection:`edit-->preferences-->advanced-->config editor` to bring up
+ Go to your main window and find the button for your main dropdown menu.
+ :menuselection:`Menu-->Preferences-->General-->Config Editor...` to bring up
the thunderbird's registry editor.
- Set ``mailnews.send_plaintext_flowed`` to ``false``
@@ -306,8 +307,6 @@ To beat some sense out of the internal editor, do this:
- :menuselection:`View-->Message Body As-->Plain Text`
-- :menuselection:`View-->Character Encoding-->Unicode (UTF-8)`
-
TkRat (GUI)
***********
--
2.37.0
next reply other threads:[~2022-07-13 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 22:50 sndanailov [this message]
2022-07-14 1:08 ` Bagas Sanjaya
2022-07-14 9:38 ` Sotir Danailov
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=20220713225037.1201-1-sndanailov@gmail.com \
--to=sndanailov@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®