From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: generate 3) S-mouse-2: follow link in new window
Date: Sun, 23 Sep 2007 15:00:02 +0300 [thread overview]
Message-ID: <87k5qha8xp.fsf@jurta.org> (raw)
In-Reply-To: <DHEEKFAFJEFOJHLCFPFDAEDMCBAA.drew.adams@oracle.com> (Drew Adams's message of "Sun\, 23 Sep 2007 02\:47\:55 -0700")
> 3. It would also be helpful to bind `S-mouse-2' in Info to a command that
> follows an Info link in a new window.
Or better to use bindings like in Web browsers: `S-mouse-1' to follow
a link in a new frame, `C-mouse-1' to follow a link in a new window
(or a tab when tabs will be implemented in Emacs).
> That way, a user could keep the `L' or the `I' buffer (or a TOC or an
> index or any other node) open while visiting its links in another window
> (or frame, with non-nil pop-up-frames).
>
> I have used this definition:
>
> (defun Info-mouse-follow-nearest-node-new-window (click)
> "Open the link at the mouse pointer in a new window."
> (interactive "e")
> (Info-mouse-follow-nearest-node click t)) ; t no good now
>
> But that particular implementation no longer works, because someone over the
> course of Emacs 22 development removed the optional FORK argument to
> `Info-follow-nearest-node' and `Info-mouse-follow-nearest-node'. (Why?)
`Info-mouse-follow-nearest-node' never had the FORK argument.
`Info-follow-nearest-node' still has it, but there were plans to remove it.
> Regardless of how it is implemented, it would be useful. You can do the same
> thing by cloning the buffer and then following a link, but it is particulaly
> handy to do this with just a mouse click.
This is a question of implementation. We can implement a command that
will clone the current manual, follow the requested node in a new copy,
and display it accordingly to the command arguments.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-09-23 12:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 9:47 generate 1) virtual index and 2) other pages for Info; 3) S-mouse-2: follow link in new window Drew Adams
2007-09-23 11:09 ` Bastien
2007-09-23 12:03 ` generate 2) other pages for Info Juri Linkov
2007-09-23 12:38 ` Lennart Borgman (gmail)
2007-09-23 14:17 ` Bastien
2007-09-23 19:18 ` Eli Zaretskii
2007-09-24 0:27 ` Bastien
2007-09-23 21:54 ` Richard Stallman
2007-09-23 11:41 ` generate 1) virtual index Juri Linkov
2007-09-23 16:43 ` Drew Adams
2007-09-23 20:42 ` Juri Linkov
2007-09-24 7:09 ` Drew Adams
2007-09-23 11:45 ` generate 2) other pages for Info Juri Linkov
2007-09-23 12:00 ` Juri Linkov [this message]
2007-09-23 16:44 ` generate 3) S-mouse-2: follow link in new window Drew Adams
2007-09-23 19:14 ` Lennart Borgman (gmail)
2007-09-23 20:42 ` Drew Adams
2007-09-24 0:20 ` Johan Bockgård
2007-09-24 1:22 ` Stefan Monnier
2007-09-24 2:01 ` Drew Adams
2007-09-24 18:20 ` Richard Stallman
2007-09-27 21:21 ` Drew Adams
2007-09-27 21:34 ` David Kastrup
2007-09-27 21:34 ` Stefan Monnier
2007-09-27 21:41 ` Drew Adams
2007-09-27 21:53 ` Drew Adams
2007-09-28 19:04 ` Richard Stallman
2007-09-28 19:33 ` Drew Adams
2007-09-28 22:22 ` David Kastrup
2007-09-30 2:19 ` Drew Adams
2007-09-30 8:54 ` David Kastrup
2007-09-30 23:37 ` Drew Adams
2007-09-30 23:49 ` David Kastrup
2007-10-01 1:36 ` Richard Stallman
2007-09-25 23:39 ` info.el patch to open node in new window [was: generate 3) S-mouse-2: follow link in new window] Drew Adams
2007-09-26 8:56 ` Juri Linkov
2007-09-26 15:02 ` Drew Adams
2007-09-29 22:44 ` info.el patch to open node in new window Juri Linkov
2007-09-30 2:19 ` Drew Adams
2007-09-29 22:41 ` generate 3) S-mouse-2: follow link " Juri Linkov
2007-09-30 2:19 ` Drew Adams
2007-09-29 22:43 ` Juri Linkov
2007-09-30 2:18 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 17:10 Davis Herring
2007-09-24 17:22 ` Drew Adams
2007-09-24 18:33 ` Davis Herring
2007-09-24 21:30 ` Drew Adams
2007-09-24 19:27 ` David Kastrup
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=87k5qha8xp.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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 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.