From: Thien-Thi Nguyen <ttn@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: How to test whether any code runs after same command invocation?
Date: Sat, 15 Feb 2014 13:25:27 +0100 [thread overview]
Message-ID: <87bny88sw8.fsf@zigzag.favinet> (raw)
In-Reply-To: <878utcd5n0.fsf@web.de> (Michael Heerdegen's message of "Sat, 15 Feb 2014 11:36:35 +0100")
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
() Michael Heerdegen <michael_heerdegen@web.de>
() Sat, 15 Feb 2014 11:36:35 +0100
> Another way to be lazy is to do nothing if there is pending input.
Yes, but that approach doesn't help in my case.
Oops, sorry for the noise.
> BTW, this should probably be on help-gnu-emacs.
Thanks, I wasn't sure about that. I thought questions about
developing Emacs addons fit here, but emacs-dev is only about
developing vanilla Emacs itself, right? Sorry, then.
No worries. In this case i suppose the issue pertains to both just
fine. IMHO, it's nicer to see a solution using existing facilities on
help-, and one using new facilities (or conventions) on -devel, but if
in the end everyone who reads one reads the other, there is distinction
not in substance, only in style.
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-02-15 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 11:09 How to test whether any code runs after same command invocation? Michael Heerdegen
2014-02-14 14:27 ` Stefan Monnier
2014-02-14 15:08 ` Michael Heerdegen
2014-02-14 17:15 ` Stefan Monnier
2014-02-14 17:42 ` Michael Heerdegen
2014-02-14 20:55 ` Stefan Monnier
2014-02-15 10:46 ` Michael Heerdegen
2014-02-14 18:41 ` Thien-Thi Nguyen
2014-02-15 10:36 ` Michael Heerdegen
2014-02-15 12:25 ` Thien-Thi Nguyen [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bny88sw8.fsf@zigzag.favinet \
--to=ttn@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).