unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 1761@debbugs.gnu.org
Subject: bug#1761: 23.0.60; Can't reach info nodes that aren't in TOC
Date: Fri, 10 Feb 2012 12:33:39 +0200	[thread overview]
Message-ID: <83aa4r9dvg.fsf@gnu.org> (raw)
In-Reply-To: <m2vcnfnhgw.fsf@igel.home>

> From: Andreas Schwab <schwab@linux-m68k.org>
> Date: Fri, 10 Feb 2012 10:52:15 +0100
> 
> Glenn Morris <rgm@gnu.org> writes:
> 
> > Version: 24.1
> >
> > David Abrahams wrote:
> >
> >> This is arguably a feature request, but it seems so glaring that you
> >> might consider it a bug.  If I'm in an xterm and type `info dbus' I get
> >> a nice info session about emacs/dbus integration.  But there doesn't
> >> seem to be any way to visit the same page from within emacs using
> >> info-mode other than `M-: (info "dbus")'.  This seems needlessly
> >> inconvenient. 
> >
> > Now you can use
> >
> > M-x info-display-manual RET dbus RET
> 
> You can also use g (dbus) in any info buffer.

"g (dbus)" loads the dbus manual into the current info buffer, which
means you lose the previous manual that was loaded there.
info-display-manual doesn't have that problem.





  reply	other threads:[~2012-02-10 10:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  8:01 bug#1761: 23.0.60; Can't reach info nodes that aren't in TOC David Abrahams
2009-01-02  9:11 ` Michael Albinus
2009-01-02 14:48 ` Stephen Berman
2009-01-06 21:06   ` Juri Linkov
2009-01-06 22:17     ` Stephen Berman
2009-01-07  0:48       ` David Abrahams
2012-02-09 21:42 ` Glenn Morris
2012-02-10  9:52   ` Andreas Schwab
2012-02-10 10:33     ` Eli Zaretskii [this message]
2012-02-10 12:08       ` Andreas Schwab
2012-02-10 15:27         ` Eli Zaretskii
2012-02-10 17:57           ` Andreas Schwab
2012-02-12 21:20           ` Juri Linkov

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=83aa4r9dvg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=1761@debbugs.gnu.org \
    --cc=schwab@linux-m68k.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).