[Top][All Lists]

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

[debbugs-tracker] bug#11061: closed (24.0.94; emacsclient -n not working

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#11061: closed (24.0.94; emacsclient -n not working)
Date: Sun, 25 Mar 2012 13:18:01 +0000

Your message dated Sun, 25 Mar 2012 14:45:54 +0200
with message-id <address@hidden>
and subject line Re: bug#11061: 24.0.94; emacsclient -n not working
has caused the debbugs.gnu.org bug report #11061,
regarding 24.0.94; emacsclient -n not working
to be marked as done.

(If you believe you have received this mail in error, please contact

11061: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11061
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.0.94; emacsclient -n not working Date: Wed, 21 Mar 2012 22:28:34 -0400
After successfully starting up Emacs with `runemacs -Q' on Windows via:

D:\emacs-24.0.94\bin\runemacs.exe -Q --eval "(setq server-host
system-name)" -f server-start

I then try to invoke emacsclient from a Windows command prompt (CMD.EXE)

emacsclient -n non-existant-file.txt

I see the message:

D:\emacs-24.0.94\bin\emacsclient.exe: connected to remote socket at

However, I don't get an Emacs frame/buffer with non-existant-file.txt
nor do I get returned to the command prompt.

I have to type Ctrl-C to get back to the command prompt.

This worked in the previous version of Emacs (02/26/2012) located at:


In GNU Emacs (i386-mingw-nt5.1.2600)
 of 2012-03-19 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --no-opt --enable-checking --cflags

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US
  value of $XMODIFIERS: nil
  locale-coding-system: cp949
  default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  jabber-activity-mode: t
  show-paren-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo> 
<menu-bar> <help-menu> <send-emacs-bug-report>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Source file `d:/emacs-24.0.94/lisp/server.el' newer than byte-compiled

Load-path shadows:
None found.

(shadow sort gnus-util mail-extr emacsbug message format-spec rfc822 mml
easymenu mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail regexp-opt rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mail-utils server time-date tooltip
ediff-hook vc-hooks lisp-float-type mwheel dos-w32 disp-table ls-lisp
w32-win w32-vars tool-bar dnd fontset image fringe lisp-mode register
page menu-bar rfn-eshadow timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core frame cham georgian utf-8-lang
misc-lang vietnamese tibetan thai tai-viet lao korean japanese hebrew
greek romanian slovak czech european ethiopic indian cyrillic chinese
case-table epa-hook jka-cmpr-hook help simple abbrev minibuffer button
faces cus-face files text-properties overlay sha1 md5 base64 format env
code-pages mule custom widget hashtable-print-readable backquote
make-network-process multi-tty emacs)

--- End Message ---
--- Begin Message --- Subject: Re: bug#11061: 24.0.94; emacsclient -n not working Date: Sun, 25 Mar 2012 14:45:54 +0200
On Sun, Mar 25, 2012 at 06:18,  <address@hidden> wrote:
> I had waited for about 5 minutes with each attempt.
> However, after I rebooted, everythime works as expected.

OK, some transient network problem, then.

> Rebooting seemed to make this problem non-reproducable, so this
> report can be closed.

OK, thanks.


--- End Message ---

reply via email to

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