Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: gnus-completing-read vs XEmacs 21.4
Date: Mon, 04 Oct 2010 10:20:35 -0400	[thread overview]
Message-ID: <84bp7aujik.fsf@davestoy.home> (raw)

After a git pull this morning (commit
896480a177c32f9c4449b796e3173fddba51c373 at the top of git log) I can
no longer complete most things.  This appears to be the addition of
gnus-completing-read.  The error appears to be that the objects
containing the lists of possible completions are not structured the
way gnus-completing-read wants.  I may be able to fix this with my
smime-keys by adding another set of parens around it, but I don't get
that option with dynamically created lists such as the list of groups
for doing things like moving/copying articles and jumping to groups,
and mime types for things like K t.  Not having seen any other
complaints here, I have to assume it's a compatibility issue with
XEmacs 21.4.

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net



             reply	other threads:[~2010-10-04 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 14:20 Dave Goldberg [this message]
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
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=84bp7aujik.fsf@davestoy.home \
    --to=david.goldberg6@verizon.net \
    --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).