From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Maus Subject: Re: [PATCH] Wash output of org-encrypt-entry, take 3 Date: Sun, 10 Apr 2011 22:08:03 +0200 Message-ID: <87wrj127ks.wl%dmaus@ictsoc.de> References: <87bp182hiw.fsf@wanadoo.es> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Sun_Apr_10_22:08:03_2011-1"; micalg=pgp-sha256; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=42211 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q90vb-0000EX-6N for emacs-orgmode@gnu.org; Sun, 10 Apr 2011 16:08:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q90va-00056V-0Y for emacs-orgmode@gnu.org; Sun, 10 Apr 2011 16:08:11 -0400 Received: from mail.xlhost.de ([213.202.242.118]:58897 helo=mysql1.xlhost.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q90vZ-00056C-RG for emacs-orgmode@gnu.org; Sun, 10 Apr 2011 16:08:09 -0400 In-Reply-To: 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: Julien Danjou Cc: =?UTF-8?B?w5NzY2Fy?= Fuentes , emacs-orgmode@gnu.org --pgp-sign-Multipart_Sun_Apr_10_22:08:03_2011-1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable At Mon, 21 Mar 2011 14:54:09 +0100, Julien Danjou wrote: >=20 > [1 ] > On Fri, Mar 18 2011, =C3=93scar Fuentes wrote: >=20 > > 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. >=20 > This is true only if you modify the content of the entry, so I'm not > sure there's a real harm done here. gpg --no-emit-version Can be configured in gpg.conf. >=20 > > Second, the empty line just wastes space and it is plain ugly once we > > remove the first one with the Version text. >=20 > This line is required by the protocol. +1 >=20 > > 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. >=20 > I do not feel the right place and/or way to fix and encoding bug. Don't think this is a bug at all: The gpg executable (as well as plain Emacs btw ) uses whatever is deemed the line-ending signature of the operating system. Washing out the ^M overrules the system settings and enforces the assumption that lines are terminated by a single newline. This sound like a bad idea: You might get the opposite situation -- the Org file uses "DOS"-style CRLF and the encrypted block doesn't. Best, -- David --=20 OpenPGP... 0x99ADB83B5A4478E6 Jabber.... dmjena@jabber.org Email..... dmaus@ictsoc.de --pgp-sign-Multipart_Sun_Apr_10_22:08:03_2011-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iF4EAREIAAYFAk2iDiMACgkQma24O1pEeObgEQD+Mysr64v4CVvzfpN5He5V3+hQ AXXDvzTukKJxIwNwdhsBAIQNXDH6DkruLMtf0w6p262Za4MtlMP4CVPjhcQEe/g5 =lLZK -----END PGP SIGNATURE----- --pgp-sign-Multipart_Sun_Apr_10_22:08:03_2011-1--