emacs-bug-tracker
[Top][All Lists]
Advanced

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

[Emacs-bug-tracker] bug#5486: closed (23.1.91; emacsclient -c not workin


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#5486: closed (23.1.91; emacsclient -c not working on windows)
Date: Sat, 02 Jul 2011 15:19:03 +0000

Your message dated Sat, 02 Jul 2011 23:17:59 +0800
with message-id <address@hidden>
and subject line Re: bug#8783: 24.0.50; emacsclientw.exe behaviour in win32 not 
the same as in linux
has caused the GNU bug report #8783,
regarding 23.1.91; emacsclient -c not working on windows
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8783: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8783
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.1.91; emacsclient -c not working on windows Date: Thu, 28 Jan 2010 01:41:59 -0800 User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1

Running emacsclientw.exe does not behave as expected on windows.

The command that I am attempting to run is:
emacsclientw.exe -c FILE

The behavior I expect is for the file to be opened in a new frame.
The actual behavior is to open the buffer in an existing frame (if
present).



In the windows environmental variables I have set:
ALTERNATE_EDITOR=C:\Programs\text\emacs\bin\runemacs.exe

In my .emacs file I have added:
(server-start)

Here is the behavior that I have observed:

1. Emacs is not running.

  "emacsclientw.exe -c", starts emacs as expected.


2. Emacs running with an existing frame.

  "emacsclientw.exe -c", nothing happens.
  "emacscilentw.exe FILE", file is opened in an existing frame.
  "emacscilentw.exe -c FILE", nothing happens, the file is not opened.
  "emacscilentw.exe -c -n FILE", file is opened in the existing frame
    (new frame expected).

  If I open up a windows command prompt (cmd.exe) and type
  "emacscilent  -c [-n]" I get the following error:

  *ERROR*: Not using an ASCII terminal now; cannot make a new ASCII frame

  This error is not displayed with emacscilentw, otherwise the behavior
  is the same.

If I run the commands from a cygwin xterm terminal (instead of using the
windows terminal), then both emacsclient.exe and emacsclientw.exe work
as expected.  No errors are reported.  Note that this is a normal
windows installation of emacs, NOT a cygwin installation.


I have tested this with emacs-23.1.0 and emacs-23.1.91.


Novimir Pablant
address@hidden




In GNU Emacs 23.1.91.1 (i386-mingw-nt5.1.2600)
 of 2010-01-02 on PRETEST
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'

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: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default enable-multibyte-characters: t

Major mode: Lisp Interaction

Minor modes in effect:
  show-paren-mode: t
  msb-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
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<help-echo> <help-echo> C-x <escape> <escape> <escape>
M-x M-x r e p o r t <down-mouse-1> <mouse-1> - e m
a c s - b u g <return>

Recent messages:
Loading font-lock...done
Loading msb...done
Loading paren...done
For information about GNU Emacs and the GNU system, type C-h C-a.
repeat-complex-command: There are no previous complex commands to repeat

Load-path shadows:
~/.emacs.d/lisp/longlines hides c:/Programs/text/emacs/lisp/longlines
~/.emacs.d/lisp/idlwave hides c:/Programs/text/emacs/lisp/progmodes/idlwave
~/.emacs.d/lisp/idlw-toolbar hides c:/Programs/text/emacs/lisp/progmodes/idlw-toolbar ~/.emacs.d/lisp/idlw-shell hides c:/Programs/text/emacs/lisp/progmodes/idlw-shell ~/.emacs.d/lisp/idlw-help hides c:/Programs/text/emacs/lisp/progmodes/idlw-help ~/.emacs.d/lisp/idlw-complete-structtag hides c:/Programs/text/emacs/lisp/progmodes/idlw-complete-structtag

Features:
(shadow sort mail-extr message smtpmail sendmail regexp-opt ecomplete
rfc822 mml easymenu mml-sec password-cache mm-decode mm-bodies mm-encode
mailcap mail-parse rfc2231 rfc2047 rfc2045 qp ietf-drums mailabbrev
nnheader gnus-util netrc time-date mm-util mail-prsvr gmm-utils wid-edit
mailheader canlock sha1 hex-util hashcash mail-utils emacsbug paren msb
cus-start cus-load server 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 mldrag 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 loaddefs button minibuffer faces cus-face files
text-properties overlay 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#8783: 24.0.50; emacsclientw.exe behaviour in win32 not the same as in linux Date: Sat, 02 Jul 2011 23:17:59 +0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
Jason Rumney <address@hidden> writes:

> Eli Zaretskii <address@hidden> writes:
>
>> AFACT, the -c option is not really supported in the Windows build,
>> because it generally needs the --display argument which Windows
>> doesn't support.
>
> That seems like something that should be fixed.

I fixed this in emacsclient.c with trunk bzr revno 104876.


--- End Message ---

reply via email to

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