Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: ot: displaying latin1 chars
Date: 22 Sep 2000 18:36:26 +0200	[thread overview]
Message-ID: <vafbsxgbcz9.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Norman Walsh's message of "22 Sep 2000 11:56:54 -0400"

On 22 Sep 2000, Norman Walsh wrote:

> Sorry for the off-topic message. I think I learned this trick on
> ding years ago and I've misplaced it...
> 
> I used to have a couple of lines of elisp in my .emacs file that
> mapped the 8-bit latin1 curly-quote characters to straight quotes so
> that I didn't see \xxx in my messages.
> 
> Can someone remind me of what those couple of lines are?

Well, `W d' invokes gnus-article-treat-dumbquotes which can be
customized to do this.  But why don't you tell Emacs that you would
like to see Latin-1 characters?  Are they missing from your font?

kai
-- 
I like BOTH kinds of music.



      reply	other threads:[~2000-09-22 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-22 15:56 Norman Walsh
2000-09-22 16:36 ` Kai Großjohann [this message]

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=vafbsxgbcz9.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).