From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: emacsclient's option decoding code
Date: Mon, 03 Nov 2008 22:06:27 +0200 [thread overview]
Message-ID: <uod0wvakc.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b0811030412g2f281128k411eba1376a1d3e8@mail.gmail.com>
> Date: Mon, 3 Nov 2008 13:12:33 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
>
> The following proof-of-concept patch seems to work (at the cost of
> adding windows-specific conditions).
Thanks, but I'd like to look for a cleaner patch, one that doesn't add
new ifdef's.
> --- lisp/server.el 30 Oct 2008 15:50:01 -0000 1.171
> +++ lisp/server.el 3 Nov 2008 12:06:49 -0000
> @@ -631,10 +631,12 @@
> ;; This is a leftover, see above.
> (environment . ,(process-get proc 'env))))
> - (frame (make-frame-on-display
> + (frame (if (eq system-type 'windows-nt)
> + (make-frame params)
> + (make-frame-on-display
> (or display
> (frame-parameter nil 'display)
> (getenv "DISPLAY")
> (error "Please specify display"))
> - params)))
> + params))))
> (server-log (format "%s created" frame) proc)
> (select-frame frame)
>
Here' I think it's unclean that the w32 port has make-frame-on-display
fboundp, but it's dysfunctional when called. If make-frame-on-display
can be made to work on Windows, provided that `display' is nil (or
maybe it should ignore `display' even if non-nil?), that would be a
cleaner and more general change.
next prev parent reply other threads:[~2008-11-03 20:06 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 14:04 emacsclient's option decoding code Eli Zaretskii
2008-11-02 2:13 ` Stefan Monnier
2008-11-02 21:45 ` Chong Yidong
2008-11-02 22:00 ` Juanma Barranquero
2008-11-02 23:18 ` Chong Yidong
2008-11-03 0:50 ` Juanma Barranquero
2008-11-03 4:14 ` Eli Zaretskii
2008-11-03 12:12 ` Juanma Barranquero
2008-11-03 20:06 ` Eli Zaretskii [this message]
2008-11-03 20:19 ` Chong Yidong
2008-11-04 4:20 ` Eli Zaretskii
2008-11-04 16:40 ` Chong Yidong
2008-11-06 11:56 ` Juanma Barranquero
2008-11-03 21:26 ` Juanma Barranquero
2008-11-04 4:19 ` Eli Zaretskii
2008-11-06 12:08 ` Juanma Barranquero
2008-11-07 9:53 ` Eli Zaretskii
2008-11-07 11:42 ` Juanma Barranquero
2008-11-07 11:47 ` Juanma Barranquero
2008-11-07 14:36 ` Eli Zaretskii
2008-11-07 14:42 ` Juanma Barranquero
2008-11-10 18:22 ` Juanma Barranquero
2008-11-10 18:36 ` Chong Yidong
2008-11-10 23:33 ` Juanma Barranquero
2008-11-11 4:09 ` Eli Zaretskii
2008-11-11 4:14 ` Chong Yidong
2008-11-11 21:16 ` Eli Zaretskii
2008-11-11 9:39 ` Juanma Barranquero
2008-11-11 15:37 ` Juanma Barranquero
2008-11-11 21:24 ` Eli Zaretskii
2008-11-11 23:36 ` Juanma Barranquero
2008-11-12 4:22 ` Eli Zaretskii
2008-11-12 9:41 ` Juanma Barranquero
2008-11-12 19:14 ` Eli Zaretskii
2008-11-12 21:05 ` Juanma Barranquero
2008-11-13 4:12 ` Eli Zaretskii
2008-11-13 8:34 ` Juanma Barranquero
2008-11-12 19:37 ` Eli Zaretskii
2008-11-12 2:31 ` Stefan Monnier
2008-11-12 9:33 ` Juanma Barranquero
2008-11-12 15:56 ` Stefan Monnier
2008-11-12 16:37 ` Juanma Barranquero
2008-11-12 17:13 ` Stefan Monnier
2008-11-13 1:16 ` Lennart Borgman
2008-11-13 4:18 ` Eli Zaretskii
2008-11-13 9:00 ` Juanma Barranquero
2008-11-13 15:45 ` Dan Nicolaescu
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:08 ` Dan Nicolaescu
2008-11-12 19:36 ` Eli Zaretskii
2008-11-12 20:56 ` Stefan Monnier
2008-11-13 4:10 ` Eli Zaretskii
2008-11-13 4:29 ` mail
2008-11-13 20:54 ` Eli Zaretskii
2008-11-13 21:27 ` mail
2008-11-13 22:30 ` Eli Zaretskii
2008-11-13 23:54 ` mail
2008-11-13 20:03 ` Juri Linkov
2008-11-13 20:40 ` mail
2008-11-13 21:08 ` Thorsten Bonow
2008-11-13 22:01 ` Thorsten Bonow
2008-11-15 2:58 ` Evil Boris
2008-11-07 14:35 ` Eli Zaretskii
2008-11-03 14:45 ` Juanma Barranquero
2008-11-03 19:59 ` Eli Zaretskii
2008-11-03 20:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uod0wvakc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.