From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: Chong Yidong <cyd@stupidchicken.com>
Newsgroups: gmane.emacs.devel
Subject: Re: emacsclient's option decoding code
Date: Mon, 10 Nov 2008 13:36:50 -0500
Message-ID: <87d4h377i5.fsf@cyd.mit.edu>
References: <u7i7nwnj5.fsf@gnu.org> <uod0wvakc.fsf@gnu.org>
	<f7ccd24b0811031326s1bbd34c0ue786328e3b5f9b2c@mail.gmail.com>
	<uk5bkunrc.fsf@gnu.org>
	<f7ccd24b0811060408r6695c201nca32de26c0bc0448@mail.gmail.com>
	<u4p2juaje.fsf@gnu.org>
	<f7ccd24b0811070342o30540935i559f1cc9cb79968b@mail.gmail.com>
	<f7ccd24b0811070347x429ebf9fpfbd4a2640c61e7b1@mail.gmail.com>
	<utzajsiw9.fsf@gnu.org>
	<f7ccd24b0811070642h59b2bffn6b3dedf0943a3377@mail.gmail.com>
	<f7ccd24b0811101022y72c3fc32x32d9b08b91f8ac98@mail.gmail.com>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: ger.gmane.org 1226342522 28390 80.91.229.12 (10 Nov 2008 18:42:02 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Mon, 10 Nov 2008 18:42:02 +0000 (UTC)
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
To: "Juanma Barranquero" <lekktu@gmail.com>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 10 19:43:02 2008
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([199.232.76.165])
	by lo.gmane.org with esmtp (Exim 4.50)
	id 1KzbiY-0002BV-MW
	for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2008 19:42:31 +0100
Original-Received: from localhost ([127.0.0.1]:53441 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1KzbhP-0007Lh-Lr
	for ged-emacs-devel@m.gmane.org; Mon, 10 Nov 2008 13:41:19 -0500
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KzbgE-00074j-FQ
	for emacs-devel@gnu.org; Mon, 10 Nov 2008 13:40:06 -0500
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KzbgC-000743-Uu
	for emacs-devel@gnu.org; Mon, 10 Nov 2008 13:40:06 -0500
Original-Received: from [199.232.76.173] (port=56873 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KzbgC-00073x-Md
	for emacs-devel@gnu.org; Mon, 10 Nov 2008 13:40:04 -0500
Original-Received: from cyd.mit.edu ([18.115.2.24]:38031)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <cyd@stupidchicken.com>)
	id 1Kzbcs-0000Cj-Rp; Mon, 10 Nov 2008 13:36:39 -0500
Original-Received: by cyd.mit.edu (Postfix, from userid 1000)
	id C535057E1BA; Mon, 10 Nov 2008 13:36:50 -0500 (EST)
In-Reply-To: <f7ccd24b0811101022y72c3fc32x32d9b08b91f8ac98@mail.gmail.com>
	(Juanma Barranquero's message of "Mon, 10 Nov 2008 19:22:08 +0100")
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)
X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not
	recognized.
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Xref: news.gmane.org gmane.emacs.devel:105538
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/105538>

"Juanma Barranquero" <lekktu@gmail.com> writes:

>  - emacsclient -c causes the same error, because emacsclient thinks
> that "-c" + null DISPLAY => "-t"; I proposed the attached patch (1),
> because even if -t is supported on Windows, the assumption that an
> empty DISPLAY implies a tty frame is false.
>
>  - (make-frame-on-display nil ...) is a synonym of (make-frame ...),
> but only on Windows; I proposed patch (2). Does anyone see a problem
> with it?

These two patches look OK to me.