From: Le Wang <l26wang@gmail.com>
To: Minejima Yuji <yuji.minejima@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is mcomplete.el still relevant?
Date: Thu, 26 Jul 2012 08:25:47 +0800 [thread overview]
Message-ID: <CAM=K+ioHcfk5-87MZxCLPXk2wQTZ1VoDHiPTe7wexmKgYKrsLQ@mail.gmail.com> (raw)
In-Reply-To: <4abbdab5-239d-456d-8272-d453b2fb45a1@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
Hi Minejima,
On Thu, Jul 26, 2012 at 3:18 AM, Minejima Yuji <yuji.minejima@gmail.com>wrote:
> Hi, there.
> I'm the author of mcomplete.el package which does minibuffer completion
> with prefix and substring matching.
> http://homepage1.nifty.com/bmonkey/emacs/elisp/mcomplete.el
>
> I've been away from Emacs and Elisp for several years now. But I decided to
> come back. Back then, some people toled me that they loved mcomplete.el.
>
I have very fond memories of using mcomplete. And I still carry it around,
although it hasn't been loaded as part of my Emacs init for some time.
Thank you for contributing your time to improve my Emacs experience!
> But time flies like an arrow, I'm not sure if it's still relevant to the
> current
> Emacs environment.
>
> Does some other package overtake its functionality? Or does Emacs no
> longer need it because it already does the same thing on its own?
>
I believe ido, which is a part of Emacs 24 has very similar functionality.
Although helm is the completion package I've settled on.
https://github.com/emacs-helm/helm
--
Le
[-- Attachment #2: Type: text/html, Size: 1722 bytes --]
next prev parent reply other threads:[~2012-07-26 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 19:18 Is mcomplete.el still relevant? Minejima Yuji
2012-07-25 21:41 ` Jambunathan K
2012-07-26 0:25 ` Le Wang [this message]
2012-07-26 1:32 ` Sohail Somani
2012-07-26 9:56 ` Le Wang
2012-07-26 10:56 ` Eric Abrahamsen
2012-07-26 12:16 ` Sohail Somani
2012-07-26 13:35 ` Tassilo Horn
2012-07-26 14:58 ` Sohail Somani
2012-07-26 0:31 ` Christopher Schmidt
2012-07-26 0:32 ` Christopher Schmidt
2012-07-26 8:50 ` Minejima Yuji
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='CAM=K+ioHcfk5-87MZxCLPXk2wQTZ1VoDHiPTe7wexmKgYKrsLQ@mail.gmail.com' \
--to=l26wang@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yuji.minejima@gmail.com \
/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).