From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: gpg encryption warning Date: Fri, 22 Apr 2016 15:10:30 +0200 Message-ID: <571A22C6.4010906@gmx.at> References: <87ega36vbj.fsf@yandex.com> <571788AF.6080809@gmx.at> <877ffsb92q.fsf@yandex.com> <57189A29.6060108@gmx.at> <878u053kij.fsf@yandex.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1461330670 11569 80.91.229.3 (22 Apr 2016 13:11:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 22 Apr 2016 13:11:10 +0000 (UTC) Cc: emacs-devel@gnu.org To: Colin Baxter Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 22 15:10:56 2016 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 1atarF-0004Rr-F6 for ged-emacs-devel@m.gmane.org; Fri, 22 Apr 2016 15:10:53 +0200 Original-Received: from localhost ([::1]:32940 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atarE-0001Rr-GT for ged-emacs-devel@m.gmane.org; Fri, 22 Apr 2016 09:10:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52480) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1atar3-0001Jw-JV for emacs-devel@gnu.org; Fri, 22 Apr 2016 09:10:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ataqz-00083c-JW for emacs-devel@gnu.org; Fri, 22 Apr 2016 09:10:41 -0400 Original-Received: from mout.gmx.net ([212.227.15.15]:62577) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ataqz-000830-A6 for emacs-devel@gnu.org; Fri, 22 Apr 2016 09:10:37 -0400 Original-Received: from [192.168.1.100] ([212.95.7.119]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Llm5o-1bSvbY1UbQ-00ZLmp; Fri, 22 Apr 2016 15:10:36 +0200 In-Reply-To: <878u053kij.fsf@yandex.com> X-Provags-ID: V03:K0:5U9Myqmmq8LIcwBVugV7UO0a7zGNERiHrDski0D4q6j1p0Q7hTe /BFFbq+f+lmXZKvugbjblQxNmjH0z3QIDb5kPBenfS/vuh13faTklt4Q34jVxaZ0XsXo/RJ 759WQcTFTELCznmrsDukEszFqtJcVtmtWDyxMrWrqoHSTVqb2t+vADTRkP1h3G/Dtt5L50v xQhc6vedlRik7RLXAal1g== X-UI-Out-Filterresults: notjunk:1;V01:K0:K0XsAQ7sH3s=:fphTDHtn7eJMzVboDllUhS XibkF+NUQ2mJjHnIqFa7ULuRa6eF/mLCMNoRWnkK3WWGxMgykdibstSF5OKiLBDJtwgjKgVrr VFF7XZfGkMbhDoe0zAQ5/472B9Ra7J+U0APkWuOPdASdOR7ejFUShdXUKsXPnlrXrftEbI+us 5PHINBd1xFknaqqAqBiq+Rn6htNzA2nwPpJKBvEP9i8nVFWCifBFudlsTDuuYl62F/sqTTetn DCjviwe9T8+xr+pzkZPmxBpYGqgmBwZl5FQ2SwBKxOGuxXeMGf2vcGQQm9qUeDIzdHgggRXT8 x7WUpFkknNS40KXvFIXLsmsx1jjR6oIUt71CA44LFpWJ27mjBtRbRpZsNfwCCV8noIx6vQehz E1AwGkiFcFq2oJdvUCeXg4B9zpdN4aSGEz0rOSNCxGNR3jit5x57ekAqGIeRThLKsv1YvOu8P 5BSQShdjkLOW+TCzvg2DiMytNdVfcgZZ13TzJWeEwjUXIRnBxeV2zmILM+gUDK93x/pITRbrV nXtT9ACo1Ud4pSsbEguKqsyLeI/Z0LtBRlUUWAJqr8vBUCFL30O7+aE/tIBhz9SBdPOcqBFHf kSMPWf0aRfZOqFgs0sEOTHKBPwNe4vEC3lejlaoOE2DmRllCw11GSWbfjKZNl2hNnLGC7P01z 4++v/qByKLZCOG29Q31jc+GbEdkVNhRoyNlDEhTpxePq33FJOB/qg5P1/ta+YEdaU6i8PMu/e Dcbs4W0QqxUtJM28oDyDDLVRHFOi4EpAoLpfB0Dja5JcwCtWfiqsXGTcP7lyNcDvjssoANwC X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.15.15 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:203172 Archived-At: > If it helps, I can confirm that I get no error message is I edit and > then save (encrypt) When you do that (I hardly ever encrypt) do you have to re-enter the password? > a gpg file that's in an un-encrypted buffer. The > issue seems to be only with first-time encryption. > > Emacs bisection is new to me and I'd have to be "talked through it"; you may, > understandably, not want to entrust a newbe with that job. It's a trivial job, all you need is a fairly fast machine (one that does a reasonable complex "make" of emacs in less than 10 minutes, preferably muss less. In the directory where you git pull emacs you'd simply have to do git bisect start git bisect bad git bisect good ... where ... stands for the hash of the version that works (probably 24.5.1). Then "make" emacs as you usually do and if the result is good mark it as good via git bisect good and if it's bad as git bisect bad One description of git bisect is this https://git-scm.com/docs/git-bisect but there might be better ones. One caveat: Often a specific commit breaks building emacs and then you have to skip this commit and usually go back until you find one that builds. I don't bisect more often than once in a month because on my machine it usually takes me half a day to finish. martin, who doesn't want to talk you into it ;-)