From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 397@debbugs.gnu.org
Subject: bug#397: 23.0.60; T in Info when in (dir)
Date: Wed, 27 Apr 2016 18:11:45 +0200 [thread overview]
Message-ID: <87eg9rhvzy.fsf@gnus.org> (raw)
In-Reply-To: <007c01c8cca4$686e6fb0$c2b22382@us.oracle.com> (Drew Adams's message of "Thu, 12 Jun 2008 08:53:07 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> `T' in Info when you are at the directory level (dir), should either
> raise an error or DTRT.
>
> To DTRT, it could do either of these:
>
> - return to the directory listing (which is useless),
> which is the top-level TOC
> - show the contents of all manuals (pretty costly),
> which is the detailed TOC
>
> Currently, what `T' does is worse than useless. It shows this, where
> (dir) and the second Top are links to the same place - the directory
> you just came from:
>
> Up: (dir)
> File: toc, Node: Top
>
> Table of Contents
> *****************
>
> Top.
This seems like it's fixed now. If I `T' in the top level node, it just
says "user-error: No such node or anchor: *TOC*".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-27 16:11 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg9rhvzy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=397@debbugs.gnu.org \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.