From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs Lisp Reference Manual
Date: Sat, 28 Nov 2020 17:17:13 +0100 [thread overview]
Message-ID: <trinity-10ac7e82-e250-44d1-a6a1-c4d4d85ab201-1606580233335@3c-app-mailcom-bs12> (raw)
In-Reply-To: <83r1odmpet.fsf@gnu.org>
Yes, just about the html code when one is using a browser. In info it is easy
to do the search. I informed the Gavin and Patrice, to see what can be done on
how texinfo processes the menu for html.
---------------------
Christopher Dimech
General 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, November 28, 2020 at 5:12 PM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Emacs Lisp Reference Manual
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: help-gnu-emacs@gnu.org
> > Date: Sat, 28 Nov 2020 12:14:28 +0100
> >
> > If one is using a Web Browser, it is much quicker to find if
> > you say "See 10.4 Backquote". You just scroll to 10, then to
> > four, rather than by a Brain Regexp.
>
> So this is only relevant to the HTML output? Because in Info you just
> use the 'g' command, which prompts for the name of the node to go to.
>
>
next prev parent reply other threads:[~2020-11-28 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 20:42 Emacs Lisp Reference Manual Christopher Dimech
2020-11-27 20:55 ` Eli Zaretskii
2020-11-27 21:18 ` Christopher Dimech
2020-11-28 7:28 ` Eli Zaretskii
2020-11-28 11:14 ` Christopher Dimech
2020-11-28 16:12 ` Eli Zaretskii
2020-11-28 16:17 ` Christopher Dimech [this message]
2020-11-27 21:06 ` Michael Heerdegen
2020-11-27 21:26 ` tomas
2020-11-28 1:37 ` Drew Adams
2020-11-28 1:56 ` Christopher Dimech
2020-11-28 8:02 ` Eli Zaretskii
2020-11-28 12:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-10ac7e82-e250-44d1-a6a1-c4d4d85ab201-1606580233335@3c-app-mailcom-bs12 \
--to=dimech@gmx.com \
--cc=eliz@gnu.org \
--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.
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.