From: Eli Zaretskii <eliz@gnu.org>
To: Uday Reddy <usr.vm.rocks@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs24 coding system problems
Date: Sun, 18 Nov 2012 23:07:21 +0200 [thread overview]
Message-ID: <83k3tizkl2.fsf@gnu.org> (raw)
In-Reply-To: <20649.12724.125000.858979@gargle.gargle.HOWL>
> Date: Sun, 18 Nov 2012 19:06:28 +0000
> From: Uday Reddy <usr.vm.rocks@gmail.com>
> Cc: Uday Reddy <usr.vm.rocks@gmail.com>
>
> Thanks for all the responses to this problem.
Sorry, I only remember very vaguely what this was about.
> > 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'.
't' is not no-conversion, 't' is raw-text. I wonder what is going on
there. Is there a file and a recipe from "emacs -Q" I could try to
reproduce this?
> 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.
If this is so complicated, then the only way to track this down is to
set breakpoints on the C level where buffer is decoded
(decode-coding-region, I guess), and see what happens there and why.
> 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
I doubt that this would be efficient, this stuff you are using
probably needs a lot of setup. If you cannot find a simple recipe,
then GDB is your friend.
next prev parent reply other threads:[~2012-11-18 21:07 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
2012-11-18 21:07 ` Eli Zaretskii [this message]
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=83k3tizkl2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=usr.vm.rocks@gmail.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.
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).