Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Mark Hood <invalid@invalid.com>
Subject: Re: Strange charset selection when posting in iso-8859-1
Date: 05 Sep 2005 17:29:07 -0700	[thread overview]
Message-ID: <ygfr7c32g4s.fsf@invalid.com> (raw)
In-Reply-To: <87k6hvpevv.fsf-monnier+gnu.emacs.gnus@gnu.org>

Stefan Monnier <monnier@iro.umontreal.ca> writes:
> >   (setq-default enable-multibyte-characters nil)
> 
> If you have problems that seem to be fixed by the above, please use
> M-x report-emacs-bug RET to report them.

Ever since Emacs 20 I have had the following lines in my .emacs:

(setq default-enable-multibyte-characters nil)
(set-language-environment "Latin-1")

Otherwise I was constantly fighting problems with coding systems.  

I often work directly with binary files, but even files I thought were
supposed to be plain unibyte text would often cause Emacs V20 and
later to ask me strange and confusing questions when reading and
writing them.  Much of the large library of Emacs lisp I had developed
for myself was broken due to multibyte issues.

Really, it was much easier to put those two lines in my .emacs then to
try to sort out all those issues in attempts to make reproducible and
understandable bug reports.  My usage of Emacs is always within the
context of European languages, so unibyte mode works very well for me.

I was stuck on Emacs 19.34 for years until I discovered that those two
lines reliably put Emacs V20 and later into unibyte mode.

-- Mark Hood


  reply	other threads:[~2005-09-06  0:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 10:26 Peter Simons
2005-09-05 10:47 ` Reiner Steib
2005-09-05 11:21   ` Peter Simons
2005-09-05 18:08 ` Stefan Monnier
2005-09-06  0:29   ` Mark Hood [this message]
2005-09-06 13:20     ` Stefan Monnier
2005-09-06  4:41   ` Ivan Boldyrev
2005-09-06 13:21     ` Stefan Monnier
2005-09-06 12:37   ` Peter Simons
2005-09-06 13:26     ` Stefan Monnier
2005-09-06 14:01       ` Peter Simons
2005-09-09  4:14         ` Stefan Monnier
2005-09-09  8:21           ` Peter Simons
2005-09-09 13:15             ` Stefan Monnier

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=ygfr7c32g4s.fsf@invalid.com \
    --to=invalid@invalid.com \
    /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).