unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Recursive `require' for feature `code-pages' (was: Additional autoload-coding-system entries in code-pages.el)
Date: Mon, 07 Mar 2005 16:18:04 +0100	[thread overview]
Message-ID: <v97jkjjxhv.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: v9hdjrmscp.fsf@marauder.physik.uni-ulm.de

[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]

On Fri, Mar 04 2005, Reiner Steib wrote:

> On Tue, Mar 01 2005, Stefan Monnier wrote:
>
>> Reiner Steib wrote:
>>> I propose to add autoloads for all iso-8859-* and windows-125* coding
>>> systems.  With these autoload, Gnus (and probably also other Emacs
>>> based mail and news readers) are able to display articles with the
>>> corresponding MIME charsets correctly.
> [...]
>> So those autoloads would indeed be very helpful,
>
> On Thu, Mar 03 2005, Richard Stallman wrote:
>
>> It seems good it me.  Handa, do you agree?
>
> As nobody seems to object, I have installed the patch.

There's a problem with this:

- Save the attached file as "Latin-7.txt".

- Start Emacs:
  $ LC_ALL=C emacs -Q Latin-7.txt

- C-h v buffer-file-coding-system RET gives:

,----
| buffer-file-coding-system's value is iso-latin-7
| Local in buffer Latin-7.txt; global value is nil
| Automatically becomes buffer-local when set in any fashion.
`----

But the non-ASCII characters are displayed as \377, and the mode line
doesn't display latin-7 but undecided.

- In the *Messages* buffer, I get:

   Error during redisplay:
   (error Recursive `require' for feature `code-pages') [9 times]

  `M-: (featurep 'code-pages) RET' gives t.

- When loading the file "Latin-7.txt" again, the non-ASCII characters
  are displayed correctly.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

[-- Attachment #2: Latin-7 aka iso-8859-13 sample --]
[-- Type: text/plain, Size: 231 bytes --]

;; Text in Latin-7 aka iso-8859-13 coding:
(require ’pc-mode) ;; Wrong: ’ instead of '
(pc-selection-mode)
(require ’tex-site) ;; Wrong: ’ instead of '
Grüße

;; Local Variables:
;; coding: iso-8859-13
;; End:


[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2005-03-07 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 13:50 Additional autoload-coding-system entries in code-pages.el Reiner Steib
2005-03-01 16:07 ` Stefan Monnier
2005-03-04 13:51   ` Reiner Steib
2005-03-07 15:18     ` Reiner Steib [this message]
2005-03-11 12:01       ` Recursive `require' for feature `code-pages' (was: Additional autoload-coding-system entries in code-pages.el) Kenichi Handa
2005-03-03 11:04 ` Additional autoload-coding-system entries in code-pages.el Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v97jkjjxhv.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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).