From: Eli Zaretskii <eliz@gnu.org>
To: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
Cc: monnier@IRO.UMontreal.CA, usr.vm.rocks@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs24 coding system problems
Date: Mon, 26 Nov 2012 19:16:22 +0200 [thread overview]
Message-ID: <83txscxp21.fsf@gnu.org> (raw)
In-Reply-To: <87zk24davy.wl%%xmue@d1.dion.ne.jp>
> Date: Mon, 26 Nov 2012 17:30:25 +0900
> From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
> Cc: Uday Reddy <usr.vm.rocks@gmail.com>, monnier@IRO.UMontreal.CA,
> emacs-devel@gnu.org
>
> At Mon, 26 Nov 2012 05:41:57 +0200,
> Eli Zaretskii wrote:
> >
> > > Date: Sun, 25 Nov 2012 23:37:14 +0000
> > > From: Uday Reddy <usr.vm.rocks@gmail.com>
> > > Cc: Uday Reddy <usr.vm.rocks@gmail.com>,
> > > kzhr@d1.dion.ne.jp,
> > > monnier@IRO.UMontreal.CA,
> > > emacs-devel@gnu.org
> > >
> > > Hmm. Eli, it looks like you haven't read Kazuhiro's bug report closely.
> > > find-file-noselect is setting the variable.
> >
> > It does? Can you show me where?
>
> find-file-not-found-set-buffer-file-coding-system in lisp/dos-w32.el.
> lisp/dos-w32.el adds find-file-not-found-set-buffer-file-coding-system
> to find-file-not-found-functions.
Thanks. I committed to the emacs-24 branch changes that should fix
this. In particular, buffer-file-type should be buffer-local again.
Please test (revision 110960).
There are still places in the Lisp sources that set buffer-file-type,
but with that variable buffer local, this should no longer affect the
other buffers. I will remove the other references to this variable on
the trunk, as doing that might destabilize Emacs, due to the
complexities of the issues involved.
next prev parent reply other threads:[~2012-11-26 17:16 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
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 [this message]
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=83txscxp21.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kzhr@d1.dion.ne.jp \
--cc=monnier@IRO.UMontreal.CA \
--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).