Re: --no-window-system and emacsclient

Re: --no-window-system and emacsclient

[Jose A. Ortega Ruiz]

[-- Attachment #1.1: Type: text/plain, Size: 347 bytes --]

Peter Danenberg <pcd@wikitex.org> writes:

> In the latest CVS, emacsclient insists on opening an X frame even when
> emacs is run with -nw; is there a way to tell emacsclient to open a
> frame in the terminal?
>

emacsclient -t

does the trick for me.

hth,
jao
-- 
Go to Heaven for the climate, Hell for the company. - Mark Twain

[-- Attachment #1.2: Type: application/pgp-signature, Size: 193 bytes --]

[-- Attachment #2: Type: text/plain, Size: 152 bytes --]

_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

Re: --no-window-system and emacsclient

[Peter Danenberg]

On Wed, Jan 02, 2008 at 04:43:12AM +0100, Jose A. Ortega Ruiz wrote:
> emacsclient -t

Thanks, Jose; `emacsclient -t' opens up a new frame in the current
terminal, whereas I was looking to open up a buffer in the original
emacs server.

It turned out emacsclient was dutifully reading the DISPLAY
environment variable, and that unsetting it was sufficient to revert
it to the latter behaviour.

--no-window-system and emacsclient

[Peter Danenberg]

In the latest CVS, emacsclient insists on opening an X frame even when
emacs is run with -nw; is there a way to tell emacsclient to open a
frame in the terminal?

Re: --no-window-system and emacsclient

[Peter Danenberg]

On Tue, Jan 01, 2008 at 09:06:30PM -0600, Peter Danenberg wrote:
> [I]s there a way to tell emacsclient to open a frame in the
> terminal?

To answer my own question, it was a DISPLAY issue; unsetting it did
the trick.

Thanks to consolers and snogglethorpe at #emacs on freenode.