all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: paul@tilk.co, 19102@debbugs.gnu.org
Subject: bug#19102: 24.4; outline-move-subtree-up/down error at last and second-last subtree
Date: Thu, 20 Nov 2014 18:21:03 +0200	[thread overview]
Message-ID: <83vbm96dxs.fsf@gnu.org> (raw)
In-Reply-To: <87r3wytcaa.fsf@rosalinde.fritz.box>

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: Eli Zaretskii <eliz@gnu.org>,  19102@debbugs.gnu.org
> Date: Thu, 20 Nov 2014 11:08:13 +0100
> 
> outline-move-subtree-up/down works if there's an empty line after
> the last subtree, but if not, it puts the last two subtree headers
> on the same line.

Does it make sense to fix outline-move-subtree-up/down so that they
also work when there's no empty line after the last subtree?  That's
one thing that looks inelegant in your patch, and might also cause
some (minor) trouble: what if the user types C-g before this function
finishes?





  parent reply	other threads:[~2014-11-20 16:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19  8:29 bug#19102: 24.4; outline-move-subtree-up/down error at last and second-last subtree Paul Rankin
2014-11-19 13:17 ` Stephen Berman
2014-11-19 15:54   ` Eli Zaretskii
2014-11-19 17:09     ` Stephen Berman
2014-11-19 18:56       ` Eli Zaretskii
2014-11-19 20:14         ` Stephen Berman
2014-11-19 20:32           ` Eli Zaretskii
2014-11-19 22:07             ` Stephen Berman
2014-11-20  6:46               ` Paul Rankin
2014-11-20 10:08                 ` Stephen Berman
2014-11-20 13:26                   ` Paul Rankin
2014-11-20 16:21                   ` Eli Zaretskii [this message]
2014-11-21 10:32                     ` Stephen Berman
2014-11-21 10:42                       ` Eli Zaretskii
2014-11-21 17:31                         ` Stephen Berman
2014-11-21 19:56                           ` Eli Zaretskii
2014-11-21 20:04                             ` Stephen Berman
2014-11-22  3:49                             ` Paul Rankin
2014-11-22 16:32                           ` Stefan Monnier
2014-11-22 16:45                             ` Eli Zaretskii
2014-11-22 22:20                             ` Stephen Berman
2014-11-24  4:07                               ` Stefan Monnier
2014-11-25 21:58                                 ` Stephen Berman
2014-11-26  2:34                                   ` Paul Rankin
2014-11-26 13:38                                     ` Stephen Berman
2014-11-20  7:22               ` Paul Rankin
2014-11-20 10:09                 ` Stephen Berman
2014-11-20 13:43                   ` Paul Rankin
2014-11-21 10:33                     ` Stephen Berman
2014-11-26  2:43               ` Stefan Monnier
2014-11-26 13:38                 ` Stephen Berman
2014-11-26 15:54                   ` Stefan Monnier
2014-11-26 19:04                     ` Stephen Berman
2014-11-26 22:11                       ` Stefan Monnier
2014-11-26 22:25                         ` Stephen Berman
2014-11-27  2:18                           ` Stefan Monnier
2014-11-27 10:12                             ` Stephen Berman
2014-11-27 17:15                               ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83vbm96dxs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19102@debbugs.gnu.org \
    --cc=paul@tilk.co \
    --cc=stephen.berman@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.