unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lekktu@gmail.com, dhruva <dhruvakm@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacsclient on WXP does not work (as it used to)
Date: Sat, 01 Nov 2008 15:53:17 +0200	[thread overview]
Message-ID: <u8ws3wo1e.fsf@gnu.org> (raw)
In-Reply-To: <e3f230850810310821r103c41f7n61fbea29955f679f@mail.gmail.com>

> Date: Fri, 31 Oct 2008 20:51:33 +0530
> From: dhruva <dhruvakm@gmail.com>
> Cc: "Juanma Barranquero" <lekktu@gmail.com>, cyd@stupidchicken.com, 
> 	emacs-devel@gnu.org
> 
> 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));
> +#else
> +      type = "CMD";
> +      tty_name = "CON";
>  #endif

Thanks.  I checked in a slightly different change, which eliminates
the need for this and one other ifdef.  Could you two please see if
the new version works for you?  Please be sure to try -t and -c
switches as well.




  reply	other threads:[~2008-11-01 13:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 10:35 emacsclient on WXP does not work (as it used to) dhruva
2008-10-31 11:02 ` Juanma Barranquero
2008-10-31 11:15   ` Eli Zaretskii
2008-10-31 12:27     ` Juanma Barranquero
2008-10-31 12:46       ` dhruva
2008-10-31 12:52         ` dhruva
2008-10-31 12:53           ` Juanma Barranquero
2008-10-31 12:57             ` dhruva
2008-10-31 12:52         ` Juanma Barranquero
2008-10-31 12:58           ` dhruva
2008-10-31 13:10             ` Juanma Barranquero
2008-10-31 13:38               ` dhruva
2008-10-31 13:40                 ` dhruva
2008-10-31 14:22                   ` Juanma Barranquero
2008-10-31 14:27                     ` Juanma Barranquero
2008-10-31 14:29                       ` dhruva
2008-10-31 14:13       ` Chong Yidong
2008-10-31 14:14         ` Juanma Barranquero
2008-10-31 14:44           ` Eli Zaretskii
2008-10-31 15:21             ` dhruva
2008-11-01 13:53               ` Eli Zaretskii [this message]
2008-11-01 14:55                 ` Juanma Barranquero
2008-11-01 16:41                   ` Eli Zaretskii
2008-11-01 17:01                   ` Eli Zaretskii
2008-11-02  4:03                     ` Juanma Barranquero
2008-11-02  4:19                       ` Eli Zaretskii
2008-11-01 17:02                   ` Eli Zaretskii
2008-11-02  2:59                     ` dhruva
2008-11-02  4:17                       ` Eli Zaretskii
2008-10-31 21:58           ` Andreas Schwab
2008-10-31 14:31         ` Newsticker is jealous Paul R
2008-10-31 14:43           ` Paul R
2008-10-31 17:21             ` Ulf Jasper

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u8ws3wo1e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dhruvakm@gmail.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).