From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?=C3=93scar_Fuentes?= Subject: Wash output of org-encrypt-entry, take 2 Date: Fri, 18 Mar 2011 23:23:03 +0100 Message-ID: <87fwqk2hmg.fsf@wanadoo.es> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=38022 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q0i4m-0001jj-CB for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 18:23:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q0i4k-0002J2-TR for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 18:23:20 -0400 Received: from lo.gmane.org ([80.91.229.12]:55093) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q0i4k-0002Il-MZ for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 18:23:18 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Q0i4i-0005So-RW for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 23:23:16 +0100 Received: from 27.red-79-158-173.staticip.rima-tde.net ([79.158.173.27]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 18 Mar 2011 23:23:16 +0100 Received: from ofv by 27.red-79-158-173.staticip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 18 Mar 2011 23:23:16 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org With a gpg executable with default settings, org-encrypt-entry produces output like this: [2. text/plain] -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.10 (GNU/Linux) jA0EAwMCBWZVym6QMPVgyTxreTb1AEL3uTO+qCh2lR9/Qxk4nEMpPr9/RwNk95Gb slUra9X+N+qSWghEHvvxY0Ol8Yw9Ko4n7JVhHFs= =E4vw -----END PGP MESSAGE----- The first line (Version:...) can change from machine to machine and over time (as gpg is updated with a new version.) This is problematic when the file is stored under version control, because as you decrypt and encrypt an entry that line will change and create differences among the file on the workspace and the file stored on VC. Second, the empty line just wastes space and it is plain ugly once we remove the first one with the Version text. Finally, on some systems (mostly Windows) depending on how your Emacs and gpg are configured, ^M characters may appear at the end of every line of gpg output once it is inserted on the Emacs buffer. This happens when the buffer uses Unix line-endings but gpg uses DOS line-endings. The patch removes all that junk from the encrypted text just before it is inserted on the buffer. I'm assuming that the transformations made by this patch are uncontroversial and desirable. If anyone actually prefers to keep that noise on his encrypted org entries, an alternative implementation that uses a configurable list of regexps is trivial to implement, but then every user would have to do some job for achieving the same result.