unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: 54175@debbugs.gnu.org
Subject: bug#54175: 27.2; Info-follow-reference completions in reverse order
Date: Sun, 27 Feb 2022 11:52:10 -0500	[thread overview]
Message-ID: <BA6068FB-C20C-4DF6-8AF0-539CF4FE4B12@gmail.com> (raw)
In-Reply-To: <83czj8nu6j.fsf@gnu.org>


> On Feb 27, 2022, at 11:36 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Sun, 27 Feb 2022 10:43:49 -0500
>> 
>> On Feb 27, 2022, at 2:17 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> 
>>> I must say that I'm uneasy with such changes, which punish every user
>>> of Info because some optional completion facility out there would like
>>> that.  It sounds wrong.  Why shouldn't we expect from those optional
>>> completion facilities to do this if and when they need?
>> 
>> 1. I understand your "who has the burden" argument but the cost of 
>> reversing a list of a handful of items is hardly punishment.
> 
> It doesn't have to be a handful, though.  Large manuals, such as
> Emacs and ELisp, have some large nodes with many cross-references.
> For example, see the Glossary node.

I mean if this is the degenerate case... the Emacs 27.2 manual 
glossary has 182 references:

    (setq strlist (make-list 182 "Some String"))
    (benchmark-run 1000 (setq strlist (nreverse strlist)))
    (0.00032399999999999996 0 0.0)

This is not a function that will be typically be called in by code, this is
"cost" will essentially always be paid during an interactive command
done occasionally while the user is reading.  Not doing this for performance
reasons seems like a pointless micro-optimization.

Howard






  reply	other threads:[~2022-02-27 16:52 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 [this message]
2022-02-27 16:49     ` Eli Zaretskii
2022-02-27 16:59       ` Howard Melman
2022-02-27 17:09         ` Eli Zaretskii
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=BA6068FB-C20C-4DF6-8AF0-539CF4FE4B12@gmail.com \
    --to=hmelman@gmail.com \
    --cc=54175@debbugs.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).