From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: debug-on-entry question
Date: Mon, 20 Jun 2005 07:59:32 +0300 [thread overview]
Message-ID: <87aclllkx9.fsf@jurta.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICEEHGCJAA.drew.adams@oracle.com> (Drew Adams's message of "Sun, 19 Jun 2005 10:24:59 -0700")
> However, that would only help with uses of `call-interactively', not
> uses of `interactive' itself.
I don't understand what you mean. `interactive' is just a specification.
`call-interactively' interprets it.
> It's probably not feasible (and I foresee immediate dismissal of the idea,
> regardless of feasibility), but what about also having a mechanism to let
> users extend (redefine) the predefined `interactive' code letters?
>
> For example, a user could define his own version of `b' in `(interactive
> "b...")'. Instead of having to find all occurrences of `(interactive
> "b...")' and replacing each of them with his own `(interactive (list
> (my-read-buffer...)...)...)', he could just redefine what `(interactive
> "b...")' means, in a single place. IOW, why not make the "bindings" between
> the `interactive' code letters (e.g. `b') and their input-reading functions
> available to users?
Rewriting it in Lisp implies that you will be able to redefine default
code letters easily if you want.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-06-20 4:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-18 10:03 debug-on-entry question Yoni Rabkin Katzenell
2005-06-18 11:23 ` David Kastrup
2005-06-18 11:47 ` Yoni Rabkin Katzenell
2005-06-19 14:03 ` Juri Linkov
2005-06-19 17:24 ` Drew Adams
2005-06-19 17:48 ` David Kastrup
2005-06-19 18:07 ` Drew Adams
2005-06-20 4:59 ` Juri Linkov [this message]
2005-06-20 15:42 ` Drew Adams
2005-06-21 2:00 ` Richard Stallman
2005-06-20 3:50 ` Richard Stallman
2005-06-20 17:41 ` Lute Kamstra
2005-06-21 16:32 ` Juri Linkov
2005-06-22 3:40 ` Richard M. Stallman
2005-06-22 8:32 ` Lute Kamstra
2005-06-23 0:54 ` Richard M. Stallman
2005-06-22 13:12 ` Juri Linkov
2005-06-23 14:38 ` Drew Adams
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=87aclllkx9.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.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.
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.