From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: hw Newsgroups: gmane.emacs.devel Subject: Re: Some developement questions Date: Mon, 27 Aug 2018 00:51:38 +0200 Organization: my virtual residence Message-ID: <871sakzssu.fsf@himinbjorg.adminart.net> 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> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1535323842 10474 195.159.176.226 (26 Aug 2018 22:50:42 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 26 Aug 2018 22:50:42 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cc: spacibba@aol.com, radon.neon@gmail.com, flexibeast@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 27 00:50:38 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 1fu3rh-0002cj-O4 for ged-emacs-devel@m.gmane.org; Mon, 27 Aug 2018 00:50:38 +0200 Original-Received: from localhost ([::1]:50640 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fu3tn-0004W9-VO for ged-emacs-devel@m.gmane.org; Sun, 26 Aug 2018 18:52:47 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fu3t6-0004Vr-9M for emacs-devel@gnu.org; Sun, 26 Aug 2018 18:52:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fu3t5-0005aE-AX for emacs-devel@gnu.org; Sun, 26 Aug 2018 18:52:04 -0400 Original-Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::9]:14330) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fu3t3-0005Us-Du; Sun, 26 Aug 2018 18:52:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1535323919; s=strato-dkim-0002; d=adminart.net; h=Sender:References:Message-ID:Date:In-Reply-To:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=SPJmCPy9MUWCxSDkgLYnB6uVa6wGLiWwyq72q1p2QQU=; b=NZexFZ4LQ2zWRLO5yVR75TZ/kfY57+I+sW+wmkc4RFrxKP9gDr0gR9yPzChNLF+lLz s3NUVL8+arJsqVjnTqN+vCORuoTf1vbq20k+1aDZIS1CmpZEOOtgVmhEzKHVXJyWvAk6 x0dqX9fBxTOGkrPAP3F2vx1P0gNZcGPhIsV6nThMVVjZL+Vf0L9pIqlbY2WxP/vJyB9k mwIE9X+fyd74dVftklEolTm/NuVnSopkCwEHtqGUugH1mJIjIbEogiu/DW61f+vXdgLo Txvl0tOrI79lGWVj8da4C2Kh9wmbc6ypQr35qhg8PI+GhZtDOu5Eg5pNjKNA2v8l4MkD /nUg== X-RZG-AUTH: ":O2kGeEG7b/pS1FS4THaxjVF9w0vVgfQ9xGcjwO5WMRo5c+h5ceMqQWZ3yrBp+AVdIIwXjneEe9k=" X-RZG-CLASS-ID: mo00 Original-Received: from lee by himinbjorg.adminart.net with local (Exim 4.90_1) (envelope-from ) id 1fu3sx-0000ss-6N; Mon, 27 Aug 2018 00:51:55 +0200 In-Reply-To: <83wosd5h3x.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 26 Aug 2018 17:37:22 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a01:238:20a:202:5300::9 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:228954 Archived-At: Eli Zaretskii writes: >> From: hw >> Cc: spacibba@aol.com, Eli Zaretskii , flexibeast@gmail.com, emacs-devel >> Date: Sun, 26 Aug 2018 03:33:08 +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. >> 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". I can understand that it might not be able to open the display on the client because I started the X session without it listening to the network. But if I do that and allow the server to access my X session, everything goes unencrypted over the network. I don't exactly understand how emacsclient fails because it can not open the terminal. 'emacsclient -f ~/.emacs.d/server/server -nw' would never work on a remote client. I can 'ssh -Y server' and then start an xterm which shows up on the client. With the current Emacs server setup, starting emacsclient fails because it insists on using display :0, ignoring that I'm telling it otherwise. I do not really want to use 'ssh -Y server', run Emacs on the server and then use frames that appear on the client unless the Emacs session on the server would survive the sudden disappearance of the frames. Last time I checked, Emacs did not survive this, even not Emacs-lucid. So how do I get this to work?