From: Jason Rumney <jasonr@gnu.org>
To: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, Leo <sdl.web@gmail.com>,
emacs-devel@gnu.org
Subject: Re: dabbrev-expand for the minibuffer
Date: Thu, 28 Feb 2008 00:08:08 +0000 [thread overview]
Message-ID: <47C5FB68.7000709@gnu.org> (raw)
In-Reply-To: <871w6yez0c.fsf@catnip.gol.com>
Miles Bader wrote:
> Juri Linkov <juri@jurta.org> writes:
>
>> It would be easier to implement this in hippie-expand because it has all
>> necessary infrastructure.
>>
>
> What exactly is the relationship between dabbrev and hippie-expand?
>
> They seem like two implementations of the same thing; is there a reason
> to have both?
>
They are quite different. dabbrev completes based on existing text in
the buffer (or multiple buffers with a prefix arg). hippie-expand
completes using multiple methods, which may or may not include dabbrev.
next prev parent reply other threads:[~2008-02-28 0:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 22:59 dabbrev-expand for the minibuffer Dan Nicolaescu
2008-02-24 9:26 ` Leo
2008-02-27 22:49 ` Juri Linkov
2008-02-27 23:22 ` Leo
2008-02-27 23:54 ` Miles Bader
2008-02-28 0:08 ` Jason Rumney [this message]
2008-02-28 0:35 ` Miles Bader
2008-02-28 8:21 ` Jason Rumney
2008-02-28 8:29 ` Leo
2008-02-28 16:41 ` Richard Stallman
2008-02-28 21:14 ` Leo
2008-02-29 19:54 ` Richard Stallman
2008-02-24 17:35 ` Juri Linkov
2008-02-25 8:13 ` Bastien
2008-02-27 0:18 ` Johan Bockgård
2008-02-27 1:06 ` Dan Nicolaescu
2008-02-27 11:28 ` Johan Bockgård
2008-02-27 14:38 ` Dan Nicolaescu
2008-02-27 15:04 ` Johan Bockgård
2008-02-27 15:30 ` Dan Nicolaescu
-- strict thread matches above, loose matches on Subject: below --
2008-03-01 13:31 Richard Stallman
2008-07-21 15:55 ` Drew Adams
2008-07-21 16:47 ` Lennart Borgman (gmail)
2008-07-21 16:48 ` Lennart Borgman (gmail)
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=47C5FB68.7000709@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=miles@gnu.org \
--cc=sdl.web@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).