[Top][All Lists]

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

Re: [multi-tty] X or tty

From: David Kastrup
Subject: Re: [multi-tty] X or tty
Date: Fri, 18 May 2007 22:14:40 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux)

csant <address@hidden> writes:

> On Fri, 18 May 2007 21:09:12 +0200, Károly Lőrentey
> <address@hidden>  wrote:
>>    1. Emacsclient opens a new frame by default.  It prefers X, but
>>       falls back to tty when necessary or when forced, just like Emacs
>>       itself.
> The simplest case is running server and client both in X, and
> expected behaviour would be for the client to prefer X.  Equally
> obvious would be the case where no X is available, and both the
> server and the client run in console.  I can easily see use cases
> for running the emacs server without X (in screen, or in console)
> and expect emacsclients to draw their frame on the X display they
> are invoked on.  I can a bit less easily imagine cases where you'd
> run the server in X, and clients on a display but wanting them to
> open the frame in terminal.

Funny.  For me it is just the other way round.  The normal case for me
is to run my emacs server in an X session.  Now if I am somewhere on
the road and want to access my Emacs session at home via a modem
connection or similar, I have quite limited bandwidth.  Even though
the ssh session I'll be using into my home computer forwards X
connections, I would not want to make use of it: it would be dead

> Ideally, I'd like the client to inherit by default any `forced'
> flags set to the server, i.e. to start by default with -t when the
> server was deliberately started -nw in an environment that does have
> $DISPLAY set.  This could be overwritten in the client with -d .
> Would that break more expected behaviours than fix some?

I think it would be unexpected.  If you have frequent particular uses,
I think it reasonable to use a shell script wrapper or shell alias or
environment variables for starting your favorite programs with your
favorite options.

Maybe emacsclient could read options from an environment variable
EMACSCLIENT_FLAGS (is that environment name acceptable under Windows?)
on startup, then you could set it there.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

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