* bug#6473: describe-how-coding-system-was-decided-for-current-buffer
@ 2010-06-20 11:26 jidanni
2010-06-21 9:41 ` Štěpán Němec
0 siblings, 1 reply; 3+ messages in thread
From: jidanni @ 2010-06-20 11:26 UTC (permalink / raw)
To: 6473
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#6473: describe-how-coding-system-was-decided-for-current-buffer
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
2012-02-22 1:48 ` Glenn Morris
0 siblings, 1 reply; 3+ messages in thread
From: Štěpán Němec @ 2010-06-21 9:41 UTC (permalink / raw)
To: jidanni; +Cc: 6473
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#6473: describe-how-coding-system-was-decided-for-current-buffer
2010-06-21 9:41 ` Štěpán Němec
@ 2012-02-22 1:48 ` Glenn Morris
0 siblings, 0 replies; 3+ messages in thread
From: Glenn Morris @ 2012-02-22 1:48 UTC (permalink / raw)
To: 6473-done
tags 6473 wontfix
stop
I see no prospect of this being implemented. Closing as wontfix.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-02-22 1:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2012-02-22 1:48 ` Glenn Morris
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).