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

[dhruva <dhruvakm@gmail.com>]

Recipe for reproducing the problem:

1. Start emacs with server
2. Use emacsclient to open a file (with -n option not to wait)
3. Start another emacs with server
4. Use emacsclient as in #2 (it will open in emacs on #3 for me)
5. Kill emacs started in #3
6. Use emacsclient and you get the error!

On Fri, Oct 31, 2008 at 7:08 PM, dhruva <dhruvakm@gmail.com> wrote:
> Hi,
>  I figured it out... I guess. The port is same as pid of the process.
> I guess I had 2 sessions of emacs running and one in which server was
> not. The client finds the one without the server running and tries to
> connect to a port with the pid of that emacs. Hence, it fails. I think
> we should use some UDP based discovery of running emacs if it is not
> too tough...
>
> On Fri, Oct 31, 2008 at 6:40 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
>> On Fri, Oct 31, 2008 at 13:58, dhruva <dhruvakm@gmail.com> wrote:
>>
>>> The second failure is because I did not use '-a' option to emacsclient
>>
>> You're right. I'm having a bad day, and it seems I'm not thinking straight.
>>
>> Now the question is, you were getting a "connect" error. How is that
>> related to entering the if()? When I run emacsclient, the error I get
>> is "could not get terminal name", as expected.
>>
>>  Juanma
>>
>
>
>
> --
> Contents reflect my personal views only!
>



-- 
Contents reflect my personal views only!