unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephan Mueller <Stephan.Mueller@microsoft.com>
Cc: emacs-devel@gnu.org
Subject: Re: Recent commit modifying mark-whole-buffer (master/aeb613ea95b7970e66d663ec5cba54e9ec0528fa)
Date: Fri, 29 Apr 2016 09:45:12 +0300	[thread overview]
Message-ID: <83wpngx69z.fsf@gnu.org> (raw)
In-Reply-To: <CY1PR0301MB1659092A179F1D2F5CB45B84F0650@CY1PR0301MB1659.namprd03.prod.outlook.com> (message from Stephan Mueller on Thu, 28 Apr 2016 22:25:09 +0000)

> From: Stephan Mueller <Stephan.Mueller@microsoft.com>
> Date: Thu, 28 Apr 2016 22:25:09 +0000
> 
> Kaushal Modi <kaushal.modi@gmail.com> writes:
> " Question:
> " - Should we revert mark-whole-buffer to its definition before this commit and
> "  mark-whole-buffer and make the cursor intangible by default in minibuffer
> "  prompt?
> 
> +1 for "make minibuffer prompt generally inaccessible" to be more like the rest of the world (at least the parts I interact with).  If that allows restoring mark-whole-buffer to its traditional, obvious, trivial implementation, then +1 more.

Emacs always allowed one to enter the prompt, if one wanted badly
enough.  One use case where this is handy is when you need to copy the
prompt text to somewhere else; I'm sure there are others.  AFAIR, we
make the prompt a field so that simple commands like C-a don't enter
it inadvertently; that measure was good enough for us for many years.
Why isn't it good enough now?

The initial message in bug #21874 provides no rationale for the
request (which seems to be a feature request, not a bug that needs to
be fixed).  So I'm not sure why we want to make such significant
changes in behavior due to that bug report.

Do I understand correctly that the proposed change will disallow doing
that, without some complicated operations that many users won't even
know about?  If so, I object.  Working with minibuffer prompts is too
hardwired into the muscle memory of veteran Emacs users for us to
change that in radical ways at this point.  If some newcomers get
surprised by some of the aspects of that behavior, I say let them get
used, it doesn't take too long to do that.



  reply	other threads:[~2016-04-29  6:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28 20:24 Recent commit modifying mark-whole-buffer (master/aeb613ea95b7970e66d663ec5cba54e9ec0528fa) Kaushal Modi
2016-04-28 21:40 ` Lars Ingebrigtsen
2016-04-28 22:25   ` Stephan Mueller
2016-04-29  6:45     ` Eli Zaretskii [this message]
2016-04-29 12:23       ` Lars Ingebrigtsen
2016-04-29 12:41         ` Eli Zaretskii
2016-04-29 12:48           ` Lars Ingebrigtsen
2016-04-29 13:28             ` Eli Zaretskii
2016-04-29 14:28               ` Lars Ingebrigtsen
2016-04-29 17:06                 ` Eli Zaretskii
2016-04-29 17:43                   ` Kaushal Modi
2016-04-29 18:33                     ` Eli Zaretskii
2016-04-30  7:51                     ` John Wiegley
     [not found]               ` <<87y47w5w0p.fsf@gnus.org>
     [not found]                 ` <<83bn4swdif.fsf@gnu.org>
2016-04-29 19:28                   ` Drew Adams
2016-04-29 20:00                     ` Eli Zaretskii
2016-04-29 20:18                       ` Lars Ingebrigtsen
2016-04-29 20:24                         ` Eli Zaretskii
2016-04-29 20:30                           ` Lars Ingebrigtsen
2016-04-30 14:19                             ` Stefan Monnier
2016-04-30 14:34                               ` Lars Ingebrigtsen
2016-04-30 14:41                                 ` Stefan Monnier
2016-04-30 14:51                                   ` Lars Ingebrigtsen
     [not found]                       ` <<87eg9ouq24.fsf@gnus.org>
     [not found]                         ` <<83shy4ups9.fsf@gnu.org>
2016-04-29 21:48                           ` Drew Adams
2016-04-30  5:23                             ` Eli Zaretskii
     [not found]                             ` <<83r3dnvfed.fsf@gnu.org>
2016-04-30 19:06                               ` Drew Adams
     [not found]                     ` <<83y47wuqvg.fsf@gnu.org>
2016-04-29 21:49                       ` Drew Adams
2016-04-30  5:24                         ` Eli Zaretskii
     [not found]                         ` <<83pot7vfch.fsf@gnu.org>
2016-04-30 19:14                           ` Drew Adams
2016-04-30 14:15       ` Stefan Monnier
2016-04-30 19:18         ` Drew Adams

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=83wpngx69z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Stephan.Mueller@microsoft.com \
    --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).