From: Florian Weimer <fw@deneb.enyo.de>
Subject: [PATCH] Refer to emacs-mime docs from Gnus Charsets docs
Date: Thu, 15 Apr 2004 14:40:09 +0200 [thread overview]
Message-ID: <87hdvlxvme.fsf@deneb.enyo.de> (raw)
Is this okay to commit to mainline (provided that my CVS write access
still works)?
2004-04-15 Florian Weimer <fw@deneb.enyo.de>
* gnus.texi (Charsets): Point to relevant section in emacs-mime.
--- gnus.texi.~7.40.~ 2004-04-14 17:41:20.000000000 +0200
+++ gnus.texi 2004-04-15 14:05:28.000000000 +0200
@@ -9478,6 +9478,10 @@
@cindex coding system aliases
@cindex preferred charset
+@xref{Encoding Customization, , Encoding Customization, emacs-mime,
+The Emacs MIME Manual}, for additional variables that control which
+MIME charsets are used when sending messages.
+
Other charset tricks that may be useful, although not Gnus-specific:
If there are several @acronym{MIME} charsets that encode the same Emacs
--
Current mail filters: many dial-up/DSL/cable modem hosts, and the
following domains: postino.it, tiscali.co.uk, tiscali.cz, tiscali.it,
voila.fr.
next reply other threads:[~2004-04-15 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 12:40 Florian Weimer [this message]
2004-04-16 12:36 ` Reiner Steib
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=87hdvlxvme.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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;
as well as URLs for NNTP newsgroup(s).