emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Maus <dmaus@ictsoc.de>
To: Julien Danjou <julien@danjou.info>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] Wash output of org-encrypt-entry, take 3
Date: Sun, 10 Apr 2011 22:08:03 +0200	[thread overview]
Message-ID: <87wrj127ks.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <sa37hbsefzy.fsf@cigue.easter-eggs.fr>

[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]

At Mon, 21 Mar 2011 14:54:09 +0100,
Julien Danjou wrote:
> [1  <text/plain; utf-8 (quoted-printable)>]
> On Fri, Mar 18 2011, Óscar Fuentes wrote:
> > 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.
> 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.

> > Second, the empty line just wastes space and it is plain ugly once we
> > remove the first one with the Version text.
> This line is required by the protocol.


> > 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.
> 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.

  -- David
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

      reply	other threads:[~2011-04-10 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 22:25 [PATCH] Wash output of org-encrypt-entry, take 3 Óscar Fuentes
2011-03-20 20:34 ` Bernt Hansen
2011-03-20 21:10 ` Bernt Hansen
2011-03-21 13:54 ` Julien Danjou
2011-04-10 20:08   ` David Maus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wrj127ks.wl%dmaus@ictsoc.de \
    --to=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=julien@danjou.info \
    --cc=ofv@wanadoo.es \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).