Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion EasyPG 0.0.12
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Daiki Ueno  
View profile  
 More options May 29 2007, 11:50 pm
Newsgroups: gnus.ding
From: Daiki Ueno <u...@unixuser.org>
Date: Wed, 30 May 2007 12:50:04 +0900
Local: Tues, May 29 2007 11:50 pm
Subject: Re: EasyPG 0.0.12

>>>>> In <loom.20070529T124032-...@post.gmane.org>
>>>>>    Adrian Aichner <adr...@xemacs.org> wrote:
> > > The biggest issue I found is that ediff-revision will not work with it
> > > out of the box.

> > If I change epa-file-name-regexp to "\\.gpg\\(~\\|\\.~[.0-9]+~\\)?\\'"
> > as you suggested, I can reproduce.  Is that the problem?  If so, which
> > is your preferred behavior to make diffs for encrypted data or decrypted
> > text?
> My preference is clearly on decrypted text (much easier on my eyes).
> The issue, as I understand it, is that data written to disk into files
> matching epa-file-name-regexp with write-region cannot just always be
> encrypted.
> It that data is coming from processes, like "cvs update ..." via
> vc-find-version then it is already/still encrypted.
> Perhaps I am missing some obvious point how to solve this problem.

I see there are two different issues.  The first is, vc-find-version
doesn't inhibit file-name-handlers when creating backup files, as you
mentioned above.  The second is, if you want to make diffs for decrypted
text, it has to be written into files since ediff calls the external
program to compute diffs.  Which may cause a security problem unless
Emacs warns about it.

Something different.  jka-compr seems to have the same issue on "*.gz"
files.  So... can this kind of problem be better solved by advices (or
hooks, if any) to ediff-revision?

Regards,
--
Daiki Ueno


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.