From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10784@debbugs.gnu.org, tim@tim-landscheidt.de
Subject: bug#10784: 23.1; info doesn't follow link in Bison TOC
Date: Mon, 14 Sep 2020 13:50:43 +0200 [thread overview]
Message-ID: <871rj4d1bg.fsf@gnus.org> (raw)
In-Reply-To: <83r4xyy7rh.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 Feb 2012 19:15:30 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Yes, it definitely should. And it already does, just not
> consistently. E.g., if, instead of typing RET on that menu line, you
> type "m RET", you get to the right node without any error messages.
[...]
> I'm not sure this is TRT. First, we should convert _any_ whitespace,
> not just a sequence of SPC characters, to a single SPC. Second, I
> think it would be better to have a single function for this job and
> call it from all the places that need to produce a canonical node
> name.
The bug was still present on the trunk, so I've now done this.
> I see at least one other place (`Info-extract-menu-node-name')
> where we need to do the same, and possibly one more in
> `Info-fontify-node'. If we do this in each place individually, we
> will have inconsistent bugs, whereas we want _consistent_ bugs ;-)
Indeed. I had a quick skim-through of Info-fontify-node, but it's a 422
line function, and I'm not sure what bit should be changed here...
> Finally, I think the right place to do this is in Info-find-node, not
> Info-find-node-2.
Done.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-09-14 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 22:06 bug#10784: 23.1; info doesn't follow link in Bison TOC Tim Landscheidt
2012-02-12 21:15 ` Juri Linkov
2012-02-13 17:15 ` Eli Zaretskii
2020-09-14 11:50 ` Lars Ingebrigtsen [this message]
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=871rj4d1bg.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=10784@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tim@tim-landscheidt.de \
/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).