* Re: Fancy completion
[not found] ` <sa3zkw4njqr.fsf@cigue.easter-eggs.fr>
@ 2010-08-30 16:43 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; only message in thread
From: Lars Magne Ingebrigtsen @ 2010-08-30 16:43 UTC (permalink / raw)
To: ding; +Cc: emacs-devel
Julien Danjou <julien@danjou.info> writes:
> Using `ido-completing-read' instead of `completing-read' if a user set
> gnus-use-ido' to t would be a good solution.
Hm... I just tried replacing completing-read with the ido method, and
I got a backtrace. So it wants a list instead of an obarray, but that's
easily enough fixed:
Debugger entered--Lisp error: (wrong-type-argument listp [nntp+news\.gmane\.org:gmane\.comp\...
reverse([nntp+news\.gmane\.org:gmane\.comp\.ide\.anjuta\.us/...
ido-set-matches()
ido-read-internal(list "Group: " gnus-group-history nil nil nil)
ido-completing-read("Group: " [nnt...
> It seems org-mode is doing this that way.
But I wonder if that's the wrong way to do it. Wouldn't it make more
sense for the user to say
(ido-mode '(buffer file gnus org))
and then for Gnus to look at the ido-mode variable? This requires a
change in ido-mode, of course, but doesn't it seem like a more clean way
for all the various packages to integrate with ido?
I've crossposted this to the Emacs list for feedback.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-08-30 16:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <m3mxs4x11r.fsf@quimbies.gnus.org>
[not found] ` <sa3aao4uwbs.fsf@cigue.easter-eggs.fr>
[not found] ` <m3occkrrr8.fsf@quimbies.gnus.org>
[not found] ` <sa3zkw4njqr.fsf@cigue.easter-eggs.fr>
2010-08-30 16:43 ` Fancy completion Lars Magne Ingebrigtsen
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).