Gnus development mailing list
 help / color / mirror / Atom feed
From: Lawrence Mitchell <wence@gmx.li>
To: ding@gnus.org
Subject: Re: gnus-completing-read vs XEmacs 21.4
Date: Mon, 04 Oct 2010 17:35:41 +0100	[thread overview]
Message-ID: <pvhppqvp3ogy.fsf@gmx.li> (raw)
In-Reply-To: <84d3rply1n.fsf@davestoy.home>

Dave Goldberg wrote:
>> This is almost certainly because old (for some value of old)
>> versions of Emacs
                    ^,

There was a comma missing here, the old qualifier only applies to
Emacs, all XEmacs versions expect this.

>> and XEmacs expect the second value of try-completion to be an
>> alist and the car of each element is checked for matching.

> [...]

> I'm running 21.4 (patch 22) "Instant Classic" XEmacs Lucid
> which I understand is current stable.  The doc string for
> try-completion says

[...]

> If COLLECTION is an alist, the cars of the elements of the alist
> (which must be strings) form the set of possible completions.

Yep, this is the cause of the problem you're seeing.

Lawrence
-- 
Lawrence Mitchell <wence@gmx.li>




  reply	other threads:[~2010-10-04 16:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 14:20 Dave Goldberg
2010-10-04 14:32 ` Julien Danjou
2010-10-04 15:20   ` Dave Goldberg
2010-10-04 15:29     ` Julien Danjou
2010-10-04 15:38       ` Dave Goldberg
2010-10-04 16:04         ` Dave Goldberg
2010-10-04 16:08           ` Julien Danjou
2010-10-04 16:25           ` Lawrence Mitchell
2010-10-04 16:31             ` Dave Goldberg
2010-10-04 16:35               ` Lawrence Mitchell [this message]
2010-10-04 16:37             ` Julien Danjou
2010-10-04 16:54               ` Lawrence Mitchell
2010-10-04 17:47                 ` Julien Danjou
2010-10-04 18:28                   ` Dave Goldberg
2010-10-04 20:18                     ` Julien Danjou
2010-10-04 21:55                       ` Dave Goldberg
2010-10-08 12:14                   ` Andrew Cohen
2010-10-08 14:35                     ` Julien Danjou

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=pvhppqvp3ogy.fsf@gmx.li \
    --to=wence@gmx.li \
    --cc=ding@gnus.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).