From: Hadron <hadronquark@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: TAGS documentation
Date: Sun, 29 Jul 2007 14:17:29 +0200 [thread overview]
Message-ID: <6kzm1f1k12.fsf@googlemail.com> (raw)
In-Reply-To: mailman.4102.1185705618.32220.help-gnu-emacs@gnu.org
AN0 <an00na@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Hadron <hadronquark@googlemail.com>
>>> Date: Sat, 28 Jul 2007 20:07:26 +0200
>>>
>>> > C-h i d m emacs RET g Tags RET
>>> >
>>> > spits out some error message instead of getting you to the description
>>> > of tags tables and associated commands and features? If so, you need
>>> > to fix your installation of the Emacs manual, because what you want is
>>> > an integral part of it.
>>>
>>> Thank you Eli - that command sequence found tags!
>>>
>>> What Search command should find it from the top index level?
>>
>> In Info manuals, never use search commands -- they are for sissies. ;-)
>> Instead, use the index search feature of Info. Any well-written Info
>> manual should have an index which will get you to the description of
>> every important concept quickly and efficiently. In this case, the
>> command "i tags RET" inside the Emacs manual will land you on the
>> above spot (this is how I found the node when answering your question,
>> btw).
>>
>> The `i' command is the way to use an Info manual as a reference (as
>> opposed to just reading through it, which is typical of the first time
>> you learn to use a program).
>
> But when I used the `i' command in the Info directory (where the `d' led me
> to), I got following message:
> The Info directory node has no index; use m to select a manual
>
> so it seems an `m' command is inevitable.
Exactly. So is there are way to search all manuals without doing an "m" first?
next prev parent reply other threads:[~2007-07-29 12:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 12:33 TAGS documentation Hadron
2007-07-28 14:49 ` Eli Zaretskii
2007-07-28 17:32 ` Frank Murray
[not found] ` <mailman.4080.1185634171.32220.help-gnu-emacs@gnu.org>
2007-07-28 15:29 ` Hadron
2007-07-28 16:35 ` Eli Zaretskii
[not found] ` <mailman.4082.1185640558.32220.help-gnu-emacs@gnu.org>
2007-07-28 18:07 ` Hadron
2007-07-28 19:37 ` Eli Zaretskii
2007-07-29 5:12 ` AN0
[not found] ` <mailman.4102.1185705618.32220.help-gnu-emacs@gnu.org>
2007-07-29 12:17 ` Hadron [this message]
2007-07-29 20:10 ` Eli Zaretskii
[not found] ` <mailman.4085.1185651464.32220.help-gnu-emacs@gnu.org>
2007-07-29 2:51 ` Hadron
2007-07-29 20:13 ` Eli Zaretskii
[not found] ` <mailman.4110.1185740045.32220.help-gnu-emacs@gnu.org>
2007-07-29 21:36 ` Hadron
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=6kzm1f1k12.fsf@googlemail.com \
--to=hadronquark@googlemail.com \
--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).