Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Fancy completion
Date: Mon, 30 Aug 2010 18:43:21 +0200	[thread overview]
Message-ID: <m34oecrqza.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <sa3zkw4njqr.fsf@cigue.easter-eggs.fr>

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




  reply	other threads:[~2010-08-30 16:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  2:54 Lars Magne Ingebrigtsen
2010-08-30  3:07 ` Leo
2010-08-30  3:12   ` Lars Magne Ingebrigtsen
2010-08-30  3:18     ` Lars Magne Ingebrigtsen
2010-08-30  3:44     ` Leo
2010-08-30 16:25       ` Lars Magne Ingebrigtsen
2010-08-30  3:08 ` Leo
2010-08-30  8:01 ` Adam Sjøgren
2010-08-30 19:54   ` Andreas Schwab
2010-08-30 19:59     ` Adam Sjøgren
2010-08-30 20:45       ` Andreas Schwab
2010-08-31  2:07         ` Eric Abrahamsen
2010-08-31  6:13   ` Reiner Steib
2010-08-31 21:12     ` Adam Sjøgren
2010-08-31 23:19       ` Andreas Schwab
2010-08-31 23:29         ` Lars Magne Ingebrigtsen
2010-08-30 12:19 ` Julien Danjou
2010-08-30 16:26   ` Lars Magne Ingebrigtsen
2010-08-30 16:33     ` Julien Danjou
2010-08-30 16:43       ` Lars Magne Ingebrigtsen [this message]
2010-08-30 17:03         ` Leo
2010-08-30 17:16         ` Adam Sjøgren
2010-08-30 17:19           ` Lars Magne Ingebrigtsen
2010-08-30 17:21             ` Leo
2010-08-30 17:42               ` Adam Sjøgren
2010-08-30 17:38             ` Adam Sjøgren
2010-08-30 17:45               ` Leo
2010-08-30 17:53                 ` Lars Magne Ingebrigtsen
2010-08-30 18:22                 ` Adam Sjøgren

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=m34oecrqza.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@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 NNTP newsgroup(s).