From: Mark Plaksin <happy@usg.edu>
Subject: Re: Use ido for *all* completion?
Date: Thu, 10 Mar 2005 12:24:18 -0500 [thread overview]
Message-ID: <m3d5u74dod.fsf@water.tss.usg.edu> (raw)
In-Reply-To: u7jkfxwlw.fsf@gmail.com
Peter Lee <pete.a.lee@gmail.com> writes:
>>>>> Mark Plaksin writes:
>
> > I have looked at icomplete, partial-completion-mode, and ido. Of the
> > three, ido is the best for me.
>
> There is also mcomplete. Not sure of the differences between
> mcomplete and those other modes you listed, but it does prefix and
> substring completion.
mcomplete.el (http://homepage1.nifty.com/bmonkey/emacs/elisp/mcomplete.el)
has a nice ASCII drawing of how it integrates with the minibuffer. Maybe
we can use this same method with ido. I'll take a look at this one day
soon. Here's the drawing;
;;; How this package works:
;; On loading this package,
;; `mcomplete-minibuffer-setup' is registered in `minibuffer-setup-hook'.
;;
;;
;; Some command tries to begin a minibuffer session
;; |
;; v
;; (run-hooks 'minibuffer-setup-hook) -+
;; | |
;; | v
;; | `mcomplete-minibuffer-setup'
;; | (when (mcomplete-p)
;; | (run-hooks 'mcomplete-minibuffer-setup-hook))
;; | |
;; | v
;; | `mcomplete-setup-command-hooks'
;; | * registers `mcomplete-pre-command-hook' in
;; | the buffer local `pre-command-hook'.
;; | * registers `mcomplete-post-command-hook' in
;; | the buffer local `post-command-hook'.
;; v
;; The minibuffer session begins
;; |
;; v
;; Some key is pressed in the minibuffer
;; |
;; v
;; (run-hooks 'pre-command-hook) -+
;; | |
;; | v
;; | (run-hooks 'mcomplete-pre-command-hook)
;; | |
;; | v
;; | `mcomplete-pre-command-tidy'
;; | * clears information display in the minibuffer.
;; v
;; The command for the key is executed
;; |
;; v
;; (run-hooks 'post-command-hook) -+
;; |
;; v
;; (run-hooks 'mcomplete-post-command-hook)
;; |
;; v
;; `mcomplete-post-command-exhibit'
;; * displays information in the minibuffer.
next prev parent reply other threads:[~2005-03-10 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3075.1110334732.32256.help-gnu-emacs@gnu.org>
2005-03-09 10:19 ` Use ido for *all* completion? Oliver Scholz
2005-03-09 17:44 ` Drew Adams
2005-03-09 17:53 ` Romain Francoise
2005-03-09 21:45 ` Oliver Scholz
2005-03-10 7:43 ` Romain Francoise
2005-03-10 12:22 ` Oliver Scholz
2005-03-10 13:27 ` Mark Plaksin
[not found] ` <mailman.3281.1110462563.32256.help-gnu-emacs@gnu.org>
2005-03-10 17:02 ` Peter Lee
2005-03-10 17:24 ` Mark Plaksin [this message]
[not found] <mailman.3043.1110317172.32256.help-gnu-emacs@gnu.org>
2005-03-09 0:58 ` Oliver Scholz
2005-03-09 1:43 ` Drew Adams
2005-03-09 14:13 ` Stefan Monnier
2005-03-09 17:43 ` Mark Plaksin
[not found] ` <mailman.3152.1110391613.32256.help-gnu-emacs@gnu.org>
2005-03-10 4:19 ` Stefan Monnier
2005-03-14 0:25 ` Mark Plaksin
2005-03-08 18:14 Mark Plaksin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d5u74dod.fsf@water.tss.usg.edu \
--to=happy@usg.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.