From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Stefan Monnier' <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: breadcrumbs for Info . . . . . .
Date: Sun, 15 Jun 2008 21:23:07 +0300 [thread overview]
Message-ID: <87prqir39k.fsf@jurta.org> (raw)
In-Reply-To: <00de01c8ceba$14b786f0$0200a8c0@us.oracle.com> (Drew Adams's message of "Sun, 15 Jun 2008 00:33:18 -0700")
>> > Better to show the information, wrapping it as needed -
>> > least surprise.
>>
>> IIUC, there is no problem now. The maximal level depth in
>> Texinfo is 4. So the current default breadcrumbs depth will
>> display all nodes for the maximal allowed depth.
>
> No. Four possible section levels + one top level = 5. As I said:
>
>> I'd suggest therefore getting rid of the depth user option
>> altogether. If you feel you must keep it, then please make
>> its default value 5, which includes everything (the 4 possible
>> section levels plus the top level). By default, at least,
>> no breadcrumb nodes should be elided.
>
> For example, visit node `General VC Options' in the Emacs manual. You get this
> with the default value of 4 for `Info-breadcrumbs-depth':
>
> > (emacs)Top > ... > Version Control > Customizing VC > General VC Options
This is not what I get with Info-breadcrumbs-depth = 4. Instead, I see
the full line like below:
> With a value of 5, you get this instead:
>
> (emacs)Top > Files > Version Control > Customizing VC > General VC Options
Now I incremented the default value to 4, so with the maximal depth of 4
actually there is no eliding now by default. In my tests, the length
of the breadcrumbs line rarely approaches 80 columns. However, if this
will cause a real problem then maybe instead of the number of nodes
Info-breadcrumbs-depth should specify the maximal length of the breadcrumbs
line measured in characters (this is easy to calculate).
> (Stefan has agreed to remove the initial `> '.)
OK, now removed the initial `> '.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-06-15 18:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 23:52 breadcrumbs for Info . . . . . Drew Adams
2008-06-11 0:04 ` Juri Linkov
2008-06-11 3:18 ` Drew Adams
2008-06-11 9:34 ` Juri Linkov
2008-06-11 13:46 ` Drew Adams
2008-06-11 18:59 ` Eli Zaretskii
2008-06-11 22:40 ` Juri Linkov
2008-06-12 2:01 ` Miles Bader
2008-06-12 22:42 ` Drew Adams
2008-06-13 3:27 ` Stefan Monnier
2008-06-13 6:34 ` Drew Adams
2008-06-13 8:43 ` Thien-Thi Nguyen
2008-06-13 13:55 ` Drew Adams
2008-06-13 17:17 ` Thien-Thi Nguyen
2008-06-13 17:52 ` Drew Adams
2008-06-13 19:55 ` Thien-Thi Nguyen
2008-06-13 20:10 ` Drew Adams
2008-06-15 18:19 ` Juri Linkov
2008-06-13 14:05 ` Stefan Monnier
2008-06-13 15:12 ` Drew Adams
2008-06-13 17:16 ` Stefan Monnier
2008-06-13 18:32 ` Thien-Thi Nguyen
2008-06-14 9:47 ` Eli Zaretskii
2008-06-14 10:01 ` Thien-Thi Nguyen
2008-06-13 13:58 ` Stefan Monnier
2008-06-13 15:11 ` Drew Adams
2008-06-13 20:34 ` Stefan Monnier
2008-06-13 22:11 ` Drew Adams
2008-06-13 22:44 ` Stefan Monnier
2008-06-14 9:45 ` Drew Adams
2008-06-14 16:16 ` Stefan Monnier
2008-06-14 17:24 ` Drew Adams
2008-06-14 18:04 ` Stefan Monnier
2008-06-15 0:27 ` Juri Linkov
2008-06-15 7:33 ` Drew Adams
2008-06-15 18:23 ` Juri Linkov [this message]
2008-06-15 19:46 ` Drew Adams
2008-06-15 0:28 ` Juri Linkov
2008-06-15 2:04 ` Stefan Monnier
2008-06-15 18:18 ` Juri Linkov
2008-06-15 7:55 ` Drew Adams
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=87prqir39k.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.