From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 25.0.04: Feature Request: Make called-interactively-p's argument optional
Date: Sun, 03 Jul 2016 22:31:20 +0300 [thread overview]
Message-ID: <831t3ar01j.fsf@gnu.org> (raw)
In-Reply-To: <b279e6f7-ab6b-9791-3265-a3203f9f3ba6@online.de> (message from Andreas Röhler on Sun, 3 Jul 2016 20:36:56 +0200)
> From: Andreas Röhler <andreas.roehler@online.de>
> Date: Sun, 3 Jul 2016 20:36:56 +0200
>
> On 30.06.2016 17:30, Eli Zaretskii wrote:
> >> From: Robert Weiner <rsw@gnu.org>
> >> Date: Thu, 30 Jun 2016 10:25:26 -0400
> >> Cc: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
> >>
> >> It would be nice if John and Eli could just make some final decision
> >> on the interactive-p issue and then put that one to rest, whatever it
> >> is.
> > I have no opinion on the subject, except the general principle that we
> > shouldn't back up on past decisions unless they are truly disastrous,
>
> They are.
Once again, please back up your assertions with some clear-cut
evidence. A disastrous decision should not be hard to show as such:
just come up with a couple of examples where this decision causes a
disaster. This:
> This is another example from a couple of issues which went
> wrong last years.
> Code was made swollen up and complicated, simple solutions rejected.
>
> BTW a characteristic design-flaw beyond mentioned last days is around
> use-region-p.
> With use-empty-active-region or region-active-p it hardly comes to an end.
doesn't even come close.
next prev parent reply other threads:[~2016-07-03 19:31 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 [this message]
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=831t3ar01j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--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 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).