all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: michael_heerdegen@web.de, 62563@debbugs.gnu.org
Subject: bug#62563: [FR] Expose `interactive' arg handling as an Elisp function
Date: Tue, 19 Sep 2023 06:21:04 -0400	[thread overview]
Message-ID: <E1qiXqq-0004do-P5@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmkL9qfViz6RaJEk+oHfXeS7vB3_TkL1kwpca5vusuyGCA@mail.gmail.com> (message from Stefan Kangas on Sun, 17 Sep 2023 04:31:57 -0700)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

In general, each interactive spec can be programmed with Lisp code
inside `interactive'.  But maybe there are some exceptions, Which ones
are exceptions?  If we post the list of those, maybe we can provide a
simple specific solutions for them.

Also, maybe people will point out existing ways to handle some of the
codes that were first thought to be "missing".


-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







      parent reply	other threads:[~2023-09-19 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  7:27 bug#62563: [FR] Expose `interactive' arg handling as an Elisp function Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-31  7:38 ` Eli Zaretskii
2023-09-11 23:54   ` Stefan Kangas
2023-09-17  0:50     ` Michael Heerdegen
2023-09-17 11:31       ` Stefan Kangas
2023-09-18  4:28         ` Michael Heerdegen
2023-09-19 10:21         ` Richard Stallman [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=E1qiXqq-0004do-P5@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=62563@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=stefankangas@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.