From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: bad epg.el+GPG2 behavior: unavoidable passphrase pinentry prompt Date: Mon, 07 Oct 2013 14:15:30 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87iox90wxp.fsf@flea.lifelogs.com> References: <878uyg0yp1.fsf@flea.lifelogs.com> <878uyfzf1w.fsf@flea.lifelogs.com> <87bo389lw0.fsf-ueno@gnu.org> <87y56cufkt.fsf@flea.lifelogs.com> <87y56b96uk.fsf-ueno@gnu.org> <87haczvlmr.fsf@flea.lifelogs.com> <87bo36tpyt.fsf@flea.lifelogs.com> <87k3hssq5m.fsf@flea.lifelogs.com> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1381169749 16315 80.91.229.3 (7 Oct 2013 18:15:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Oct 2013 18:15:49 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 07 20:15:52 2013 Return-path: Envelope-to: ged-emacs-devel@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 1VTFLS-000694-N6 for ged-emacs-devel@m.gmane.org; Mon, 07 Oct 2013 20:15:50 +0200 Original-Received: from localhost ([::1]:32877 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTFLS-00060a-0g for ged-emacs-devel@m.gmane.org; Mon, 07 Oct 2013 14:15:50 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60029) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTFLK-00060L-An for emacs-devel@gnu.org; Mon, 07 Oct 2013 14:15:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VTFL9-0003ok-FM for emacs-devel@gnu.org; Mon, 07 Oct 2013 14:15:41 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:56065) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTFL9-0003oV-6S for emacs-devel@gnu.org; Mon, 07 Oct 2013 14:15:31 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VTFL8-00062X-7G for emacs-devel@gnu.org; Mon, 07 Oct 2013 20:15:30 +0200 Original-Received: from c-98-229-61-72.hsd1.ma.comcast.net ([98.229.61.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Oct 2013 20:15:30 +0200 Original-Received: from tzz by c-98-229-61-72.hsd1.ma.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Oct 2013 20:15:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 27 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-229-61-72.hsd1.ma.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:eqEIV/1pzKn63h2GSMRA+BmiCK4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:163960 Archived-At: On Sat, 05 Oct 2013 12:21:35 -0400 Stefan Monnier wrote: >> I don't think it's worthwhile after this discussion. SM> I think it is. This whole discussion has been completely muddled SM> because it mixes up details of gpg behaviors with everything else, SM> whereas the only thing that really matters is the behavior of Emacs SM> (which depends on many more things than just gpg) and the problem there SM> is still unclear. >> I'll work around it and see if I can make the workaround >> generally available. SM> Maybe that's the best we can do, but noone will know until you report SM> this bug with a clear description of the undesirable behavior, so that SM> people can assess really what is the core of the problem and se how we SM> can fix it (since it surely can be fixed in many different ways at SM> different levels). I reported two bugs about the two different issues (the unavoidable popups and `epa-file-cache-passphrase-for-symmetric-encryption'). I did not elaborate on how unpleasant VCS interactions are because they are just the latter bug over and over. I am not able to develop a workaround as I hoped since my work in the direction of implementing OpenPGP has been rejected. Ted