From: "Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>
To: help-gnu-emacs@gnu.org
Subject: Re: How does M-x completion works
Date: Fri, 26 Feb 2010 12:58:14 +0100 [thread overview]
Message-ID: <op.u8qgvczfvwnd5a@garhos> (raw)
In-Reply-To: mailman.1758.1266983111.14305.help-gnu-emacs@gnu.org
Le Wed, 24 Feb 2010 04:44:54 +0100, Kevin Rodgers
<kevin.d.rodgers@gmail.com> a écrit:
> No. Compare the Completion node of the Emacs manual with the Tags node:
>
> | Some arguments allow "completion" to enter their value. This means
> | that after you type part of the argument, Emacs can fill in the rest,
> | or some of it, based on what you have typed so far.
> | ...
> | For example, `M-x' uses the minibuffer to read the name of a
> | command, so it provides a list of all Emacs command names for
> | completion candidates.
>
>
> | A "tags table" is a description of how a multi-file program is broken
> | up into files. It lists the names of the component files and the names
> | and positions of the functions (or other named subunits) in each file.
>
Thanks for the point Kevin. I was starting to feel lost and wondering if I
did really understand the manual. So you confirm these are really
different things. I feel better now.
--
No-no, this isn't an oops ...or I hope (TM) - Don't blame me... I'm just
not lucky
next prev parent reply other threads:[~2010-02-26 11:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 12:35 How does M-x completion works Hibou57 (Yannick Duchêne)
2010-02-22 16:34 ` Lennart Borgman
[not found] ` <4B82A7A4.6050005@easy-emacs.de>
[not found] ` <op.u8jfv6nuesn74s@garhos>
2010-02-22 17:42 ` Andreas Röhler
2010-02-22 22:06 ` Colin S. Miller
2010-02-23 7:06 ` Hibou57 (Yannick Duchêne)
2010-02-23 8:36 ` Barry Margolin
2010-02-23 9:25 ` Hibou57 (Yannick Duchêne)
2010-02-23 10:03 ` Andreas Röhler
[not found] ` <mailman.1694.1266919287.14305.help-gnu-emacs@gnu.org>
2010-02-23 13:47 ` Hibou57 (Yannick Duchêne)
2010-02-23 15:18 ` Andreas Röhler
2010-02-24 3:44 ` Kevin Rodgers
2010-02-26 13:12 ` Andreas Röhler
[not found] ` <mailman.1758.1266983111.14305.help-gnu-emacs@gnu.org>
2010-02-26 11:58 ` Hibou57 (Yannick Duchêne) [this message]
[not found] ` <mailman.1706.1266938167.14305.help-gnu-emacs@gnu.org>
2010-02-23 17:17 ` Hibou57 (Yannick Duchêne)
2010-02-23 19:32 ` Andreas Röhler
[not found] ` <mailman.1728.1266953431.14305.help-gnu-emacs@gnu.org>
2010-02-23 21:24 ` Tim X
2010-02-24 4:08 ` Kevin Rodgers
2010-02-24 20:10 ` Stefan Monnier
2010-02-24 4:10 ` Kevin Rodgers
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=op.u8qgvczfvwnd5a@garhos \
--to=yannick_duchene@yahoo.fr \
--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).