From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 38183-done@debbugs.gnu.org
Subject: bug#38183: 26.3; Doc about equality of markers
Date: Fri, 15 Nov 2019 21:26:35 +0200 [thread overview]
Message-ID: <83sgmp0wlw.fsf@gnu.org> (raw)
In-Reply-To: <2e1f5720-317d-47e5-886d-bb06d4ee15af@default> (message from Drew Adams on Fri, 15 Nov 2019 10:27:27 -0800 (PST))
> Date: Fri, 15 Nov 2019 10:27:27 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 38183@debbugs.gnu.org
>
> Just know that as one user it took me a while
> to find the information.
>
> I started in the Markers section of the manual,
> and I had difficulty finding that `equal'
> includes buffer comparison (`equal' example
> uses only the same buffer).
"Overview of Markers" starts by saying what components are entailed in
a marker, so what 'equal' compares should be clear from that.
> Then, after finding that info, I had difficulty
> finding how to compare markers only numerically
> (nothing in the Markers section).
That's described under '='.
It is impractical to have every piece of information described
together in the same place as every other possibly related piece of
information, as that will lead to endless repetitions.
next prev parent reply other threads:[~2019-11-15 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<104e3572-fe9c-42b8-a099-769389ff1588@default>
[not found] ` <<<83eey92s7m.fsf@gnu.org>
[not found] ` <<dff3319b-b0d9-4137-a732-33ac97f031c7@default>
[not found] ` <<83tv7511r3.fsf@gnu.org>
2019-11-15 18:27 ` bug#38183: 26.3; Doc about equality of markers Drew Adams
2019-11-15 19:26 ` Eli Zaretskii [this message]
[not found] <<104e3572-fe9c-42b8-a099-769389ff1588@default>
[not found] ` <<83eey92s7m.fsf@gnu.org>
2019-11-15 17:26 ` Drew Adams
2019-11-15 17:35 ` Eli Zaretskii
2019-11-12 19:03 Drew Adams
2019-11-15 13:18 ` Eli Zaretskii
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=83sgmp0wlw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38183-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).