From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 397@debbugs.gnu.org
Subject: bug#397: 23.0.60; T in Info when in (dir)
Date: Wed, 27 Apr 2016 11:09:54 -0700 (PDT) [thread overview]
Message-ID: <b018da66-7a95-4b32-b184-baecc0a3af3a@default> (raw)
In-Reply-To: <<83vb33x7b6.fsf@gnu.org>>
> > `Info-toc' should raise an error immediately, if the current node
> > is the top. Something like this, perhaps:
> >
> > (defun Info-toc ()
> > "@@@@@@@@@"
> > (interactive)
> > (when (equal Info-current-file "dir") (error "@@@@@@@@@@@@@@@@@"))
>
> So, from now on, no Info manual can be called "dir" or "dir.info", or
> suchlikes? Does dimming an option in a rarely-used menu really
> justify this? I don't think so.
It was a quick-and-dirty implementation suggestion. I don't
argue for that implementation.
If we put the "real" code for this into an :enable menu guard
then that guard would be (Info-find-node "dir" "*TOC*").
And in the case of your hypothetical manual named "dir", there
could be such a *TOC* node, and in that case the menu item would
be correctly enabled.
> We should look for a better solution, if one exists. If it doesn't,
> then it isn't a catastrophe to have that option be available and fail
> if invoked where it cannot work. No one who knows something about
> Info will invoke that function in this situation, anyway.
Fair enough. Someone might actually try it: use the :enable
guard (Info-find-node "dir" "*TOC*") and see whether it is
in fact onerous. If it is then I agree with (both of) you:
we can do without disabling the menu item.
> > But probably not. `Info-index' does only this:
> > (equal Info-current-file "dir")
>
> Bad, bad Info-index!
;-)
next prev parent reply other threads:[~2016-04-27 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 15:53 bug#397: 23.0.60; T in Info when in (dir) Drew Adams
2016-04-27 16:11 ` Lars Ingebrigtsen
2016-04-27 16:42 ` Drew Adams
2016-04-27 16:47 ` Lars Ingebrigtsen
2016-04-27 17:12 ` Drew Adams
2016-04-27 17:35 ` Lars Ingebrigtsen
2016-04-27 17:46 ` Drew Adams
2016-04-27 17:58 ` Eli Zaretskii
2016-04-27 18:22 ` Andreas Schwab
2016-04-27 19:27 ` Eli Zaretskii
2016-04-30 20:08 ` Juri Linkov
[not found] ` <<5a64ed8a-d9c7-4b33-b63a-11d83b7dab99@default>
[not found] ` <<83vb33x7b6.fsf@gnu.org>
2016-04-27 18:09 ` Drew Adams [this message]
2016-04-27 18:28 ` Lars Ingebrigtsen
2022-03-21 22:06 ` Lars Ingebrigtsen
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=b018da66-7a95-4b32-b184-baecc0a3af3a@default \
--to=drew.adams@oracle.com \
--cc=397@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).