From: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>
Subject: [PATCH] Documentation/email-clients.txt: Fix one grammar mistake, add extra info about TB
Date: Mon, 9 Mar 2015 03:53:45 +0200 [thread overview]
Message-ID: <1425866025-21002-1-git-send-email-giedrius.statkevicius@gmail.com> (raw)
Fix one grammar mistake (Allows->Allow) and add extra information about
the external editor add-on of Thunderbird: the developer must make sure
that their editor doesn't fork (IOW it mustn't return before closing)
thus they should be careful how they configure the addon. Furthermore,
add a tip how to do it with gvim.
Signed-off-by: Giedrius Statkevičius <giedrius.statkevicius@gmail.com>
---
Documentation/email-clients.txt | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index eede608..064eed5 100644
--- a/Documentation/email-clients.txt
+++ b/Documentation/email-clients.txt
@@ -211,13 +211,20 @@ Thunderbird (GUI)
Thunderbird is an Outlook clone that likes to mangle text, but there are ways
to coerce it into behaving.
-- Allows use of an external editor:
+- 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
View->Toolbars->Customize... and finally just click on it when in the
Compose dialog.
+ Please note that "external editor" requires that your editor must not fork, or
+ in other words, the editor must not return before closing thus you may have to
+ pass additional flags or change the settings of your editor. Most notably if
+ you are using gvim then you must pass the -f option to gvim by putting
+ "/usr/bin/gvim -f" (if the binary is in /usr/bin) to the text editor field in
+ "external editor" settings. If you are using some other editor then please
+ read its manual to find out how to do this.
To beat some sense out of the internal editor, do this:
--
2.3.2
next reply other threads:[~2015-03-09 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 1:53 Giedrius Statkevičius [this message]
2015-03-19 20:54 ` 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=1425866025-21002-1-git-send-email-giedrius.statkevicius@gmail.com \
--to=giedrius.statkevicius@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®