unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Tomas Hlavaty <tom@logand.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: finding stuff
Date: Sun, 28 Feb 2021 06:20:53 +0000	[thread overview]
Message-ID: <87ft1gu30a.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <87a6szjc81.fsf@logand.com> (message from Tomas Hlavaty on Sun, 24 Jan 2021 03:33:02 +0100)

Tomas Hlavaty <tom@logand.com> writes:

> Hi,
>
> is there a way to search "everything" which comes with Emacs?
>
> Example: I do not remember Local Variables section syntax and have to
> look it up.  I try various things, fail and end up using web browser.
> That is far from ideal.
>
> Today I invested a bit more time and found C-h d command so C-h d "local
> variables" and then C-s "local variables:" finds something: one hit
> only.  Now I discovered add-file-local-variable function.  But still not
> the syntax of the Local Variables section.
>
> Searching info is still a mystery to me.  Is there a way to search
> across all info files?
>
> Is there a way to search everything which comes with emacs,
> e.g. function names, docstrings, info, NEWS etc?

I think a way of searching all those things would be useful.  As others
have mentioned there are separate ways of searching most of them.  I
think "info-apropos" is the most useful for your wishes.

Another possibility that people haven't mentioned is to build Emacs from
source then to load the tags-table and search that.

However, I still think that info-apropos is best.  Things like grep or
the Emacs source can bring too many hits to be useful.

BR,
Robert Thorpe




  parent reply	other threads:[~2021-02-28  6:20 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-24  2:33 finding stuff Tomas Hlavaty
2021-01-24  5:33 ` Bob Newell
2021-01-24  7:22   ` Jean Louis
2021-01-24 11:09     ` Tomas Nordin
2021-01-24  7:13 ` Jean Louis
2021-01-24 16:26   ` John Yates
2021-01-25 16:31     ` [External] : " Drew Adams
2021-01-25 17:02       ` Eli Zaretskii
2021-01-25 17:37         ` Bob Newell
2021-01-25 19:39           ` John Yates
2021-01-25 20:59           ` Stefan Monnier
2021-01-26 10:33             ` Robert Pluim
2021-01-26 21:09               ` Drew Adams
2021-01-26  1:38           ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 21:06             ` Bob Newell
2021-01-26  5:21         ` Drew Adams
2021-01-26  5:45           ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 21:09             ` Drew Adams
2021-01-26 22:16               ` John Yates
2021-01-26 23:28                 ` Drew Adams
2021-01-27  6:29               ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26 15:02           ` Eli Zaretskii
2021-01-26 21:17             ` Drew Adams
2021-01-27  6:39               ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27  6:43                 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27 18:43                   ` Drew Adams
2021-01-27 18:59                     ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-27 18:24                 ` Drew Adams
2021-01-27 18:34                   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-26  1:58     ` Robert Thorpe
2021-01-26 14:49       ` John Yates
2021-01-27 11:33         ` doltes doltes
2021-01-24  9:18 ` Jude DaShiell
2021-01-24 10:58 ` Tomas Nordin
2021-02-27  1:10   ` Tomas Hlavaty
2021-02-27  2:57     ` Eduardo Ochs
2021-02-27  8:36       ` Tomas Hlavaty
2021-02-27 17:33         ` Eduardo Ochs
2021-02-27 23:25           ` Tomas Hlavaty
2021-02-27 23:28             ` Tomas Hlavaty
2021-02-28  6:20 ` Robert Thorpe [this message]
2021-02-28  7:39   ` Tomas Hlavaty
2021-02-28  7:55     ` Jean Louis

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=87ft1gu30a.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tom@logand.com \
    /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).