From: Eli Zaretskii <eliz@gnu.org>
To: John Wiegley <jwiegley@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 25.0.04: Feature Request: Make called-interactively-p's argument optional
Date: Wed, 06 Jul 2016 17:48:16 +0300 [thread overview]
Message-ID: <83wpkyn7pr.fsf@gnu.org> (raw)
In-Reply-To: <m2vb0jip41.fsf@newartisans.com> (message from John Wiegley on Tue, 05 Jul 2016 17:31:26 -0700)
> From: John Wiegley <jwiegley@gmail.com>
> Date: Tue, 05 Jul 2016 17:31:26 -0700
> Cc: emacs-devel@gnu.org
>
> >>>>> Dmitry Gutov <dgutov@yandex.ru> writes:
>
> > As the docstring explains, the function in question should be used rarely,
> > if at all. It should follow that the verbosity of its calling convention
> > can't be a significant problem.
>
> If this is the case, I'm curious why this is an issue at all then. Bob, is
> really a problem that needs addressing, or is it just for infrequent
> convenience? If it's only the latter, let's leave this sleeping dog to lie.
IMO, if we want to make a rational decision that would make sense to
most everybody, we need first to define the problem. After reading
this and past discussions, I'm still not sure what the problem(s)
is/are. What's more, I'm not sure anyone else here understands the
actual problem(s) being brought up. Large portions of the discussions
seem to be based on distant experiences, which I'm not sure is
relevant nowadays, and the problems are described very vaguely. A
couple of times that an actual problem was reported (e.g., bug#21083),
it was promptly fixed, but I don't see any updated reports after it
was fixed, it seems people are still claiming the same claims
regardless of the fix.
So: what exactly is the problem? Is it a convenience issue, or are
there some real problems in the recommended replacements for
'interactive-p' (such as 'called-interactively-p')? Do we have
reproducible recipes for the problems the recommended practices
allegedly have? If so, would someone please present these recipes
with the current versions of Emacs, preferably as bug reports?
I'd also ask Stefan to please summarize the reasons for deprecating
'interactive-p' and describe its recommended substitutes for the
popular use cases.
Armed with that knowledge, we can hopefully proceed with the subject:
fix the bugs, clarify the documentation, and make the decision whether
the recommended practices are viable or need some changes.
next prev parent reply other threads:[~2016-07-06 14:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:35 Emacs 25.0.04: Feature Request: Make called-interactively-p's argument optional Robert Weiner
2016-06-28 19:09 ` 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 [this message]
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=83wpkyn7pr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).