From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: dhruva Newsgroups: gmane.emacs.devel Subject: Re: emacsclient on WXP does not work (as it used to) Date: Fri, 31 Oct 2008 19:10:22 +0530 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1225460443 27699 80.91.229.12 (31 Oct 2008 13:40:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 31 Oct 2008 13:40:43 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 31 14:41:45 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KvuFz-00071I-Kr for ged-emacs-devel@m.gmane.org; Fri, 31 Oct 2008 14:41:44 +0100 Original-Received: from localhost ([127.0.0.1]:34169 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvuEs-0000nU-9T for ged-emacs-devel@m.gmane.org; Fri, 31 Oct 2008 09:40:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KvuEo-0000nA-8X for emacs-devel@gnu.org; Fri, 31 Oct 2008 09:40:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KvuEm-0000mF-MS for emacs-devel@gnu.org; Fri, 31 Oct 2008 09:40:29 -0400 Original-Received: from [199.232.76.173] (port=59794 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvuEm-0000m9-HQ for emacs-devel@gnu.org; Fri, 31 Oct 2008 09:40:28 -0400 Original-Received: from ti-out-0910.google.com ([209.85.142.190]:38499) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KvuEj-0001zI-Fj; Fri, 31 Oct 2008 09:40:26 -0400 Original-Received: by ti-out-0910.google.com with SMTP id u5so657068tia.10 for ; Fri, 31 Oct 2008 06:40:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=mTj109RwxuLYZ1S3m6NeRFb6uDZ4svLnhL+UBBMhzOw=; b=EnuDU9Je9IOgWhmuGosp3L21XDt6+PqXHdyILyfeYfPP/ZKcE6S0kG4Z/hCB4aTkiu rgjYSvgBRkVY4RYb/6kL9oMh770BwsfBUcCWdfu+ArKIYoHJzT0a6weyFA41l1vNCo4k DMHDdtIkjTuYJWWQl+R9FMJS7xyd69w70LUSk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=g9pseDEIKpLT+4a9O6TFLH5lO+2F59a6Cyl2m8IBc6Z41smF3N7tOBquJWgTACRpnj 1T3d6xicHEPde3OOS0dYEHZZjwQ2zvpLj8xeOsx/8VgKgnBtvcfjMonl22ni3pO/8HTE 7q7t1I9Mh8mEzrgrCJoER3VRyt4qKI57y6BO0= Original-Received: by 10.110.37.17 with SMTP id k17mr4779690tik.26.1225460422839; Fri, 31 Oct 2008 06:40:22 -0700 (PDT) Original-Received: by 10.110.93.2 with HTTP; Fri, 31 Oct 2008 06:40:22 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:105202 Archived-At: 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 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 wrote: >> On Fri, Oct 31, 2008 at 13:58, dhruva 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!