GNU bug report logs - #54175
27.2; Info-follow-reference completions in reverse order

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Howard Melman <hmelman <at> gmail.com>
Cc: 54175 <at> debbugs.gnu.org
Subject: bug#54175: 27.2; Info-follow-reference completions in reverse order
Date: Sun, 27 Feb 2022 19:09:18 +0200

> From: Howard Melman <hmelman <at> gmail.com>
> Date: Sun, 27 Feb 2022 11:59:35 -0500
> 
> On Feb 27, 2022, at 11:49 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > 
> >> From: Howard Melman <hmelman <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.