unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: cyd@stupidchicken.com, rms@gnu.org, drew.adams@oracle.com,
	emacs-devel@gnu.org
Subject: Re: interactive-p and called-interactively-p
Date: Thu, 03 Sep 2009 17:17:20 -0400	[thread overview]
Message-ID: <jwveiqnd95p.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87iqg0ktic.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Thu, 03 Sep 2009 23:11:39 +0900")

>> If you don't mind the size of the transient caused by the change, I think
>> the mandatory argument is the best design.
> I don't know how many of my colleagues at XEmacs and SXEmacs will
> agree, but I'd like to see that change.

That's actually very good to hear.
So, I'd suggest the following:

- mark interactive-p as obsolete.
- add a mandatory argument to called-interactively-p.

The next best solution is:

- mark interactive-p and called-interactively-p as obsolete.
- create a new function `invoked-interactively-p' with a mandatory argument.

I prefer the first because I think called-interactively-p is the
better name.  But only the second preserves 100% backward compatibility.
This said, AFAIK called-interactively-p is not used in any Elisp package
other the ones bundled with Emacs, so I'm not sure this backward
compatibility issue is significant (which is why I prefer the first
option).


        Stefan





  reply	other threads:[~2009-09-03 21:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 23:00 interactive-p and called-interactively-p Drew Adams
2009-08-16  5:16 ` Stefan Monnier
2009-08-16 13:29   ` Chong Yidong
2009-08-16 14:53     ` Stefan Monnier
2009-08-16 15:51     ` Drew Adams
2009-08-16 21:23   ` Richard Stallman
2009-08-16 22:40     ` Drew Adams
2009-08-17  5:38     ` Stephen J. Turnbull
2009-08-18  4:57       ` Richard Stallman
2009-08-18  7:08         ` Stephen J. Turnbull
2009-08-29 21:54     ` Stefan Monnier
2009-08-31 22:21       ` Richard Stallman
2009-08-31 23:56         ` Stefan Monnier
2009-09-01  1:58           ` Chong Yidong
2009-09-01  5:40             ` Stefan Monnier
2009-09-01 21:20               ` Richard Stallman
2009-09-01 23:30                 ` Stefan Monnier
2009-09-03 13:48                   ` Richard Stallman
2009-09-03 14:11                     ` Stephen J. Turnbull
2009-09-03 21:17                       ` Stefan Monnier [this message]
2009-09-04  1:21                         ` Stephen J. Turnbull
2009-09-04 13:11                           ` Stefan Monnier
2009-09-04  3:04                         ` Glenn Morris
2009-09-04  4:44                           ` Stephen J. Turnbull
  -- strict thread matches above, loose matches on Subject: below --
2009-09-03 16:27 MON KEY
2004-12-02  2:16 Luc Teirlinck
2004-12-03  3:41 ` Richard Stallman

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=jwveiqnd95p.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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 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).