Re: emacsclient on WXP does not work (as it used to)

[dhruva]

The second failure is because I did not use '-a' option to emacsclient

On Fri, Oct 31, 2008 at 6:22 PM, Juanma Barranquero <address@hidden> wrote:
> On Fri, Oct 31, 2008 at 13:46, dhruva <address@hidden> wrote:
>
>> The following patch fixes this issue since tty and TERM does not make
>> sense on windows (a wild guess though) ...
>
> Yes, I said as much.
>
> That does not answer the question, why are you getting two different
> messages, one for connect (presumably from set_tcp_socket) and the
> other from fail via the main() code we're discussing.
>
> Which arguments / env vars did you use when running that emacsclient?
>
>  Juanma
>



-- 
Contents reflect my personal views only!