From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Mail body escape sequence fouls display
Date: Wed, 06 Apr 2005 17:12:58 +0200 [thread overview]
Message-ID: <v9sm24rlad.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <vxkzmwcgejr.fsf@mesquite.charcoal.com>
On Wed, Apr 06 2005, Karl Kleinpaste wrote:
> Since when does Gnus, or XEmacs in general, react to embedded escape
> sequences in text being displayed?
,----[ (info "(gnus)No Gnus") / GNUS-NEWS ]
| * ANSI SGR control sequences can be transformed using `W A'.
|
| ANSI sequences are used in some Chinese hierarchies for
| highlighting articles (`gnus-article-treat-ansi-sequences').
`----
Does it help to set `gnus-treat-ansi-sequences' to nil?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-04-06 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 14:34 Karl Kleinpaste
2005-04-06 15:12 ` Reiner Steib [this message]
2005-04-06 15:34 ` Karl Kleinpaste
2005-04-08 12:49 ` 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=v9sm24rlad.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).