[Top][All Lists]

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

bug#11091: 24.0.94; emacsclient -t

From: Dani Moncayo
Subject: bug#11091: 24.0.94; emacsclient -t
Date: Mon, 26 Mar 2012 00:10:43 +0200


>From a cmd.exe terminal:
* emacs -Q
* M-x server-start RET

Then, from another cmd.exe terminal:
* emacsclient -t some-file

According to the manual [1], the expected behavior would be to open
"some-file" in a new frame inside the second terminal, but I see that
a new graphical frame is created instead.

Also, if I repeat the experiment starting with "emacs -Q -nw", the
effect is that a new frame is created in the first terminal, when TRT
would be to create the frame in the second terminal.

--- Footnotes ------

[1] Quotation from (info "(emacs) emacsclient Options")

       Create a new Emacs frame on the current text-only terminal,
       instead of using an existing Emacs frame.  Emacs can open a
       text-only terminal even if it was started in another text-only
       terminal, or on a graphical display.  If you omit a filename
       argument while supplying this option, the new frame displays the
       `*scratch*' buffer.  *Note Buffers::.

In GNU Emacs (i386-mingw-nt6.1.7601)
 of 2012-03-23 on DANI-PC
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --with-gcc (4.6) --no-opt --enable-checking --cflags
 -IC:/emacs/libs/gnutls-3.0.16/include -IC:/emacs/libs/jpeg-6b-4/include
 -IC:/emacs/libs/libpng-1.4.10 -IC:/emacs/libs/libxpm-3.5.8/include
 -IC:/emacs/libs/libxpm-3.5.8/src -IC:/emacs/libs/tiff-3.8.2-1/include

Dani Moncayo

reply via email to

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