all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: \201 chars showing up in buffer when using emacs from mutt
Date: Fri, 25 Mar 2005 02:12:27 +0100	[thread overview]
Message-ID: <89a257782f881a234ca54eddba84ee24@Web.DE> (raw)
In-Reply-To: <D8ECD0B6B0695144A6C2C000997D6BF4451DF6@esebe105.NOE.Nokia.com>


Am 24.03.2005 um 13:14 schrieb <Dirk-Jan.Binnema@nokia.com>:

> So does anyone have bullet proof settings such that I will never see 
> that
> dreaded \201 again? I am *almost* capabable of just removing them 
> trough some
> hook function when I start emacs, but taht seems very evil.
>

You have a few choices:

a) set in the file's header something like
	<comment> -*- coding: utf-8 -*-
    where <comment> is the comment character for this type of file

b) set file-coding-system-alist, auto-coding-alist -- You can customize 
this variable:
	 ("\\.tex\\'" iso-latin-9-unix . iso-latin-9-unix)

c) some of these:
      (set-language-environment 'Chinese-BIG5)
      (set-default-coding-systems 'euc-jp-unix)
      (set-keyboard-coding-system 'mac-roman)
      (set-clipboard-coding-system 'sjis-mac)
      (set-terminal-coding-system 'utf-8)
      (set-file-name-coding-system 'utf-8)

d) combinations of above

--
Greetings

   Pete

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
      -Benjamin Franklin, Historical Review of Pennsylvania.

  reply	other threads:[~2005-03-25  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 12:14 \201 chars showing up in buffer when using emacs from mutt Dirk-Jan.Binnema
2005-03-25  1:12 ` Peter Dyballa [this message]
     [not found] <mailman.114.1111668219.28103.help-gnu-emacs@gnu.org>
2005-03-25  0:39 ` B.T. Raven
  -- strict thread matches above, loose matches on Subject: below --
2005-03-29 11:09 Dirk-Jan.Binnema

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=89a257782f881a234ca54eddba84ee24@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.