all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Kenichi Handa <handa@m17n.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: describe-categories (was: find-composition still depends on the composition property)
Date: Fri, 24 Oct 2008 02:44:03 +0300	[thread overview]
Message-ID: <87ej26rja6.fsf_-_@jurta.org> (raw)
In-Reply-To: <E1KsoqE-0006VL-Ty@etlken.m17n.org> (Kenichi Handa's message of "Thu, 23 Oct 2008 10:18:22 +0900")

>> By the way, I'd suggest to move the legend generated by
>> describe-categories to the beginning of the buffer, because the buffer
>> is huge and it does not say anywhere at the beginning that there's a
>> legend at the end.  Without the legend, the buffer looks like a large
>> pile of gibberish.
>
> The legend is longer than 40 lines.  If we put that at the
> head, it will occupy the whole first page, which I think is
> not that good.  Saying something like "See the end of the
> buffer for the legend." with "legend" clickable at the first
> line will be good.  What do you think?

The buffer is so long already (ca 27000 lines) that adding 40 lines
at the beginning doesn't make it worse.  Otherwise, it is not obvious
for the user that the legend is at the end, so it is easy to miss it.
A link to the legend will help, but it seems moving 40 lines to the
beginning is not a bad thing.

-- 
Juri Linkov
http://www.jurta.org/emacs/




  reply	other threads:[~2008-10-23 23:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 13:46 find-composition still depends on the composition property Juanma Barranquero
2008-09-05  1:24 ` Kenichi Handa
2008-10-19 23:15   ` Juri Linkov
2008-10-20  6:46     ` Kenichi Handa
2008-10-21 23:46       ` Juri Linkov
2008-10-22  1:17         ` Kenichi Handa
2008-10-22  4:25           ` Eli Zaretskii
2008-10-22  5:43             ` Kenichi Handa
2008-10-22  5:29           ` Kenichi Handa
2008-10-22 19:35             ` Eli Zaretskii
2008-10-23  1:18               ` Kenichi Handa
2008-10-23 23:44                 ` Juri Linkov [this message]
2008-10-25  1:37                   ` describe-categories (was: find-composition still depends on the composition property) Kenichi Handa
2008-10-25  8:33                     ` Eli Zaretskii
2008-10-23 23:48                 ` Word boundary " Juri Linkov
2008-10-25 18:03                   ` Eli Zaretskii
2008-10-26 13:36                     ` Kenichi Handa
2008-10-26 19:32                       ` Eli Zaretskii
2008-10-27  0:17                         ` Word boundary Miles Bader
2008-10-27  0:27                           ` Kenichi Handa
2008-10-27  4:12                             ` Eli Zaretskii
2008-10-27  5:16                             ` Miles Bader
2008-10-31  5:50                               ` Kenichi Handa
2008-10-26  8:15                   ` Word boundary (was: find-composition still depends on the composition property) Kenichi Handa

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=87ej26rja6.fsf_-_@jurta.org \
    --to=juri@jurta.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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.