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: Wed, 03 Dec 2003 16:10:33 GMT	[thread overview]
Message-ID: <jwvllptlxju.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: 87ekvmp0s4.fsf@herrrossi.mmweg.rwth-aachen.de

>     No, I only mean a GNU/Linux box with a windowmanager which gives
>     me multiple virtual desktops (LarsWM, 4 virtual desktops). 

Well, I don't know of any standard way for the window-manager to tell
clients about the existence of such virtual workspaces, so from
Emacs's point of view, those don't exist.

My window-manager (ctwm) automatically brings a window into the current
workspace if an application asks for its window to be de-iconified.

This means that for me pop-to-buffer in your example will cause the *info*
frame to be brought into the current workspace.

>     No, I think pop-to-buffer/pop-up-frame is working as advertised,
>     it's just not what I want---or I haven't figured out how to
>     configure it right for my needs.

Maybe you can get your window-manager to do its part.

>     On XEmacs, this function forces the creation of a new frame that
>     shows the *info* buffer on the virtual desktop I am looking
>     at---and yes, if another frame somewhere else is displaying *info*
>     too, I end up having two frames displaying *info*.

Ah, so you're working around a limitation of your window manager (or maybe
a limitation in Emacs w.r.t understanding what your window-manager does) by
forcing the creation of a new frame no-matter-what.
Of course, you can do that as well with emacsclient.
E.g. something like (100% guaranteed non-tested code):

   emacsclient --eval '(progn (select-frame (make-frame)) (info))'


-- Stefan

  reply	other threads:[~2003-12-03 16: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
2003-12-02 23:44         ` Stefan Monnier
2003-12-03 12:02           ` Thorsten Bonow
2003-12-03 16:10             ` Stefan Monnier [this message]
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=jwvllptlxju.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).