From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: nljlistbox2@gmail.com (N. Jackson) Newsgroups: gmane.emacs.devel Subject: Please consider making Bug #23917 a blocker for 25.1 (was Re: org-capture: Capture template =?utf-8?B?4oCYZ+KAmTo=?= Match data clobbered by buffer modification hooks) Date: Sat, 16 Jul 2016 13:01:50 -0300 Message-ID: <87mvlhmv0x.fsf_-_@moondust.awandering> References: <87vb066ejv.fsf@linaro.org> <8360s67qcp.fsf@gnu.org> <87bn1yyaui.fsf@linaro.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1468685023 23035 80.91.229.3 (16 Jul 2016 16:03:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 16 Jul 2016 16:03:43 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 16 18:03:34 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 1bOS3u-0006u1-6V for ged-emacs-devel@m.gmane.org; Sat, 16 Jul 2016 18:03:30 +0200 Original-Received: from localhost ([::1]:38054 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOS3t-0007cQ-5h for ged-emacs-devel@m.gmane.org; Sat, 16 Jul 2016 12:03:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35533) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOS2a-0005ac-O2 for emacs-devel@gnu.org; Sat, 16 Jul 2016 12:02:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bOS2U-0002gt-Og for emacs-devel@gnu.org; Sat, 16 Jul 2016 12:02:07 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:34151) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOS2U-0002gm-Ht for emacs-devel@gnu.org; Sat, 16 Jul 2016 12:02:02 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1bOS2R-0005US-2U for emacs-devel@gnu.org; Sat, 16 Jul 2016 18:01:59 +0200 Original-Received: from 142.227.16.2 ([142.227.16.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Jul 2016 18:01:59 +0200 Original-Received: from nljlistbox2 by 142.227.16.2 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Jul 2016 18:01:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 142.227.16.2 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) Cancel-Lock: sha1:SFOd/HBDarqGSjG9qosPGRVJats= 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.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:205762 Archived-At: At 15:37 -0400 on Friday 2016-07-15, Noam Postavsky wrote: > On Fri, Jul 15, 2016 at 3:12 PM, Alex Bennée wrote: > > See Bug #23917 "commit 3a9d6296b35e5317c497674d5725eb52699bd3b8 > causing org-capture to error out" Please consider making this bug (Bug #23917 http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23917) a blocker for release of Emacs 25.1. I use Org capture dozens of times a day -- it is central to my workflows -- and this bug breaks all of my captures, even the very simplest ones. An Emacs with this bug is unusable for me. I don't think my pattern of using Org Mode is particularly unusual, at least among those who use it is as an organizer. [Those who use it for publication or for reproducible research or for literate programming may have different usage patterns.] So this bug potentially impacts a large number of Emacs users. It seems clear from the discussion in the bug report that a change in Emacs triggered the bug. (For me it was not present in the 25.0.95 pretest tarball with latest Org Mode, but is present in yesterday's Emacs 25 branch with latest Org Mode.) But apparently with the version of Org built in to Emacs the bug does not manifest. So it isn't clear if the bug is in Emacs or if the change in Emacs just uncovered a bug in Org Mode (or both). Either way, please can we wait until it's fixed before the release (which otherwise feels like it's going to happen in the next three to five weeks). Thanks. N.