From: Lars Ingebrigtsen <larsi@gnus.org>
To: Robert Weiner <rsw@gnu.org>
Cc: 23857@debbugs.gnu.org, rswgnu@gmail.com
Subject: bug#23857: Emacs 25.0.94: Info-read-node-name fails outside of Info buffers; patch to fix included
Date: Tue, 25 Jun 2019 14:22:47 +0200 [thread overview]
Message-ID: <m3d0j1dfc8.fsf@gnus.org> (raw)
In-Reply-To: <CA+OMD9jjaAiy-VcWXQWnU=U5EzPymkkW5GEhGE-1VWRD+WmTcA@mail.gmail.com> (Robert Weiner's message of "Mon, 27 Jun 2016 16:04:15 -0400")
Robert Weiner <rsw@gnu.org> writes:
> Info-read-node-name is useful even when the current buffer is not an
> Info buffer because it can be used to specify a file from which to read
> Info node name completions, e.g. if you want to produce a link within an
> Emacs Lisp file to a specific Info node.
(Info-read-node-name "(File)Node: ")
=> "Top This is the top of the INFO tree"
It seems like a very mode-specific function to me...
[...]
> ! (condition-case nil
> ! (Info-build-node-completions-1)
> ! (error nil)))))
And just catching all errors isn't a good way to solve these things,
because it may be covering up other errors we want to catch.
Given both these things, I don't think this is a good idea, and I'm
closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-06-25 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:04 bug#23857: Emacs 25.0.94: Info-read-node-name fails outside of Info buffers; patch to fix included Robert Weiner
2019-06-25 12:22 ` 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=m3d0j1dfc8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=23857@debbugs.gnu.org \
--cc=rsw@gnu.org \
--cc=rswgnu@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).