From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>,
Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
Date: Fri, 16 Oct 2020 14:11:05 -0700 (PDT) [thread overview]
Message-ID: <ce8e4fe9-1aac-4d60-ab97-f37f268a4ae9@default> (raw)
In-Reply-To: <trinity-26662718-9833-4331-b405-391d90bedbd0-1602880626691@3c-app-mailcom-bs14>
> As example, on the first line one gets
>
> (gungadin-elisp-abbrev)Top > Introduction > Modifier-Keys
>
> This is good. However, if would be super to have this also at the end of the
> info buffer rather than having to scroll up every time after reading a
> section in a manual that can be relatively long.
Why is it that you want to see that? Just wondering.
FWIW, if you use library `info+.el' then, by default,
you see what you describe in the mode-line of the
Info window. And each part of those breadcrumbs is
clickable there, just as it is in the header-line.
This is controlled by minor mode
`Info-breadcrumbs-in-mode-line-mode'. You can toggle
the mode on/off anytime, including using menu-bar
menu Info > Toggle > Breadcrumbs In Mode Line.
When turned off, you see the usual mode-line.
You can also toggle whether the breadcrumbs are shown
in the Info header-line. That's on menu Info > Toggle
> Breadcrumbs In Node Header. When turned off, you
see instead two links in the header, for (1) the Info
file (manual) and (2) the current node in the manual.
https://www.emacswiki.org/emacs/InfoPlus
next prev parent reply other threads:[~2020-10-16 21:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 20:37 Viewing Info Files - Introduce Top Menu also before end of buffer Christopher Dimech
2020-10-16 21:11 ` Drew Adams [this message]
2020-10-16 21:18 ` Christopher Dimech
2020-10-16 21:23 ` Christopher Dimech
2020-10-16 21:46 ` Christopher Dimech
2020-10-16 21:58 ` Drew Adams
2020-10-16 22:58 ` Christopher Dimech
2020-10-16 23:08 ` Drew Adams
2020-10-16 23:51 ` Christopher Dimech
2020-10-17 16:37 ` Drew Adams
2020-10-17 18:01 ` Christopher Dimech
2020-10-17 18:05 ` RE: RE: RE: " Christopher Dimech
2020-10-17 18:39 ` Drew Adams
2020-10-17 19:03 ` Christopher Dimech
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce8e4fe9-1aac-4d60-ab97-f37f268a4ae9@default \
--to=drew.adams@oracle.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.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.
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).