From: "Štěpán Němec" <stepnem@gmail.com>
To: jidanni@jidanni.org
Cc: 6473@debbugs.gnu.org
Subject: bug#6473: describe-how-coding-system-was-decided-for-current-buffer
Date: Mon, 21 Jun 2010 11:41:14 +0200 [thread overview]
Message-ID: <87y6e8205h.fsf@gmail.com> (raw)
In-Reply-To: <8739wiymf3.fsf@jidanni.org> (jidanni@jidanni.org's message of "Sun, 20 Jun 2010 19:26:56 +0800")
jidanni@jidanni.org writes:
> In (info "(emacs) Recognize Coding") do mention how to make emacs say
> just why it chose the coding system it did.
>
> E.g., hide a NULL in a file,
> $ { LC_ALL=zh_TW.UTF-8 date; seq 99; echo -e \\0;} >| /tmp/oo
> $ emacs -Q /tmp/oo
> and watch as the user goes nuts trying to figure out why emacs is not
> showing the file in the usual character set anymore.
>
> Indeed, there should be a
> describe-how-coding-system-was-decided-for-current-buffer
> command.
Well, I doubt there is any way, in general. I see here a broader problem
-- I often find myself wondering where/how a variable was set to its
current value. Something like (or preferably even better than) Vim's
:verbose command, which does precisely that (i.e. reports "Last set from
<filenameorsimilar>" along with the value), would be great. I'm hoping
the apparently-being-worked-upon watch point functionality could be of
some help here.
(Sorry if this seems like hijacking this bug report to you, I just felt
it was relevant.)
Štěpán
next prev parent reply other threads:[~2010-06-21 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 11:26 bug#6473: describe-how-coding-system-was-decided-for-current-buffer jidanni
2010-06-21 9:41 ` Štěpán Němec [this message]
2012-02-22 1:48 ` Glenn Morris
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=87y6e8205h.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=6473@debbugs.gnu.org \
--cc=jidanni@jidanni.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).