Re: RFC: MULE coding system docs and modeline indicators
Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes in xemacs-beta(a)xemacs.org:
...
It seems to me that *very* short and cryptic is the way to go, so
I'm
thinking about adding (a) balloon help giving full name of the coding
system plus
Balloon help is not necessarily going to be available. I would
consider putting it in the echo area instead, as we already do this
for several other mode-line fields.
(b) the "about the coding system" help function(s) from
the Mule menu to the modeline. (a) seems pretty uncontroversial; for
(b) should the functions be duplicate, moved, or don't do this?
My first thought is "don't do this", but I don't feel strongly one way
or another.
I'm also working on fixing the functions in
mule-base/mule-diag.el.
Again, if anybody's done anything in that direction, let me know. The
current description functions come in a verbose but very incomplete
form and a uninterpretably terse but complete form. I don't see any
use for the latter; I think that should be verbose, too. Comments?
There are two versions of this file, mule-test.el is the other one, I
believe. One of them was recently updated, so make a quick check
first to see whether or not the stuff you're trying to update has
already been updated or not.