From: Uday Reddy <usr.vm.rocks@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Cc: Uday Reddy <usr.vm.rocks@gmail.com>
Subject: Re: Emacs24 coding system problems
Date: Sun, 18 Nov 2012 19:06:28 +0000 [thread overview]
Message-ID: <20649.12724.125000.858979@gargle.gargle.HOWL> (raw)
In-Reply-To: <m2pq3w8km1.fsf@igel.home>, <83objg5qwk.fsf@gnu.org>, <jwvsj8i4spy.fsf-monnier+emacs@gnu.org>
Thanks for all the responses to this problem.
Andreas Schwab writes:
> Maybe you have a non-nil global value of coding-system-for-read, or
> file-coding-system-alist is clobbered somehow.
coding-system-for-read is nil. file-coding-system-alist looks the same as
the normal.
Eli Zaretskii writes:
> Or maybe the file in question has undecodeable byte sequences. Do you
> see "t" (which stands for 'raw-text') in the mode line, per chance?
The files are normal unicode text. But, they appear as sequences of octets,
as if they were visited by find-file-literally.
There is `t' in the modeline. `buffer-file-coding-system' is getting set to
`no-conversion', whereas normally it is `utf-8-unix'.
These files work fine in Emacs23. The problems only arise in Emacs24.
Stefan Monnier writes:
> Could you have set coding-system-for-read maybe?
coding-system-for-read is nil.
----
I have made some progress on narrowing down the problem. It happens only if
VM is used along with emacs-w3m for displaying the HTML content. Without
emacs-w3m, everything works fine.
Emacs-w3m evidently does a lot of manipulations with coding-systems. But,
they are only supposed to affect the interaction with the w3m sub-process.
So, it is not clear why they should affect the reading of files. Indeed, in
Emacs23 they didn't.
If you would like to take a look at what w3m does, here is a linke to the
main file:
http://cvs.namazu.org/Development/emacs-w3m/w3m.el?view=log
Cheers,
Uday
next prev parent reply other threads:[~2012-11-18 19:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 8:24 Emacs24 coding system problems Uday Reddy
2012-11-02 8:39 ` Andreas Schwab
2012-11-02 8:51 ` Eli Zaretskii
2012-11-02 8:56 ` Eli Zaretskii
2012-11-18 19:06 ` Uday Reddy [this message]
2012-11-18 21:07 ` Eli Zaretskii
2012-11-19 4:05 ` Stephen J. Turnbull
2012-11-19 8:43 ` Uday Reddy
2012-11-24 20:29 ` Stefan Monnier
2012-11-25 7:58 ` Uday Reddy
2012-11-25 10:44 ` Uday Reddy
2012-11-25 16:06 ` Eli Zaretskii
2012-11-25 20:36 ` Uday Reddy
2012-11-25 21:10 ` Eli Zaretskii
2012-11-25 11:48 ` Kazuhiro Ito
2012-11-25 19:58 ` Uday Reddy
2012-11-25 21:14 ` Eli Zaretskii
2012-11-25 23:37 ` Uday Reddy
2012-11-26 3:41 ` Eli Zaretskii
2012-11-26 8:30 ` Kazuhiro Ito
2012-11-26 17:16 ` Eli Zaretskii
2012-11-28 12:39 ` Kazuhiro Ito
2012-11-28 17:40 ` Eli Zaretskii
2012-11-28 21:16 ` Uday S Reddy
2012-11-29 3:46 ` Eli Zaretskii
2012-11-30 10:58 ` Uday Reddy
2012-11-30 13:40 ` Eli Zaretskii
2012-12-02 0:46 ` Emacs24 unpredictable behaviour [Was: coding system problems] Uday Reddy
2012-12-02 8:06 ` Andreas Schwab
2012-12-02 11:42 ` Uday Reddy
2012-11-09 17:01 ` Emacs24 coding system problems 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
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=20649.12724.125000.858979@gargle.gargle.HOWL \
--to=usr.vm.rocks@gmail.com \
--cc=emacs-devel@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 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).