[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: dhruva
Subject: Re: emacsclient on WXP does not work (as it used to)
Date: Fri, 31 Oct 2008 20:51:33 +0530

Even this works!

diff --git a/lib-src/emacsclient.c b/lib-src/emacsclient.c
index 0bbc385..6d2d2c4 100644
--- a/lib-src/emacsclient.c
+++ b/lib-src/emacsclient.c
@@ -1446,6 +1446,9 @@ main (argc, argv)
       char *tty_name = NULL;
 #ifndef WINDOWSNT
       tty_name = ttyname (fileno (stdout));
+      type = "CMD";
+      tty_name = "CON";

       if (! tty_name)

On Fri, Oct 31, 2008 at 8:14 PM, Eli Zaretskii <address@hidden> wrote:
>> Date: Fri, 31 Oct 2008 15:14:42 +0100
>> From: "Juanma Barranquero" <address@hidden>
>> Cc: "Eli Zaretskii" <address@hidden>, address@hidden
>> On Fri, Oct 31, 2008 at 15:13, Chong Yidong <address@hidden> wrote:
>> > This was for bug#1267.
>> >
>> > The goal was to pass the tty to the Emacs server even if we're supposed
>> > to use the current frame, because in daemon mode, if the "current frame"
>> > is the fake daemon frame, we wan to be able to fall back on using that
>> > tty.
>> Yes, but that should be conditional on Windows, where tty is (I think) not 
>> used.
> What will happen if we provide an emulation of `ttyname' for Windows,
> which would just return something like "CONOUT$"?  Since daemon mode
> is not used on Windows, I think the tty name should never be used by
> server.el on Windows.
> Can you try this and see if it works?  If it does, then we can fix
> this problem much cleaner, and even remove an existing ifndef.

Contents reflect my personal views only!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]