From: Drew Adams <drew.adams@oracle.com>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Pierre-Yves Luyten <py@luyten.fr>, emacs-devel@gnu.org
Subject: RE: [PATCH] open bookmark in other frame
Date: Thu, 11 Oct 2018 13:35:58 +0000 (UTC) [thread overview]
Message-ID: <344de0a4-16ae-47ea-91bf-66ad8b380cb0@default> (raw)
In-Reply-To: <87zhvl0x2y.fsf@red-bean.com>
> > IOW, do the equivalent of this, or similar:
> > (let ((pop-up-frames t)) (bookmark-jump-other-window bookmark)
>
> (I haven't studied `pop-up-frames' enough to know whether Drew's back-of-
> the-envelope solution above is the best way, but presumably a little more
> research would lead to the best way.)
Non-nil `pop-up-frames' just makes "other-window" commands
use "other-frame".
I wrote "the equivalent of this, or similar", because someone
will perhaps say that there is a more "modern" way to do the
same thing, involving a `display-buffer' ACTION or something.
I still keep things simple in my own code, partly for backward
compatibility. The above code DTRT, but someone might
prefer a different formulation that does the same thing, or
similar.
next prev parent reply other threads:[~2018-10-11 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 20:14 [PATCH] open bookmark in other frame Pierre-Yves Luyten
2018-10-10 20:16 ` Marcin Borkowski
2018-10-10 21:35 ` Karl Fogel
2018-10-11 11:42 ` Pierre-Yves Luyten
2018-10-10 22:06 ` Drew Adams
2018-10-11 7:19 ` Karl Fogel
2018-10-11 11:30 ` Pierre-Yves Luyten
2018-10-11 13:35 ` Drew Adams [this message]
2018-10-11 21:50 ` Pierre-Yves Luyten
2018-10-11 22:04 ` Drew Adams
2018-10-12 19:45 ` Pierre-Yves Luyten
2018-10-12 21:23 ` Karl Fogel
2018-10-14 19:45 ` Pierre-Yves Luyten
2018-10-16 2:09 ` Karl Fogel
2018-10-16 9:51 ` Pierre-Yves Luyten
2018-10-16 2:10 ` Karl Fogel
2018-11-02 18:55 ` Karl Fogel
2018-11-04 21:10 ` Pierre-Yves Luyten
2018-11-09 0:54 ` Karl Fogel
2018-10-13 15:04 ` Stephen Leake
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=344de0a4-16ae-47ea-91bf-66ad8b380cb0@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=py@luyten.fr \
/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).