unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: emacsclient/server finished, documentation, raising frames
Date: Tue, 07 Nov 2006 12:23:17 +0000	[thread overview]
Message-ID: <45507AB5.5050601@gnu.org> (raw)
In-Reply-To: <f7ccd24b0611070400m21990e1av9eafe32f6ee7b400@mail.gmail.com>

Juanma Barranquero wrote:
> [All the following is Windows-specific; please skip it if you're not
> interested.]
>
> I've just checked in a patch to emacsclient that allows it to bring
> Emacs to front just before passing it a file. "Allows" is the
> operative word: Emacs won't be the foreground app unless it does
> something to be, that is, call `raise-frame'.
Is this really Windows specific? It doesn't seem like it should be, as 
it is a user preference whether Emacs should jump to the front when 
emacsclient is used. Currently the frame is raised whenever Emacs was 
iconified, and there doesn't seem to be a user option to control this. 
Personally I think there should be a user option that controls whether 
Emacs is raised, whether iconified or not.

> 1) Modify `server-switch-buffer' to raise the frame. Hairy.
> `server-switch-buffer' already does quite a lot of things to try to
> determine the right buffer/window/frame (and in some cases it already
> calls `raise-frame'), so I don't think it is wise to mess with it.
I think this is the best place for it though, as this code has knowledge 
about which frame needs to be raised.

  reply	other threads:[~2006-11-07 12:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 12:00 emacsclient/server finished, documentation, raising frames Juanma Barranquero
2006-11-07 12:23 ` Jason Rumney [this message]
2006-11-07 14:11   ` Stefan Monnier
2006-11-07 14:27     ` Kim F. Storm
2006-11-07 14:48     ` Juanma Barranquero
2006-11-07 15:00       ` Kim F. Storm
2006-11-07 17:07       ` Stefan Monnier
2006-11-07 17:23         ` Juanma Barranquero
2006-11-07 18:22           ` Stefan Monnier
2006-11-07 21:59             ` Juanma Barranquero
2006-11-09  1:47               ` Juanma Barranquero
2006-11-09 23:30                 ` Juanma Barranquero
2006-11-09 23:45                   ` Lennart Borgman
2006-11-09 23:50                     ` Juanma Barranquero
2006-11-11  2:09                     ` Richard Stallman
2006-11-11 11:44                       ` Lennart Borgman
2006-11-11 14:16                       ` Juanma Barranquero
2006-11-12  5:14                         ` Richard Stallman
2006-11-12  5:23                           ` Juanma Barranquero
2006-11-10  9:57                 ` Juanma Barranquero
2006-11-07 14:49     ` Andreas Schwab
2006-11-07 17:09       ` Stefan Monnier
2006-11-07 17:16         ` Andreas Schwab
2006-11-07 17:36         ` Juanma Barranquero
2006-11-07 14:55     ` Jason Rumney
2006-11-07 15:27   ` Juanma Barranquero

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=45507AB5.5050601@gnu.org \
    --to=jasonr@gnu.org \
    --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 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).