From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: isolating history with buffer-local variables Date: Wed, 20 May 2015 17:26:42 -0400 Message-ID: References: <54AE8A33-FB8D-4F63-8BC1-F84DB290EF05@tenpoint.co.nz> <4F35C3B0-4EA7-4B66-8006-F5048B1BF8B4@tenpoint.co.nz> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1432157243 5481 80.91.229.3 (20 May 2015 21:27:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 May 2015 21:27:23 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed May 20 23:27:15 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YvBWD-0003Bp-5v for geh-help-gnu-emacs@m.gmane.org; Wed, 20 May 2015 23:27:13 +0200 Original-Received: from localhost ([::1]:54046 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YvBWC-0000t4-7y for geh-help-gnu-emacs@m.gmane.org; Wed, 20 May 2015 17:27:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49208) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YvBW2-0000s4-4B for help-gnu-emacs@gnu.org; Wed, 20 May 2015 17:27:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YvBVv-0002so-HP for help-gnu-emacs@gnu.org; Wed, 20 May 2015 17:27:02 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:36776) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YvBVv-0002s9-BL for help-gnu-emacs@gnu.org; Wed, 20 May 2015 17:26:55 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YvBVr-00030I-Bd for help-gnu-emacs@gnu.org; Wed, 20 May 2015 23:26:51 +0200 Original-Received: from 206-248-179-22.dsl.teksavvy.com ([206.248.179.22]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2015 23:26:51 +0200 Original-Received: from monnier by 206-248-179-22.dsl.teksavvy.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 May 2015 23:26:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 55 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 206-248-179-22.dsl.teksavvy.com User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:h5CKZd+WqplSo+MCIuFBykOsw4Q= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:104505 Archived-At: > So, all up, for a single edit, I could end up with nine or more uncontrolled > copies or fragments of foo.txt floating around. For normal files, this To the extent that 9 copies is not fundamentally different from 3 copies, I think that it's OK to require the user to explicitly request to skip backups/autosaves via something like: > ;; backup-inhibited: t > ;; eval: (auto-save-mode 0) [ I have backup inhibited globally, FWIW. ] > to foo.conf to prevent the copies being created, but has no simple control > over saved rings and histories. For rings and history, the problem here is the same as for encrypted files, so once we solve the problem for encrypted files, it can be used for these confidential-but-not-encrypted files. > +---------+---------+---------------+---------------+ > |File |Local FS |Fp Ap Bp Hp Rp |Fe - Be Hp Rp | > |loc +---------+---------------+---------------+ > | |LAN |Fp Ap Bp Hp Rp |Fe - Be Hp Rp | > | +---------+---------------+---------------+ > | |Remote |Fp Ap Bp Hp Rp |Fe Ap Be Hp Rp | > +---------+---------+---------------+---------------+ > > Where: > F = visited file (on user save) > A = auto-saves (to ~/.emacs.d/auto-saves) > B = backups (to ~/.emacs.d/backups) > H = minibuffer history (et al) (to ~/.emacs.d/.emacs_history via savehist) > R = kill-ring (et al) (also to ~/.emacs.d/.emacs_history via savehist) As mentioned, please report a bug w.r.t minibuffer histories so your private-mode can more easily make sure data doesn't escape this way. > The results are largely as expected, with the exception of the handling of > auto-saves on remote machines (the remote encrypted gpg was saved in plain > text on the local machine). Perhaps this is a bug. This is very much a severe bug, yes. Please report it. > +---------------+-------------------------------+---------------+ > | PRIVATE | > +---------------+---------------+---------------+---------------+ > |plain-text |plain-text |encrypted |encrypted | > +----+---------+---------------+---------------+---------------+---------------+ I'm not sure we need to distinguish "encrypted+private" from the "normal encrypted" files. I.e. we should treat all encrypted files as private (at least by default). Stefan