all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raman <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Suggest: dont declare interactive-p obsolete
Date: Thu, 19 Nov 2015 09:32:29 -0800	[thread overview]
Message-ID: <p91si41rj2q.fsf@google.com> (raw)
In-Reply-To: <m2r3jm6jnf.fsf@newartisans.com> (John Wiegley's message of "Thu,  19 Nov 2015 08:25:40 -0800")

Cleaning up those places would be a good first step.

Then we could nuke the definition in subr.el.   At that point, we should
still revisit what the right API to expose for this functionality is --
as  others have pointed out-- the present option

(called-interactively-p 'interactive )

is awkward and hard to discover as an elisp developer -- and even if you
discovered it -- you'd run screaming in fear.  

The  net/net of the documentation of called-interactively-p is that you
should essentially only use it as (called-interactively-p
'interactive) -- if that is our intent -- why not provide that as a
high-level call?

Let me make it clear -- I'm not asking for this because any o fmy own
code /libs depend on this -- they dont -- for the record,
called-interactively-p as implemented does not work in any form  for my
own use-cases:-)
-- 



  reply	other threads:[~2015-11-19 17:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  1:57 Suggest: dont declare interactive-p obsolete raman
2015-11-19  4:16 ` John Wiegley
2015-11-19  8:39   ` Artur Malabarba
2015-11-19 13:06     ` Andreas Röhler
2015-11-19 13:46       ` Dmitry Gutov
2015-11-20  7:29         ` Andreas Röhler
2015-11-19 13:44     ` Dmitry Gutov
2015-11-19 15:29   ` Eli Zaretskii
2015-11-19 16:25     ` John Wiegley
2015-11-19 17:32       ` raman [this message]
2015-11-19 17:47         ` Eli Zaretskii

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=p91si41rj2q.fsf@google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.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.