Viewing Info Files - Introduce Top Menu also before end of buffer

Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

Dear Compeers

I am viewing Info files on Emacs 27.

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.

Regards
C*

RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Drew Adams]

> 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

Re: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

Will check it out.



> Sent: Friday, October 16, 2020 at 11:11 PM
> 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
>
> > 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
>
>

Re: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

If I can get breadcrumbs in the mode line it would work for me.

---------------------
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Friday, October 16, 2020 at 11:11 PM
> 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
>
> > 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
>

Re: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

I have put your code in one of my directories and put the following in my
init code. It works. But I have noticed that the Mouse Wheel Scroll does
not scroll through the buffer.

Are you aware of this?


( add-to-list 'load-path
    "/home/hagbard/GAdmSw/GungaDin--1.0/el/InfoPlus/"
)
(require 'info+)






> Sent: Friday, October 16, 2020 at 11:11 PM
> 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
>
> > 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
>
>

RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Drew Adams]

> I have put your code in one of my directories and put the following in my
> init code. It works. But I have noticed that the Mouse Wheel Scroll does
> not scroll through the buffer.

It does for me.  That is, it scrolls through the
current node's text - same as without info+.el.

Do you see the same thing if you start Emacs using
`emacs -Q' (no init file)?  If not, bisect your init
file, to find the culprit.  If yes, please send me
a step-by-step to repro the problem, starting from
`emacs -Q'.  Say what you see at each relevant
recipe step, and what you expected to see instead.

Re: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

I will need to scrutinise my Init File, then and see what is changing
things.


> Sent: Friday, October 16, 2020 at 11:58 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > I have put your code in one of my directories and put the following in my
> > init code. It works. But I have noticed that the Mouse Wheel Scroll does
> > not scroll through the buffer.
>
> It does for me.  That is, it scrolls through the
> current node's text - same as without info+.el.
>
> Do you see the same thing if you start Emacs using
> `emacs -Q' (no init file)?  If not, bisect your init
> file, to find the culprit.  If yes, please send me
> a step-by-step to repro the problem, starting from
> `emacs -Q'.  Say what you see at each relevant
> recipe step, and what you expected to see instead.
>
>

RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Drew Adams]

> I will need to scrutinise my Init File, then and see what is changing
> things.

Binary search is your friend in such a case.

E.g., comment out 1/2 of your init file, then
3/4, 7/8, 15/16, ... till you find the culprit.

You can use command `comment-region' to comment
out a block of code (the region).  With `C-u'
the same command uncomments the region.

This method is blind but efficient.  It seems
to go slowly at first, then picks up quickly.

You might think you can figure things out
instead, by looking at your init file.  And
that might be true.  But it is also often a
trap/gotcha - a dumb binary search can often
be more efficient.

Re: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

Have tried your suggestion and ended up commenting everything and
loading just your code. Scroll up gets me to the First Node I visited,
Scroll Down gets me to Last Node I visited.



> Sent: Saturday, October 17, 2020 at 1:08 AM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > I will need to scrutinise my Init File, then and see what is changing
> > things.
>
> Binary search is your friend in such a case.
>
> E.g., comment out 1/2 of your init file, then
> 3/4, 7/8, 15/16, ... till you find the culprit.
>
> You can use command `comment-region' to comment
> out a block of code (the region).  With `C-u'
> the same command uncomments the region.
>
> This method is blind but efficient.  It seems
> to go slowly at first, then picks up quickly.
>
> You might think you can figure things out
> instead, by looking at your init file.  And
> that might be true.  But it is also often a
> trap/gotcha - a dumb binary search can often
> be more efficient.
>

RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Drew Adams]

> Have tried your suggestion and ended up commenting everything and
> loading just your code. Scroll up gets me to the First Node I visited,
> Scroll Down gets me to Last Node I visited.

Aha.  Sorry for the trouble, and thanks for your report.

Yes, Info+ made these mouse key-bindings in `Info-mode-map':

(define-key Info-mode-map [mouse-4] 'Info-history-back)
(define-key Info-mode-map [mouse-5] 'Info-history-forward)

But that's not correct for systems that use `mouse-[45]'
events for mouse-wheel scrolling instead of for buttons
4 and 5.

Please try the latest info+.el version, which removes
those two bindings for systems like yours.
___

FYI, node `Misc Events' of the Elisp manual tells us:

 ‘(wheel-up POSITION)’
 ‘(wheel-down POSITION)’
  These kinds of event are generated by moving a mouse wheel....

  This kind of event is generated only on some kinds of systems.
  On some systems, ‘mouse-4’ and ‘mouse-5’ are used instead.
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
___

On other systems, such as MS Windows, it's common for
`mouse-[45]' to be used for browser etc. history Back
and Forward.  `mouse-4' and `mouse-5' (and `-6' etc.)
are legitimate mouse buttons, for mice that have more
than three buttons.  But on some systems those events
are co-opted, in Emacs at least, to represent mouse
wheel movement, so they can't be used for history
navigation.

Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

That's fantastic. Cheers. Will remove the RE.

---------------------
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Saturday, October 17, 2020 at 6:37 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > Have tried your suggestion and ended up commenting everything and
> > loading just your code. Scroll up gets me to the First Node I visited,
> > Scroll Down gets me to Last Node I visited.
> 
> Aha.  Sorry for the trouble, and thanks for your report.
> 
> Yes, Info+ made these mouse key-bindings in `Info-mode-map':
> 
> (define-key Info-mode-map [mouse-4] 'Info-history-back)
> (define-key Info-mode-map [mouse-5] 'Info-history-forward)
> 
> But that's not correct for systems that use `mouse-[45]'
> events for mouse-wheel scrolling instead of for buttons
> 4 and 5.
> 
> Please try the latest info+.el version, which removes
> those two bindings for systems like yours.
> ___
> 
> FYI, node `Misc Events' of the Elisp manual tells us:
> 
>  ‘(wheel-up POSITION)’
>  ‘(wheel-down POSITION)’
>   These kinds of event are generated by moving a mouse wheel....
> 
>   This kind of event is generated only on some kinds of systems.
>   On some systems, ‘mouse-4’ and ‘mouse-5’ are used instead.
>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ___
> 
> On other systems, such as MS Windows, it's common for
> `mouse-[45]' to be used for browser etc. history Back
> and Forward.  `mouse-4' and `mouse-5' (and `-6' etc.)
> are legitimate mouse buttons, for mice that have more
> than three buttons.  But on some systems those events
> are co-opted, in Emacs at least, to represent mouse
> wheel movement, so they can't be used for history
> navigation.
>

Re: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

So the lisp code can detect according to the system or there will be two versions
of the code, or whatever you have done.  I recommend putting a list of the keybindings
so one can easily figure it they interfere with those already set by the user.

---------------------
Christopher Dimech
Chief Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Saturday, October 17, 2020 at 6:37 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > Have tried your suggestion and ended up commenting everything and
> > loading just your code. Scroll up gets me to the First Node I visited,
> > Scroll Down gets me to Last Node I visited.
> 
> Aha.  Sorry for the trouble, and thanks for your report.
> 
> Yes, Info+ made these mouse key-bindings in `Info-mode-map':
> 
> (define-key Info-mode-map [mouse-4] 'Info-history-back)
> (define-key Info-mode-map [mouse-5] 'Info-history-forward)
> 
> But that's not correct for systems that use `mouse-[45]'
> events for mouse-wheel scrolling instead of for buttons
> 4 and 5.
> 
> Please try the latest info+.el version, which removes
> those two bindings for systems like yours.
> ___
> 
> FYI, node `Misc Events' of the Elisp manual tells us:
> 
>  ‘(wheel-up POSITION)’
>  ‘(wheel-down POSITION)’
>   These kinds of event are generated by moving a mouse wheel....
> 
>   This kind of event is generated only on some kinds of systems.
>   On some systems, ‘mouse-4’ and ‘mouse-5’ are used instead.
>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ___
> 
> On other systems, such as MS Windows, it's common for
> `mouse-[45]' to be used for browser etc. history Back
> and Forward.  `mouse-4' and `mouse-5' (and `-6' etc.)
> are legitimate mouse buttons, for mice that have more
> than three buttons.  But on some systems those events
> are co-opted, in Emacs at least, to represent mouse
> wheel movement, so they can't be used for history
> navigation.
>

RE: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer

[Drew Adams]

> I recommend putting a list of the keybindings so one can easily
> figure it they interfere with those already set by the user.

The keys that get bound depend on the context, options,
system etc.  Hard-coding doc that lists the bindings is
impractical.

`C-h b' shows you the currently available bindings.

This section of `info+.el' provides the key bindings,
so you can see what you're getting (assuming some
knowledge of reading Elisp):

 ;;; KEYS & MENUS ;;;;;;;;;;;;;;;;;;;;;;;;

If you use library `help-fns+.el' then `C-h M-k'
describes the bindings of a keymap.  For `Info-mode-map'
it describes the bindings for Info mode.

https://www.emacswiki.org/emacs/download/help-fns%2b.el

Viewing Info Files - Introduce Top Menu also before end of buffer

[Christopher Dimech]

That figures. You put bindings in one place. Incidentally, I am
writing an abbreviated manual for Elisp for release as Part of
the Gnu Project.

> Sent: Saturday, October 17, 2020 at 8:39 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: RE: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
>
> > I recommend putting a list of the keybindings so one can easily
> > figure it they interfere with those already set by the user.
>
> The keys that get bound depend on the context, options,
> system etc.  Hard-coding doc that lists the bindings is
> impractical.
>
> `C-h b' shows you the currently available bindings.
>
> This section of `info+.el' provides the key bindings,
> so you can see what you're getting (assuming some
> knowledge of reading Elisp):
>
>  ;;; KEYS & MENUS ;;;;;;;;;;;;;;;;;;;;;;;;
>
> If you use library `help-fns+.el' then `C-h M-k'
> describes the bindings of a keymap.  For `Info-mode-map'
> it describes the bindings for Info mode.
>
> https://www.emacswiki.org/emacs/download/help-fns%2b.el
>
>