On 8/7/2012 11:14 AM, Eli Zaretskii wrote:
>> Date: Tue, 07 Aug 2012 01:19:27 -0700
>> From: Daniel Colascione <dancol@dancol.org>
>>
>> @@ -188,9 +192,7 @@ struct option longopts[] =
>>    { "socket-name",	required_argument, NULL, 's' },
>>  #endif
>>    { "server-file",	required_argument, NULL, 'f' },
>> -#ifndef WINDOWSNT
>>    { "display",	required_argument, NULL, 'd' },
>> -#endif
>>    { "parent-id", required_argument, NULL, 'p' },
>>    { 0, 0, 0, 0 }
>>  };
> 
> How will the -d switch react in the native Windows build of
> emacsclient?
> 

NT-native emacsclient would bail out and die. Hrm: maybe it'd be better to
retain the functionality? But what would we do with DISPLAY information there?
It'd be nice if any emacsclient could work with any emacs, but I don't think
we're there yet.