[Top][All Lists]

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

Re: Some developement questions

From: Eli Zaretskii
Subject: Re: Some developement questions
Date: Sat, 01 Sep 2018 21:47:39 +0300

> From: hw <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden,  address@hidden
> Date: Fri, 31 Aug 2018 02:40:30 +0200
> > Assuming they are separate: for the first one, is using the -dDISPLAY
> > option (without any client) what you want?  And for the second, did
> > you try using server-use-tcp?
> I tried both.  Without the -d option, emacs and emacsclient both seem to
> ignore the DISPLAY variable, and only with -d, they try to use the
> display they should use.

I think this is expected behavior.  Does it solve your use case?  If
not, why not?

> >> I understand that the Emacs server can not open the virtual terminal
> >> when using 'emacsclient -nw' because from its perspective, that is a
> >> remote file.
> >
> > I'm afraid I don't understand why you need to run "emacsclient -nw" on
> > another machine.  Why not remotely login and run emacsclient there?
> That's because I want to use emacsclient with a remote Emacs server and
> because I would have to log in to run emacsclient on the server.  I
> wouldn't be able to use Emacs in an X frame, either, unless I'd switch
> the monitor over to the server and run an X server there.

You explicitly mentioned -nw, so how is X frame relevant here?

> Why would I want to run the emacsclient on the same machine as the Emacs
> server?

Why do you want to run emacsclient at all?  IOW, I still don't
understand what is it that you are trying to accomplish.

reply via email to

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