From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
To: 12989@debbugs.gnu.org
Subject: bug#12989: 24.3.50; buffer-file-type is not buffer-local
Date: Sun, 25 Nov 2012 12:58:01 +0900 [thread overview]
Message-ID: <87pq32pc52.wl%%xmue@d1.dion.ne.jp> (raw)
When I evaluate below code, Emacs-23 and trunk on Windows return the
different results.
(list
(setq buffer-file-type nil)
(progn
(let ((coding-system-for-read 'no-conversion))
;; Specify non-existing file.
(kill-buffer (find-file-noselect "c:/zzzzzzz")))
buffer-file-type))
-> (nil nil) (Emacs 23)
-> (nil t) (trunk)
And, if buffer-file-type is set to t, many file coding system
detections fail. Docstring says that buffer-file-type autmatically
becomes buffer-local, but that is not true on trunk.
> buffer-file-type is a variable defined in `subr.el'.
> Its value is nil
>
> Documentation:
> Non-nil if the visited file is a binary file.
> This variable is meaningful on MS-DOG and Windows NT.
> On those systems, it is automatically local in every buffer.
> On other systems, this variable is normally always nil.
Additionally, there is typo in docsstring of buffer-file-type.
> This variable is meaningful on MS-DOG and Windows NT.
~~~~~~
--
Kazuhiro Ito
next reply other threads:[~2012-11-25 3:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 3:58 Kazuhiro Ito [this message]
2012-11-25 16:50 ` bug#12989: 24.3.50; buffer-file-type is not buffer-local Eli Zaretskii
2012-11-25 21:16 ` Stefan Monnier
2012-11-25 21:26 ` Eli Zaretskii
2012-11-25 23:47 ` Richard Stallman
2012-11-26 0:47 ` Juanma Barranquero
2012-11-26 1:26 ` Stefan Monnier
2012-11-26 14:35 ` Kazuhiro Ito
2012-11-26 17:24 ` Eli Zaretskii
2013-02-09 13:01 ` Eli Zaretskii
2013-02-09 14:29 ` Stefan Monnier
2013-02-09 16:21 ` Eli Zaretskii
2013-02-09 16:08 ` Michael Albinus
2013-02-09 16:17 ` Eli Zaretskii
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=87pq32pc52.wl%%xmue@d1.dion.ne.jp \
--to=kzhr@d1.dion.ne.jp \
--cc=12989@debbugs.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 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.