From: "Alan E. Davis" <lngndvs@gmail.com>
To: "Nikolaj Schumacher" <n_schumacher@web.de>,
"Peter Dyballa" <Peter_Dyballa@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unknown character encodings in .emacs
Date: Sun, 8 Jun 2008 08:36:16 +1000 [thread overview]
Message-ID: <7bef1f890806071536g54e7fffh231a34680f61975e@mail.gmail.com> (raw)
In-Reply-To: <m2tzg5ccox.fsf@nschum.de>
[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]
Thank you very much, Nikolaj and Peter:
As of now, I see:
GDM_LANG=en_US.UTF-8
LANG=en_US.UTF-8
Emacs can read .emacs.el now, I have incrementally deleted or commented out
parts that emacs tripped over when reading .emacs . I also placed the header
into the file that peter suggested.
;; -*- mode: Emacs-Lisp; coding: utf-8; -*-
Now the question comes up: what is the most appropriate coding system to be
using? I guess that is a matter for another post. Or is it? Should I be
using a two-byte language encoding at all? All characters I ordinarily use
are availalbe in a latin-1 encoding. The original reason I turned to a text
editor is the need for raw text input and output for language data (I was
working on a lexicon of Chuukese at the time).
I also was put off by the Windows encodings that emacs recommended when a
file was being saved. I avoid all proprietary file formats, so felt a bit
taken aback by that suggestion.
I have started to read more about this problem/issue. I have gotten away
with a sloppy .emacs.el file for a while, and sloppy conventions on
encoding. I need to look into it now. However, it is not something I would
choose to spend a great deal of time on: it's only of secondary importance
to my work.
It is suspicious that the problem only recently happened. The first
instance I discovered was a cut and paste from firefox of snippets for a
.emacs. I've been using this same .emacs.el (with many changes and
additions) for 15 years, all on GNU/Linux systems. I have had to adapt, but
nothing this radical.
Thank you again,
Alan
On Sun, Jun 8, 2008 at 4:38 AM, Nikolaj Schumacher <n_schumacher@web.de>
wrote:
> "Alan E. Davis" <lngndvs@gmail.com> wrote:
>
> > I'be been poking around, but don't have a clue where to start.
> > I never did understand encoding
>
> Well, that's a clue where to start, I suppose. :)
>
> > ("a`" "á" nil 1)
>
> Looks like the file has been written using UTF-8 and read using
> Latin-1. Try adding:
>
> (set-language-environment "UTF-8")
>
> However, I believe this shouldn't be necessary if the system is
> configured correctly. What OS do you use?
>
>
> regards,
> Nikolaj Schumacher
>
--
Alan Davis, Kagman High School, Saipan lngndvs@gmail.com
"It's never a matter of liking or disliking ..."
---Santa Ynez Chumash Medicine Man
"We have no art. We do everything as well as we can." ---Balinese saying
[-- Attachment #2: Type: text/html, Size: 3234 bytes --]
next prev parent reply other threads:[~2008-06-07 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 13:32 Unknown character encodings in .emacs Alan E. Davis
2008-06-07 18:34 ` Peter Dyballa
2008-06-07 18:38 ` Nikolaj Schumacher
2008-06-07 22:36 ` Alan E. Davis [this message]
2008-06-08 0:35 ` Alan E. Davis
[not found] <mailman.12844.1212845557.18990.help-gnu-emacs@gnu.org>
2008-06-07 14:04 ` Giorgos Keramidas
2008-06-07 23:09 ` Alan
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=7bef1f890806071536g54e7fffh231a34680f61975e@mail.gmail.com \
--to=lngndvs@gmail.com \
--cc=Peter_Dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=n_schumacher@web.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.
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.