unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: gnu/emacs client --create-frame somehow?
Date: Tue, 02 Dec 2003 23:44:47 GMT	[thread overview]
Message-ID: <jwvptf6n684.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: 87ekvmzx9w.fsf@herrrossi.mmweg.rwth-aachen.de

>     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.

You mean it will reuse a pre-existing window and change the buffer
displayed in that window ?
In that case indeed, pop-to-buffer might not be what you want, but I don't
understand when a frame is going to be opened, then, unless you're thinking
of a multiple-X-server situation, in which case the --display argument of
emacsclient should be what you want (although it's only be lightly tested).

Or do you mean that if the buffer is already displayed in a window but
on another display, then pop-to-buffer fails to open a new window/frame
on the right display ?  That might be: there are many such bugs in
a multiple-display situation.  Please report such problems to gnu.emacs.bug
via M-x report-emacs-bug.
    
>     (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.

But I can't easily check what the above code does: are you trying to force
the creation of a new frame that shows the same *info* buffer a second time
on the same display or is it on a separate display ?


        Stefan

  reply	other threads:[~2003-12-02 23:44 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
2003-12-02 23:44         ` Stefan Monnier [this message]
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=jwvptf6n684.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
    --to=monnier@iro.umontreal.ca \
    /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).