From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
help-gnu-emacs@gnu.org
Subject: RE: call function in other window ?
Date: Sun, 21 May 2017 15:58:15 -0700 (PDT) [thread overview]
Message-ID: <bd7d2841-2f4c-47ec-9a00-9577c20b02e5@default> (raw)
In-Reply-To: <77FFF9DB-058E-4C00-B8C7-1AF22112AEE4@gmail.com>
> > You should use both, IMO. Info manuals often provide additional
> > information that expands and enhances the doc strings.
>
> As I wrote, I (still) prefer to read the manuals as PDFs in an external
> reader. The main advantage is that I can easily move from a manual to
> another while I can only have one info buffer opened in Emacs, or maybe I
> have not yet found the way to keep a number of manuals opened at the same
> time in Emacs.
`M-n' is bound to `clone-buffer' in `Info-mode-map'. Use it to get
an Info clone of the current node - buffer `*info*<2>' etc. Then
navigate from either of the two buffers for the node. Etc.
IOW, you can have as many Info buffers as you like open at the
same time. Each has its own history (Back etc.).
Remember that in any mode, and Info mode is no exception, `C-h m'
is your friend. It tells you, among many other things, that `M-n'
selects "a new cloned Info buffer in another window".
Ask Emacs.
next prev parent reply other threads:[~2017-05-21 22:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 15:35 call function in other window ? Jean-Christophe Helary
2017-05-20 20:25 ` Drew Adams
2017-05-20 22:43 ` Jean-Christophe Helary
2017-05-20 23:50 ` Emanuel Berg
2017-05-21 1:27 ` Drew Adams
2017-05-21 1:58 ` Emanuel Berg
2017-05-21 2:39 ` Jean-Christophe Helary
2017-05-21 10:07 ` Emanuel Berg
2017-05-21 10:16 ` Jean-Christophe Helary
2017-05-21 10:50 ` Joost Kremers
2017-05-21 11:08 ` Jean-Christophe Helary
2017-05-21 13:52 ` Emanuel Berg
2017-05-21 15:05 ` Eli Zaretskii
2017-05-21 15:14 ` Jean-Christophe Helary
2017-05-21 15:56 ` Emanuel Berg
2017-05-22 6:39 ` Jean-Christophe Helary
2017-05-22 21:18 ` Emanuel Berg
2017-05-22 22:26 ` Jean-Christophe Helary
2017-05-22 22:42 ` Kaushal Modi
2017-05-23 0:20 ` Emanuel Berg
2017-05-23 0:19 ` Emanuel Berg
2017-05-23 7:10 ` tomas
2017-05-23 7:44 ` Emanuel Berg
2017-05-23 7:57 ` tomas
2017-05-23 8:14 ` Emanuel Berg
2017-05-23 8:54 ` tomas
2017-05-23 12:58 ` Emanuel Berg
2017-05-23 13:03 ` Jean-Christophe Helary
2017-05-23 13:14 ` Emanuel Berg
2017-05-23 19:18 ` tomas
2017-05-23 20:25 ` Tomas Nordin
2017-05-23 21:02 ` John Ankarström
2017-05-24 19:40 ` Emanuel Berg
2017-05-24 7:26 ` tomas
2017-05-21 15:59 ` Eli Zaretskii
2017-05-21 22:58 ` Drew Adams [this message]
[not found] ` <<83tw4enqtl.fsf@gnu.org>
2017-05-21 23:00 ` Drew Adams
2017-05-21 13:48 ` Emanuel Berg
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=bd7d2841-2f4c-47ec-9a00-9577c20b02e5@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jean.christophe.helary@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.
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).