Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds

Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds

[Robert J. Chassell]

Thank you, Handa-san.  With your recent fixes,
"-misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1" in
x-fixed-font-alist in emacs/lisp/mouse.el now works again!

Today's GNU Emacs CVS snapshot, Thu, 2008 May 22  09:56 UTC
GNU Emacs 23.0.60.5 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
started with

     /usr/local/src/emacs/src/emacs -Q -D \
     -fn "-Misc-Fixed-Medium-R-Normal--20-200-75-75-C-100-ISO8859-1"

-- 
    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc

Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds

[Kenichi Handa]

In article <m1Jz8RC-002K4NC@rattlesnake.com>, "Robert J. Chassell" <bob@rattlesnake.com> writes:

> Thank you, Handa-san.  With your recent fixes,
> "-misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1" in
> x-fixed-font-alist in emacs/lisp/mouse.el now works again!

That's good.  Thank you for testing.

BTW, I added a facility to log the font listing and
opening.  If you find a font problem, please try this:

(1) If your startup font is not correct, start Emacs as this:
  % EMACS_FONT_LOG=1 emacs ...arguments...
then type:
  M-x font-show-log RET

(2) Otherwise, start Emacs as usual, and type:
  ESC : (setq font-log nil) RET
then type
  M-x font-show-log RET

Don't keep using Emacs with font-logging on.  After you get
a proper log, please turn logging off by:
  ESC : (setq font-log t) RET

Please note that this facility is not yet matured.  Any idea
is welcome.

---
Kenichi Handa
handa@ni.aist.go.jp

Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds

[Kenichi Handa]

In article <m1JzGKI-002K4NC@rattlesnake.com>, "Robert J. Chassell" <bob@rattlesnake.com> writes:

>     Don't keep using Emacs with font-logging on.  After you get
>     a proper log, please turn logging off by:
>       ESC : (setq font-log t) RET

> Regardless of internal meanings, font-log should use `t' for on and
> `nil' for off.  It is confusing for users otherwise.

I just followed what Emacs does for buffer-undo-list; nil
for start new recording, t for not recording.

---
Kenichi Handa
handa@ni.aist.go.jp

Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds

[David Kastrup]

Kenichi Handa <handa@m17n.org> writes:

> In article <m1JzGKI-002K4NC@rattlesnake.com>, "Robert J. Chassell" <bob@rattlesnake.com> writes:
>
>>     Don't keep using Emacs with font-logging on.  After you get
>>     a proper log, please turn logging off by:
>>       ESC : (setq font-log t) RET
>
>> Regardless of internal meanings, font-log should use `t' for on and
>> `nil' for off.  It is confusing for users otherwise.
>
> I just followed what Emacs does for buffer-undo-list; nil
> for start new recording, t for not recording.

I find it perfectly reasonable.  "nil" does not mean "don't log the
fonts" but rather "the font-log contains nothing yet".  As you say: just
like buffer-undo-list.

If one can think up a good name ending with "-list", that would probably
help a bit.  I am not sure it is worth the trouble, though.  It is not
like this is exactly a user-accessible variable that people will change
and customize all the time.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

font-show-log facility

[Kenichi Handa]

In article <85prrdh6c1.fsf@lola.goethe.zz>, David Kastrup <dak@gnu.org> writes:

> > I just followed what Emacs does for buffer-undo-list; nil
> > for start new recording, t for not recording.

> I find it perfectly reasonable.  "nil" does not mean "don't log the
> fonts" but rather "the font-log contains nothing yet".  As you say: just
> like buffer-undo-list.

> If one can think up a good name ending with "-list", that would probably
> help a bit.  I am not sure it is worth the trouble, though.  It is not
> like this is exactly a user-accessible variable that people will change
> and customize all the time.

I'm now thinking about producing log only for a specific
character so that people can more easily find why that
character is shown by a specific font (or not shown).  For
that, perhaps I must change the current font-log to
font-log-list, and make font-log to control what kind of log
to produce as below:

    t: all log
  nil: suppresss logging
 char: log for that character
 list: for instance, `(open close)' logs only opening and closing

Another improvement is for font-show-log (in mule-diag.el).
Currently a list of each entry is truncated to at most 20
items.  It will be good to use text property to record the
truncated items on "..." and make it clickable to see all
the items.

Unfortunately I don't have a time to work on them at the
moment.  :-(

---
Kenichi Handa
handa@ni.aist.go.jp

Re: font-show-log facility

[Ted Zlatanov]

On Fri, 23 May 2008 16:24:00 +0900 Kenichi Handa <handa@m17n.org> wrote: 

KH> Another improvement is for font-show-log (in mule-diag.el).
KH> Currently a list of each entry is truncated to at most 20 items.  It
KH> will be good to use text property to record the truncated items on
KH> "..." and make it clickable to see all the items.

Could you consider something similar to gnus-message for font logging?
It lets the user specify a number (gnus-verbose), and log messages don't
show up unless their level is at or below gnus-verbose.  Thus you can
specify informational messages at level 9 but critical messages at level
0.  Your specific case may truncate at 20 for low verbosity but print
out everything for high verbosity.

Ted

font-log [was Re: -misc-fixed-medium-r-normal--20-*-*-*-c-100-iso8859-1 succeeds]

[Robert J. Chassell]

    I find it perfectly reasonable.  "nil" does not mean "don't log the
    fonts" but rather "the font-log contains nothing yet".  As you say: just
    like buffer-undo-list.

As a user, I pay attention to the command, `font-show-log', and
figure that the variable follows it.  

The variable `buffer-undo-list' is wrong, too; nil should turn the
feature off not on.  I understand the list contains nothing until you
enable it; but that is irrelevant.  Fortunately, neither variable is
evaluated often and their default global values can get away with
being t.

-- 
    Robert J. Chassell                          GnuPG Key ID: 004B4AC8
    bob@rattlesnake.com                         bob@gnu.org
    http://www.rattlesnake.com                  http://www.teak.cc

Re: font-log

[David Kastrup]

"Robert J. Chassell" <bob@rattlesnake.com> writes:

>     I find it perfectly reasonable.  "nil" does not mean "don't log
>     the fonts" but rather "the font-log contains nothing yet".  As you
>     say: just like buffer-undo-list.
>
> As a user, I pay attention to the command, `font-show-log', and
> figure that the variable follows it.

Variables have DOC strings for a reason.

> The variable `buffer-undo-list' is wrong, too; nil should turn the
> feature off not on.

Logging is on iff (listp buffer-undo-list) is t.

> I understand the list contains nothing until you enable it; but that
> is irrelevant.

The list must contain nothing _after_ you enabled it.  And that is
relevant.  So it is natural to mark the list as inactive by not making
it a list.  t accomplishes that.  nil doesn't.

> Fortunately, neither variable is evaluated often and their default
> global values can get away with being t.

The default global value for buffer-undo-list is nil.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum