From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org, Stephan.Mueller@microsoft.com
Subject: Re: Recent commit modifying mark-whole-buffer (master/aeb613ea95b7970e66d663ec5cba54e9ec0528fa)
Date: Fri, 29 Apr 2016 16:28:01 +0300 [thread overview]
Message-ID: <83fuu4wnmm.fsf@gnu.org> (raw)
In-Reply-To: <87shy4a8d4.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 29 Apr 2016 14:48:39 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stephan.Mueller@microsoft.com, emacs-devel@gnu.org
> Date: Fri, 29 Apr 2016 14:48:39 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I assumed it was an uncontroversial fix -- there are many commands that
> >> work differently in the minibuffer exactly because we don't want to
> >> include the prompt.
> >
> > Fix of what problem? I was saying that the problem is not clear to
> > me?
>
> Well, the problem was that mark-whole-buffer marked the prompt in the
> minibuffer. :-)
And why is that a problem? The prompt _is_ part of the buffer text.
> >> I don't quite follow. If you want to mark the prompt, there's a
> >> gazillion ways of doing that, including `C-u C-a C-<SPC>'. Or just hold
> >> down `<left>'. :-)
> >
> > Are we mis-communicating? I thought the suggestion on the table, to
> > which I objected, was to make the prompt have a property that would
> > preclude doing all these things.
> >
> >> (By the way, I think it would be nice if `<left>' didn't enter the
> >> prompt.)
> >
> > And I don't understand why you think so. We were allowed to do so for
> > eons, why suddenly change that?
>
> I think we must be miscommunicating. On the one hand you seem to be
> suggesting that we should make the prompt more special than it is now,
> and on the other hand, you seem to be suggesting that we shouldn't,
> because we haven't for eons?
I didn't suggest any changes, no. The prompt is special, but it
doesn't need to be more so.
next prev parent reply other threads:[~2016-04-29 13:28 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
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 [this message]
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=83fuu4wnmm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stephan.Mueller@microsoft.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).