* (interactive "...") : What goes in, what does not ?
@ 2008-03-15 18:50 paul r
2008-03-18 9:04 ` paul r
0 siblings, 1 reply; 3+ messages in thread
From: paul r @ 2008-03-15 18:50 UTC (permalink / raw)
To: emacs- devel
Dear list,
I was wondering recently why (interactive) does not provide a code
letter for "yes-or-no-p".
That lead me to this question : Is there a reason why some input
reading methods have a code letter for interactive and some not ?
By "input reading methods", I mean most of functions begining with
read- , plus yes-or-no-p, plus any I could miss here, provided they
could fit in this role.
Regards
Paul
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: (interactive "...") : What goes in, what does not ?
2008-03-15 18:50 (interactive "...") : What goes in, what does not ? paul r
@ 2008-03-18 9:04 ` paul r
2008-03-18 17:14 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: paul r @ 2008-03-18 9:04 UTC (permalink / raw)
To: emacs- devel
> Is there a reason why some input
> reading methods have a code letter for interactive and some not ?
Sorry to bump this question, but I'm still wondering. In case there is
no clear policy about it, how would you like a patch to provide code
letter for commonly used prompt that does not have their own code
letter yet, please ?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: (interactive "...") : What goes in, what does not ?
2008-03-18 9:04 ` paul r
@ 2008-03-18 17:14 ` Stefan Monnier
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Monnier @ 2008-03-18 17:14 UTC (permalink / raw)
To: paul r; +Cc: emacs- devel
>> Is there a reason why some input
>> reading methods have a code letter for interactive and some not ?
> Sorry to bump this question, but I'm still wondering. In case there is
> no clear policy about it, how would you like a patch to provide code
> letter for commonly used prompt that does not have their own code
> letter yet, please ?
Code letters were important when built-in functions couldn't use Elisp
forms as interactive specs. Now that they can use Elisp code as well,
it is less important.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-03-18 17:14 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-15 18:50 (interactive "...") : What goes in, what does not ? paul r
2008-03-18 9:04 ` paul r
2008-03-18 17:14 ` Stefan Monnier
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).