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#19102: 24.4; outline-move-subtree-up/down error at last and second-last subtree Date: Wed, 19 Nov 2014 17:54:41 +0200 Message-ID: <83lhn789tq.fsf@gnu.org> References: <87lhn7s522.fsf@rosalinde.fritz.box> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1416412591 1222 80.91.229.3 (19 Nov 2014 15:56:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Nov 2014 15:56:31 +0000 (UTC) Cc: paul@tilk.co, 19102@debbugs.gnu.org To: Stephen Berman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 19 16:56:23 2014 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 1Xr7cF-0003pd-JS for geb-bug-gnu-emacs@m.gmane.org; Wed, 19 Nov 2014 16:56:23 +0100 Original-Received: from localhost ([::1]:59204 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7cE-0001rP-TR for geb-bug-gnu-emacs@m.gmane.org; Wed, 19 Nov 2014 10:56:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57523) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7b2-000087-DZ for bug-gnu-emacs@gnu.org; Wed, 19 Nov 2014 10:55:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr7aw-0005gY-HD for bug-gnu-emacs@gnu.org; Wed, 19 Nov 2014 10:55:08 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:41237) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7aw-0005gO-F6 for bug-gnu-emacs@gnu.org; Wed, 19 Nov 2014 10:55:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Xr7av-0008V5-MR for bug-gnu-emacs@gnu.org; Wed, 19 Nov 2014 10:55:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 19 Nov 2014 15:55:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 19102 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 19102-submit@debbugs.gnu.org id=B19102.141641249032653 (code B ref 19102); Wed, 19 Nov 2014 15:55:01 +0000 Original-Received: (at 19102) by debbugs.gnu.org; 19 Nov 2014 15:54:50 +0000 Original-Received: from localhost ([127.0.0.1]:38450 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Xr7ak-0008Ub-6D for submit@debbugs.gnu.org; Wed, 19 Nov 2014 10:54:50 -0500 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:47465) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Xr7ah-0008UQ-0j for 19102@debbugs.gnu.org; Wed, 19 Nov 2014 10:54:48 -0500 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NFA00600MCX3Y00@mtaout25.012.net.il> for 19102@debbugs.gnu.org; Wed, 19 Nov 2014 17:50:21 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NFA003ADMNXUK30@mtaout25.012.net.il>; Wed, 19 Nov 2014 17:50:21 +0200 (IST) In-reply-to: <87lhn7s522.fsf@rosalinde.fritz.box> 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:96242 > From: Stephen Berman > Date: Wed, 19 Nov 2014 14:17:25 +0100 > Cc: 19102@debbugs.gnu.org > > The following patch (against master) seems to fix this, though it could > probably be done more elegantly. Thanks. Can you explain why the problem happened in the first place? > + ;; Make sure we can move forward when needed (bug#19102). Please only mention the bug number in comments if the code or the rest of the comment text do not speak for themselves, and there are some subtle issues here that can only be understood by reading the bug discussion. Otherwise, the bug number will appear in the commit log, so no need to put it in the code.