From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#14786: 24.3.50; `field-end' is now very slow Date: Fri, 05 Jul 2013 21:33:49 +0300 Message-ID: <83zju0yhyq.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1373049310 9089 80.91.229.3 (5 Jul 2013 18:35:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 5 Jul 2013 18:35:10 +0000 (UTC) Cc: 14786@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jul 05 20:35:10 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1UvAqb-0008JF-MW for geb-bug-gnu-emacs@m.gmane.org; Fri, 05 Jul 2013 20:35:09 +0200 Original-Received: from localhost ([::1]:50169 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UvAqb-0005mB-8w for geb-bug-gnu-emacs@m.gmane.org; Fri, 05 Jul 2013 14:35:09 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UvAqW-0005k6-EJ for bug-gnu-emacs@gnu.org; Fri, 05 Jul 2013 14:35:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UvAqV-0006HS-4x for bug-gnu-emacs@gnu.org; Fri, 05 Jul 2013 14:35:04 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:38259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UvAqV-0006Gl-0S for bug-gnu-emacs@gnu.org; Fri, 05 Jul 2013 14:35:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1UvAqU-0001uE-Av for bug-gnu-emacs@gnu.org; Fri, 05 Jul 2013 14:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 05 Jul 2013 18:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14786 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 14786-submit@debbugs.gnu.org id=B14786.13730492647253 (code B ref 14786); Fri, 05 Jul 2013 18:35:02 +0000 Original-Received: (at 14786) by debbugs.gnu.org; 5 Jul 2013 18:34:24 +0000 Original-Received: from localhost ([127.0.0.1]:60808 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UvApr-0001ss-Qm for submit@debbugs.gnu.org; Fri, 05 Jul 2013 14:34:24 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:60205) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UvApo-0001sM-2R for 14786@debbugs.gnu.org; Fri, 05 Jul 2013 14:34:21 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MPH00I007JMYR00@a-mtaout20.012.net.il> for 14786@debbugs.gnu.org; Fri, 05 Jul 2013 21:33:52 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MPH00IQ57KGR180@a-mtaout20.012.net.il>; Fri, 05 Jul 2013 21:33:52 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:75958 Archived-At: > Date: Fri, 5 Jul 2013 10:06:41 -0700 (PDT) > From: Drew Adams > Cc: 14786@debbugs.gnu.org > > For my info: When such a code change is made, is there no log of the > reason behind the change? Every change comes with a change log. The reason is not always stated in the change log, it can sometimes be in the comments to the changed code or in some discussion that led to the change (preferably cited in the change log). > If it was to fix a bug, for instance, wouldn't that bug # be noted? Yes, definitely.