Re: Some developement questions

[Eli Zaretskii]

> From: hw <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden,  address@hidden
> Date: Mon, 27 Aug 2018 00:51:38 +0200
> 
> >> In theory, Emacs could find out which variables are being defined in
> >> ~/.emacs and whether they are already known or not, like by checking if
> >> they can successfully be described.  The unknown variables could then be
> >> brought to the attention of the user.
> >
> > That would definitely annoy me, for example: I have a lot of settings
> > of "unknown" variables, in preparation for when they will become known
> > (when the corresponding package is loaded on demand).
> 
> Hmm, yes, there would have to be a way to tell the check which unknown
> variables it must not consider.  Would it bother you when there was
> merely a function you needed to run to perform the check?  I wouldn't
> consider it useful that the check would be done on every startup.

If there were a setting to disable the check, that'd be fine by me.
Of course, then we'd have an argument about the default of that
setting ;-)

> >> Unfortunately, the Emacs server can still not be used from remote
> >> machines --- or can it finally?
> >
> > Yes, it can.
> 
> Wow!  Finally!  Awesome!  I have to see if I can get that to work right
> now!  That would be incredibly helpful ...
> 
> Hm, no, it doesn't work:  It says it connects, but then it either says
> "*ERROR*: Display :0 can't be opened" or "*ERROR*: Could not open file:
> /dev/pts/35".
> [...]
> So how do I get this to work?

Read about that in the manual, nodes "TCP Emacs server" and the
description of the --tramp-prefix= option under "emacsclient Options".