From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Kan-Ru Chen <kanru@kanru.info>
Cc: ding@gnus.org
Subject: Re: [PATCH] ecomplete.el: Use a local keymap to handle bindings
Date: Mon, 26 Sep 2011 23:00:26 +0200 [thread overview]
Message-ID: <m362kfqas5.fsf@stories.gnus.org> (raw)
In-Reply-To: <m3wrcvxh1j.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 26 Sep 2011 21:03:20 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Kan-Ru Chen <kanru@kanru.info> writes:
>
>> + * ecomplete.el (ecomplete-display-matches): Use a local keymap to
>> + handle bindings.
>
> Thanks; applied.
Unfortunately, it didn't work under XEmacs, so I reverted it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-09-26 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 13:37 Kan-Ru Chen
2011-09-26 15:14 ` Julien Danjou
2011-09-26 17:59 ` Kan-Ru Chen
2011-09-26 19:03 ` Lars Magne Ingebrigtsen
2011-09-26 21:00 ` Lars Magne Ingebrigtsen [this message]
2011-09-27 5:08 ` Kan-Ru Chen
2011-09-27 5:09 ` [PATCHv3] " Kan-Ru Chen
2011-10-06 21:33 ` [PATCH] " Lars Magne Ingebrigtsen
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=m362kfqas5.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=kanru@kanru.info \
/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).