From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 54175@debbugs.gnu.org
Subject: bug#54175: 27.2; Info-follow-reference completions in reverse order
Date: Sun, 27 Feb 2022 19:09:18 +0200 [thread overview]
Message-ID: <83a6ecnsn5.fsf@gnu.org> (raw)
In-Reply-To: <5EDDF26F-4350-469D-B98C-99D7743E9424@gmail.com> (message from Howard Melman on Sun, 27 Feb 2022 11:59:35 -0500)
> From: Howard Melman <hmelman@gmail.com>
> Date: Sun, 27 Feb 2022 11:59:35 -0500
>
> On Feb 27, 2022, at 11:49 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> From: Howard Melman <hmelman@gmail.com>
> >> Date: Sun, 27 Feb 2022 10:43:49 -0500
> >>
> >> 2. It's not unreasonable to expect a completion table to be in a meaningful
> >> order when there is one.
> >
> > But what is a meaningful order in this particular case, why is it
> > more meaningful than the current order?
>
> I believe I explained this. It is the order they are found in the node. It means
> the offered candidates appear to me in the order I see them in the
> node.
But if your position is near the end of the buffer, the first
cross-reference in the node will also be the one that's the farthest.
I'm not sure I understand the utility of such an order.
next prev parent reply other threads:[~2022-02-27 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 0:17 bug#54175: 27.2; Info-follow-reference completions in reverse order Howard Melman
2022-02-27 7:17 ` Eli Zaretskii
2022-02-27 15:43 ` Howard Melman
2022-02-27 16:36 ` Eli Zaretskii
2022-02-27 16:52 ` Howard Melman
2022-02-27 16:49 ` Eli Zaretskii
2022-02-27 16:59 ` Howard Melman
2022-02-27 17:09 ` Eli Zaretskii [this message]
2022-02-27 17:18 ` Howard Melman
2022-02-27 17:31 ` Eli Zaretskii
2022-02-27 17:50 ` Howard Melman
2022-05-04 14:46 ` Howard Melman
2022-05-05 11:30 ` Lars Ingebrigtsen
2022-05-05 14:00 ` Howard Melman
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=83a6ecnsn5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54175@debbugs.gnu.org \
--cc=hmelman@gmail.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).