From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Howard Melman Newsgroups: gmane.emacs.bugs Subject: bug#54175: 27.2; Info-follow-reference completions in reverse order Date: Sun, 27 Feb 2022 12:50:38 -0500 Message-ID: References: <7A89A71F-708C-4217-989C-2E9990759E13@gmail.com> <831qzopymk.fsf@gnu.org> <83bkysntjv.fsf@gnu.org> <5EDDF26F-4350-469D-B98C-99D7743E9424@gmail.com> <83a6ecnsn5.fsf@gnu.org> <1C706C79-657B-4B02-B028-0D1BEB448A8B@gmail.com> <838rtwnrms.fsf@gnu.org> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25981"; mail-complaints-to="usenet@ciao.gmane.io" To: 54175@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Feb 27 18:51:11 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nONhO-0006eV-MB for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 27 Feb 2022 18:51:10 +0100 Original-Received: from localhost ([::1]:40832 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nONhN-0002FT-K2 for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 27 Feb 2022 12:51:09 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:54038) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nONhG-0002FJ-65 for bug-gnu-emacs@gnu.org; Sun, 27 Feb 2022 12:51:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37034) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nONhF-0005Pe-UJ for bug-gnu-emacs@gnu.org; Sun, 27 Feb 2022 12:51:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nONhF-0002ta-JS for bug-gnu-emacs@gnu.org; Sun, 27 Feb 2022 12:51:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Howard Melman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 27 Feb 2022 17:51:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54175 X-GNU-PR-Package: emacs Original-Received: via spool by 54175-submit@debbugs.gnu.org id=B54175.164598424711110 (code B ref 54175); Sun, 27 Feb 2022 17:51:01 +0000 Original-Received: (at 54175) by debbugs.gnu.org; 27 Feb 2022 17:50:47 +0000 Original-Received: from localhost ([127.0.0.1]:59164 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nONh1-0002t7-18 for submit@debbugs.gnu.org; Sun, 27 Feb 2022 12:50:47 -0500 Original-Received: from mail-qk1-f176.google.com ([209.85.222.176]:43621) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nONgz-0002su-5u for 54175@debbugs.gnu.org; Sun, 27 Feb 2022 12:50:45 -0500 Original-Received: by mail-qk1-f176.google.com with SMTP id z66so8729329qke.10 for <54175@debbugs.gnu.org>; Sun, 27 Feb 2022 09:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=xWibXyPGdOkJqQHYemgLE1oEet817O3TLF8rhFL2KLY=; b=A7oaGQbmUVzSizzjWMj6ay2vvxXRCKpm1IVlDrkTWWyFxiBUbQTlkjpcljTBoit+FS ZObhqJta7V8VTJBADzDf/u6l1mshPrwiJ+sxLuTLODxlshMCjxBkk2JK5Wefis22AeIt G2PoKg5PcOKihm08B1++7CgosKcydG6wYbHCJW1YqA314fwbBR6K3ZdpPM/NYTO4bc+O N3RUAvJYxC+nSGx+Ayr1VT0Vxgmy135T6h29Z6wqmLfXgwTsEPQAx+M00rgzVjFeGL9m B6MPtOJD5h9NHOVut11Bxsumi3zz9jE3twZzMcyt2JGSOtsTo8LUC9lguE1moNhiaiJj rqUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=xWibXyPGdOkJqQHYemgLE1oEet817O3TLF8rhFL2KLY=; b=cWEzmn7tLRXND4eRLC+DxrFcWe2y+fY8C115ZAOKfs+CzfShxjtMpVcqcwjKTro0Oq xGIZWjn3ehWCxj7k83ObYlI6AUDgZRolzj6vv4nG7dY43NKDl0Z2SWczZcgbFqsGxKRW eDKDL4MmgvWVzb8VCNeLztjOexQQSjERMIrE4Qfc1gv02UuNYnt4s6cdMLVNHesaa3mf Ewde2GfNYdA5/TtxgPjjDUKuWdEO7dywjySeNS5U67EIy6dgXtHzXPmsgUChA5D95A8D /g0ZL2aeVX+gQqWQuIioy5W8GZeOlJ3EUmLHPdWrwIQBIRFfZKmc9tw9YOyomU1w3nhZ xSoA== X-Gm-Message-State: AOAM533SgDch8BaBfts2AvLQTAoXJbHAm+45Xr4iYLedhtuDgqvVeNc7 5j+8SwWjExwt2Z02bd4bQK1awZnLqvw= X-Google-Smtp-Source: ABdhPJzYsRC1H4jpUsiXKPWMNVjnWNH6Ft4/J3euOy8wg/MHhQHM9mszC0LsZoL19kZxhM7tqBySUQ== X-Received: by 2002:a05:620a:80f:b0:648:e2e3:532d with SMTP id s15-20020a05620a080f00b00648e2e3532dmr9499612qks.569.1645984239194; Sun, 27 Feb 2022 09:50:39 -0800 (PST) Original-Received: from smtpclient.apple (pool-108-26-204-101.bstnma.fios.verizon.net. [108.26.204.101]) by smtp.gmail.com with ESMTPSA id w8-20020ae9e508000000b0064905055a5esm3964279qkf.92.2022.02.27.09.50.38 for <54175@debbugs.gnu.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Feb 2022 09:50:38 -0800 (PST) In-Reply-To: <838rtwnrms.fsf@gnu.org> X-Mailer: Apple Mail (2.3654.120.0.1.13) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:227737 Archived-At: On Feb 27, 2022, at 12:31 PM, Eli Zaretskii wrote: >=20 >> From: Howard Melman >> Date: Sun, 27 Feb 2022 12:18:49 -0500 >>=20 >>>> I believe I explained this. It is the order they are found in the = node. It means=20 >>>> the offered candidates appear to me in the order I see them in the >>>> node. >>>=20 >>> 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. >>=20 >> It doesn't help in all cases. If you're positioned near the end of = the node >> then you might be positioned near the reference and get it as the = default. >> But when visiting a node you start at the top, and many nodes fit = entirely >> on one screen, so it's a more common case that it will help (again = for a >> imperceptible cost). It's certainly a more intuitive order than what = is returned >> now. >=20 > I don't think I agree. I could understand if the request was to order > them starting from the current position, or to sort them by their > distance from the current position, but starting from the node > beginning sounds as arbitrary as starting from the end. >=20 > In any case, instead of sorting or reversing, an alternative could be > to collect the cross-reference in the desired order to begin with, to > avoid the cost of sorting/reversing. I proposed an easy-to-understand one line fix with negligible = performance impact similar to a previously accepted fix; if someone wants to fix it = with a rewrite of the function I don't object. > And finally, Info-follow-reference is called by other functions, so we > should make sure we don't break them by changing the order. Yes, though given my proposed change is in the call to interactive I = believe it shouldn't affect other non-interactive callers of it. There is code in Info-menu-update "stolen from `Info-follow-reference'" = that builds the dynamic submenu of References. That currently shows references, in = the menu in the same reverse order. It would be nice if those were in some = sensible order; either alphabetical or as found in the node seem more reasonable than what's = there now. Howard