From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Kan-Ru Chen <kanru@kanru.info>
Cc: ding@gnus.org
Subject: Re: [PATCH] ecomplete.el: Intercept key sequence from terminal as well.
Date: Wed, 21 Sep 2011 20:14:07 +0200 [thread overview]
Message-ID: <m3ty854vbk.fsf@stories.gnus.org> (raw)
In-Reply-To: <871uva2g4x.fsf@isil.kanru.info> (Kan-Ru Chen's message of "Wed, 21 Sep 2011 21:12:46 +0800")
Kan-Ru Chen <kanru@kanru.info> writes:
> D'oh! I got a buildbot compile failed report and realized
> `read-key-sequence-vector' does not exist in XEmacs and
> `read-key-sequence' is so different between the variants that origin
> code wouldn't work in XEmacs either.
I reverted the code for now, but if you could come up with a version
that would work on both Emacs versions, that would be nice.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2011-09-21 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 12:43 Kan-Ru Chen
2011-09-21 11:22 ` Kan-Ru Chen
2011-09-21 11:30 ` Julien Danjou
2011-09-21 13:12 ` Kan-Ru Chen
2011-09-21 18:14 ` Lars Magne Ingebrigtsen [this message]
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=m3ty854vbk.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).