From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Some developement questions Date: Mon, 27 Aug 2018 17:45:26 +0300 Message-ID: <83bm9n6f7d.fsf@gnu.org> References: <87sh36inql.fsf@himinbjorg.adminart.net> <8336v6cvem.fsf@gnu.org> <8736v6icgt.fsf@himinbjorg.adminart.net> <83tvnmb958.fsf@gnu.org> <877ekigiiw.fsf@himinbjorg.adminart.net> <837ekhb2me.fsf@gnu.org> <87zhxcbmtr.fsf@himinbjorg.adminart.net> <83in409lub.fsf@gnu.org> <871sanb71j.fsf@himinbjorg.adminart.net> <87k1oeaofu.fsf@ada> <20180825103413.gbm5stsl67j6weow@Ergus> <87k1od7vzf.fsf@himinbjorg.adminart.net> <83wosd5h3x.fsf@gnu.org> <871sakzssu.fsf@himinbjorg.adminart.net> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1535381098 9157 195.159.176.226 (27 Aug 2018 14:44:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 27 Aug 2018 14:44:58 +0000 (UTC) Cc: spacibba@aol.com, radon.neon@gmail.com, flexibeast@gmail.com, emacs-devel@gnu.org To: hw Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 27 16:44:53 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fuIlB-0002Fs-3T for ged-emacs-devel@m.gmane.org; Mon, 27 Aug 2018 16:44:53 +0200 Original-Received: from localhost ([::1]:53579 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuInH-0000zN-7o for ged-emacs-devel@m.gmane.org; Mon, 27 Aug 2018 10:47:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48137) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuIlt-0000yW-Sx for emacs-devel@gnu.org; Mon, 27 Aug 2018 10:45:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fuIlp-0004NV-Qr for emacs-devel@gnu.org; Mon, 27 Aug 2018 10:45:37 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41949) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuIlp-0004NP-Mr; Mon, 27 Aug 2018 10:45:33 -0400 Original-Received: from [176.228.60.248] (port=2600 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fuIlp-0003YV-Ak; Mon, 27 Aug 2018 10:45:33 -0400 In-reply-to: <871sakzssu.fsf@himinbjorg.adminart.net> (message from hw on Mon, 27 Aug 2018 00:51:38 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:228970 Archived-At: > From: hw > Cc: spacibba@aol.com, radon.neon@gmail.com, flexibeast@gmail.com, emacs-devel@gnu.org > 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".