emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#23067: closed (25.0.92; A detail in the doc of que


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#23067: closed (25.0.92; A detail in the doc of query-replace)
Date: Fri, 25 Mar 2016 10:10:02 +0000

Your message dated Fri, 25 Mar 2016 13:09:39 +0300
with message-id <address@hidden>
and subject line Re: bug#23067: 25.0.92; A detail in the doc of query-replace
has caused the debbugs.gnu.org bug report #23067,
regarding 25.0.92; A detail in the doc of query-replace
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23067: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23067
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.0.92; A detail in the doc of query-replace Date: Sun, 20 Mar 2016 03:02:00 +0100
Hello,

"In Transient Mark mode, if the mark is active, operate on the contents
of the region.  Otherwise, operate from point to the end of the buffer."

I think the second sentence is confusing (wrong).  The command operates
up to `point-max'.


Thanks,

Michael.



In GNU Emacs 25.0.92.8 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9)
 of 2016-03-19 built on drachen
Repository revision: 9ab03f27fad7b1ae68dda7a2effd075658dcf184
Windowing system distributor 'The X.Org Foundation', version 11.0.11802000
System Description:     Debian GNU/Linux testing (stretch)




--- End Message ---
--- Begin Message --- Subject: Re: bug#23067: 25.0.92; A detail in the doc of query-replace Date: Fri, 25 Mar 2016 13:09:39 +0300
> From: Michael Heerdegen <address@hidden>
> Date: Sun, 20 Mar 2016 03:02:00 +0100
> 
> "In Transient Mark mode, if the mark is active, operate on the contents
> of the region.  Otherwise, operate from point to the end of the buffer."
> 
> I think the second sentence is confusing (wrong).  The command operates
> up to `point-max'.

Thanks.  I fixed the doc string of this function (and of a few others
in the same file).

However, I must say that it makes very little sense to me to make such
corrections only in a couple of functions, when we have gobs of them
with the same problem in the doc strings, so much so that I wonder
whether "end of buffer" isn't already a widely accepted synonym of
"end of the buffer's accessible portion", and we shouldn't bother,
certainly not with fixing that one function at a time.  I won't be
surprised if the same issue has crept in the manuals as well.

Please, let's not start another prolonged dispute that leads nowhere.
Instead, if someone really thinks this stuff should be spelled out in
documentation, that someone is kindly requested to submit a patch that
fixes _all_ of the instances where we don't say that explicitly.  TIA.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]