unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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 08:13:35 -0700 (PDT)	[thread overview]
Message-ID: <fdb1ac4c-22c2-4762-9ce9-d475fb170dd8@default> (raw)
In-Reply-To: <86vb09hd10.fsf@student.uu.se>

> > FWIW, I find the elisp manual to be pretty
> > good and it's index pretty complete and easy
> > to use via Emacs' info system (C-h i and then
> > i in a manual).
> 
> Alright, so what is the exact sequence of
> keystrokes and/or functions invoked to find `x'
> in the Elisp manual?

If you are in the manual, then `i x RET'.

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.

If `x' is indexed multiple times then you can continue to
visit indexed occurrences in the manual, by using `,' -
just as the message tells you.  E.g.:

 "Found `defun' in Index.  (11 total; use `,' for next)"

You can also use `I', which creates a virtual Info node
with the results of an index search.

If you don't know which manual to check, try `M-x info-apropos'.

All of this is well explained in the (small) Info manual,
in particular, (info) `Search Index'.

I suggest you start with the Info manual, before trying to use
any other manual.  Your time spent there will be rewarded.

There is a reason that the Info manual is presented first in
the list of manuals (by default).  Its description:

 "How to use the documentation browsing system."

It will answer that how-to question far better than answers
you'll get here, I'm guessing (including this answer).



  reply	other threads:[~2016-07-13 15:13 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 [this message]
     [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
     [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=fdb1ac4c-22c2-4762-9ce9-d475fb170dd8@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).