unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Weiner <rsw@gnu.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Emacs 25.0.04: Feature Request: Make called-interactively-p's argument optional
Date: Mon, 27 Jun 2016 16:35:18 -0400	[thread overview]
Message-ID: <CA+OMD9iQ_x71J5zcjO8gOJK57yC20itvw05o9W30RZ5RqSiK9g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 633 bytes --]

I have some older code with a lot of calls to (interactive-p) for which
I am having to substitute (called-interactively-p 'interactive) to get the
same behavior with a non-obsoleted call.  Visually, this does not read well
to me and I imagine others.  What do people think of making the argument
optional and defaulting it to the behavior of (interactive-p) which I
believe equates to the 'interactive argument value?

Then we would have: if (called-interactively-p) ...) in a lot of places and
that would look much better and be much easier to call properly.

When more complex behavior is needed, the argument could be given.

Bob

[-- Attachment #2: Type: text/html, Size: 1331 bytes --]

             reply	other threads:[~2016-06-27 20:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 20:35 Robert Weiner [this message]
2016-06-28 19:09 ` Emacs 25.0.04: Feature Request: Make called-interactively-p's argument optional John Wiegley
2016-06-28 20:28   ` Robert Weiner
2016-06-30 16:54   ` Andreas Röhler
2016-06-28 20:29 ` Glenn Morris
2016-06-28 20:46   ` Robert Weiner
2016-06-28 20:51     ` Robert Weiner
2016-06-29 20:02     ` Richard Stallman
2016-06-29 20:54       ` Robert Weiner
2016-06-29 21:19         ` Drew Adams
2016-06-29 21:39           ` Robert Weiner
2016-06-29 21:48             ` Robert Weiner
2016-06-30 23:18               ` Richard Stallman
2016-06-29 21:21         ` Clément Pit--Claudel
2016-06-29 21:52           ` Dmitry Gutov
2016-06-29 22:00             ` Robert Weiner
2016-06-30  2:51         ` raman
2016-06-30 14:25           ` Robert Weiner
2016-06-30 15:30             ` Eli Zaretskii
2016-07-03 18:36               ` Andreas Röhler
2016-07-03 18:56                 ` Alan Mackenzie
2016-07-03 19:57                   ` Andreas Röhler
2016-07-03 19:31                 ` Eli Zaretskii
2016-06-30 15:34             ` raman
2016-07-03  0:10         ` Richard Stallman
2016-07-06  0:09   ` John Wiegley
2016-07-06  0:21     ` Dmitry Gutov
2016-07-06  0:31       ` John Wiegley
2016-07-06  1:46         ` raman
2016-07-06  2:05           ` Dmitry Gutov
2016-07-06 14:49           ` Eli Zaretskii
2016-07-06 15:14             ` raman
2016-07-06 14:48         ` Eli Zaretskii
2016-07-06 15:20           ` Robert Weiner
2016-07-06  0:24     ` Noam Postavsky
2016-07-06  5:03       ` Robert Weiner
2016-07-06  6:45         ` Andreas Röhler

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=CA+OMD9iQ_x71J5zcjO8gOJK57yC20itvw05o9W30RZ5RqSiK9g@mail.gmail.com \
    --to=rsw@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rswgnu@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 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).