From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 23067@debbugs.gnu.org
Subject: bug#23067: 25.0.92; A detail in the doc of query-replace
Date: Fri, 25 Mar 2016 09:08:55 -0700 (PDT) [thread overview]
Message-ID: <acf769e3-7c37-4bc1-b845-bc6a70fe931b@default> (raw)
In-Reply-To: <87io0ay2kw.fsf@web.de>
> > If we do say things like that then that gives credence to an
> > impression that "end of buffer" might not always mean `point-max'
> > (otherwise, we would not contrast it with a description of the buffer
> > end when there is a restriction).
>
> I don't think that "end-of-buffer" is such a good synonym for
> `point-max'.
>
> But OTOH, this is consistent with widely used functions as `eobp' and
> `end-of-buffer'. I didn't realize this when I created this report.
>
> Since we will undoubtedly not rename these functions, it's best to leave
> things as they are. I still think it was not wrong to clear up things
> in this special case, because to the user it could have made sense that
> query-replace indeed would operate up to the real end of the buffer.
I agree that our doc should be clear about which is meant. And I
think we might want to come up with a term for "the real end of the
buffer", as you put it, to make the distinction. I don't have a
concreate suggestion at this point. Sometimes the doc refers to
something like "end of the accessible portion of the buffer", but
that doesn't really help, if we also expect users to understand
"end of the buffer" as the same thing.
It was good to raise the issue generally. Dunno what the best way
to deal with it is.
next prev parent reply other threads:[~2016-03-25 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<87oaa9vrdz.fsf@web.de>
[not found] ` <<<83k2kq27j0.fsf@gnu.org>
[not found] ` <<42d06a78-824b-4661-aa84-845def8ca855@default>
[not found] ` <<837fgq1vr4.fsf@gnu.org>
2016-03-25 14:41 ` bug#23067: 25.0.92; A detail in the doc of query-replace Drew Adams
2016-03-25 15:55 ` Michael Heerdegen
2016-03-25 16:08 ` Drew Adams [this message]
[not found] <<87oaa9vrdz.fsf@web.de>
[not found] ` <<83k2kq27j0.fsf@gnu.org>
2016-03-25 14:13 ` Drew Adams
2016-03-25 14:23 ` Eli Zaretskii
2016-03-20 2:02 Michael Heerdegen
2016-03-20 2:14 ` Drew Adams
2016-03-25 10:09 ` Eli Zaretskii
2016-03-26 22:06 ` John Wiegley
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=acf769e3-7c37-4bc1-b845-bc6a70fe931b@default \
--to=drew.adams@oracle.com \
--cc=23067@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).