From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 38183@debbugs.gnu.org
Subject: bug#38183: 26.3; Doc about equality of markers
Date: Fri, 15 Nov 2019 09:26:45 -0800 (PST) [thread overview]
Message-ID: <dff3319b-b0d9-4137-a732-33ac97f031c7@default> (raw)
In-Reply-To: <<83eey92s7m.fsf@gnu.org>>
> > I think the doc about equality of markers should be improved.
>
> I don't understand what are the practical problems caused by the
> current text in the manual. It seems the information you were after
> is present, so it isn't clear what exactly is the problem here.
>
> It seems that the only problem you have is the place where the details
> of 'equal' for markers are described?
I think the bug report is pretty clear, detailed, and
specific. But to provide a quick summary response:
1. Yes, "Creating Markers" is not the best place for
specifying equality tests between markers.
2. There should be an example for `equal' that shows
inequality when the positions are the same but the
buffers differ.
3. In the section about markers, there should be a
mention of how to compare markers with regard only
to their positions, i.e., use `='.
This, from the bug report, says what I think is needed,
as a minimum:
At the very least, all of that info should be
available in one place, in the section about markers.
And it should include simple examples (like now, but
including `=' and the case of `equal' for two markers
with the same numerical value but for different buffers).
Please consider putting all of the info in the section
about markers, mentioning the different equality tests:
`eq', `equal', and `='.
next parent reply other threads:[~2019-11-15 17: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>
2019-11-15 17:26 ` Drew Adams [this message]
2019-11-15 17:35 ` bug#38183: 26.3; Doc about equality of markers Eli Zaretskii
[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 ` Drew Adams
2019-11-15 19:26 ` 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=dff3319b-b0d9-4137-a732-33ac97f031c7@default \
--to=drew.adams@oracle.com \
--cc=38183@debbugs.gnu.org \
--cc=eliz@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).