From: Thorsten Bonow <thorsten.bonow@post.rwth-aachen.de>
Subject: Re: gnu/emacs client --create-frame somehow?
Date: Tue, 02 Dec 2003 23:10:19 +0100 [thread overview]
Message-ID: <87ekvmzx9w.fsf@herrrossi.mmweg.rwth-aachen.de> (raw)
In-Reply-To: jwv8ylws510.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca
>>>>> "Stefan" == Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> After some testing I think gnuclient's option to set
>> "gnuserv-frame" to "gnuserv-visible-frame-function", which is
>> opening a new frame only if there isn't one already opened on
>> your (virtual) screen and is using the visible frame otherwise,
>> is my preferred solution. Alas, this is not working even with
>> emacsclient from CVS.
Stefan> Huh ? Setting server-window to `pop-to-buffer' does
Stefan> exactly that (provided you configure pop-to-buffer
Stefan> properly of course: by default it does not create new
Stefan> frames).
Sorry, now I'm utterly confused. The way I understood the manual
is, that pop-to-buffer is buffer oriented, meaning that even if I
set pop-up-frames to non-nil, a new frame is only opened if the
buffer is not displayed in another frame. This solves my
LaTeX-Xdvi problem, but doesn't work if I want to force
frame-creation.
gnuserv-visible-frame-function on the other hand is frame
oriented. If there is no frame on my virtual screen, one pops up,
even if the file is already displayed in another buffer.
So with gnuclient, I can solve my LaTeX-Xdvi problem *and* if I
define
(defun my-xemacs-info-other-frame ()
"my-xemacs-info-other-frame"
(interactive)
(let (gnuserv-frame)
(info)))
I can call gnuclient -eval "(my-xemacs-info-other-frame)" and a
frame pops up even if *INFO* is displayed in another frame.
(defun my-info-other-frame ()
"my-info-other-frame"
(interactive)
(let ((pop-up-frames t))
(info-other-window)))
only works with emacsclient if *INFO* isn't displayed somewhere
else.
Sorry about pestering you with this. But I hope to get this right
for my emacsclient/gnuclient wrapper script.
Stefan> Stefan
Toto
--
Contact information and PGP key at
http://www-users.rwth-aachen.de/thorsten.bonow
Now I have a cat. Well, that's not quite accurate. A cat and I have
each other.
Friedman, Kinky (1993), When the cat's away. New York (Wings Books),
421
next prev parent reply other threads:[~2003-12-02 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 16:28 gnu/emacs client --create-frame somehow? Thorsten Bonow
2003-11-27 22:23 ` Stefan Monnier
2003-11-28 0:47 ` Ian Zimmerman
2003-11-28 9:01 ` Thorsten Bonow
2003-12-01 11:03 ` Thorsten Bonow
2003-12-01 19:39 ` Stefan Monnier
2003-12-02 22:10 ` Thorsten Bonow [this message]
2003-12-02 23:44 ` Stefan Monnier
2003-12-03 12:02 ` Thorsten Bonow
2003-12-03 16:10 ` Stefan Monnier
2003-12-01 20:19 ` Kevin Rodgers
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=87ekvmzx9w.fsf@herrrossi.mmweg.rwth-aachen.de \
--to=thorsten.bonow@post.rwth-aachen.de \
/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).