From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <embe8573@student.uu.se>, help-gnu-emacs@gnu.org
Subject: RE: require basic stuff from specific packages
Date: Wed, 13 Jul 2016 09:25:16 -0700 (PDT) [thread overview]
Message-ID: <e7e8232b-fcc3-4602-98d7-8016b9784141@default> (raw)
In-Reply-To: <86mvllh68i.fsf@student.uu.se>
> > If you are in the manual, then `i x RET'.
>
> OK, so there is no hit for "trim" in the index.
If you think there should be one: `M-x report-emacs-bug'.
> > If `x' is not in the index then you will need
> > to search for it: `C-s x C-s C-s...' or
> > likewise, with `C-M-s', if `x' is a regexp.
>
> The normal search? Cool, only in what
> buffer, then?
Buffer `*info*', in some manual. Doesn't matter what node:
you can repeat it to search across nodes, throughout the book,
including with wraparound.
This is the way to find things that are not indexed,
including particular strings of text that would never
be indexed. And don't forget regexp search: `C-M-s'.
This has been in Emacs since the beginning, except that
in the old days it was not incremental search across nodes.
You had to type `s', then a regexp and then `RET'. Then
you repeated the search by just `s RET'. Incremental
search is much better, of course.
But the main takeaway should be that `i' is your friend.
Use search only when `i' doesn't help, or within a node.
One reason for this is that a (smart and knowledgeable)
human being has specified the occurrences of something
that _should_ be indexed. That's quite different from
just searching and thus hitting _each_ occurrence.
next prev parent reply other threads:[~2016-07-13 16:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 23:13 require basic stuff from specific packages Emanuel Berg
2016-07-04 8:10 ` Stefan Monnier
2016-07-04 8:31 ` Lars Magne Ingebrigtsen
2016-07-05 0:44 ` Emanuel Berg
2016-07-13 1:26 ` Howard Melman
2016-07-13 1:58 ` Drew Adams
[not found] ` <mailman.1251.1468375187.26859.help-gnu-emacs@gnu.org>
2016-07-13 2:11 ` Emanuel Berg
[not found] ` <mailman.1248.1468373420.26859.help-gnu-emacs@gnu.org>
2016-07-13 2:06 ` Emanuel Berg
2016-07-13 13:31 ` Howard Melman
2016-07-13 14:10 ` Drew Adams
[not found] ` <mailman.1273.1468416740.26859.help-gnu-emacs@gnu.org>
2016-07-13 13:40 ` Emanuel Berg
2016-07-13 15:13 ` Drew Adams
[not found] ` <mailman.1301.1468422827.26859.help-gnu-emacs@gnu.org>
2016-07-13 16:07 ` Emanuel Berg
2016-07-13 16:16 ` Kaushal Modi
2016-07-13 16:19 ` Kaushal Modi
2016-07-13 16:41 ` Drew Adams
2016-07-13 16:25 ` Drew Adams [this message]
[not found] ` <mailman.1322.1468427133.26859.help-gnu-emacs@gnu.org>
2016-07-13 19:24 ` Emanuel Berg
2016-07-14 3:12 ` Howard Melman
[not found] ` <mailman.1377.1468465957.26859.help-gnu-emacs@gnu.org>
2016-07-15 1:49 ` Emanuel Berg
2016-07-16 7:07 ` Emanuel Berg
2016-07-19 20:43 ` EB double-grep function for bash Tomas Nordin
2016-07-14 1:35 ` require basic stuff from specific packages Emanuel Berg
2016-08-09 14:16 ` Udyant Wig
2016-08-10 15:39 ` Emanuel Berg
2016-08-10 15:51 ` Drew Adams
2016-08-10 17:54 ` Udyant Wig
2016-08-10 19:43 ` Emanuel Berg
2016-08-11 5:38 ` Udyant Wig
2016-08-11 14:49 ` Eli Zaretskii
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=e7e8232b-fcc3-4602-98d7-8016b9784141@default \
--to=drew.adams@oracle.com \
--cc=embe8573@student.uu.se \
--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).