From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@altern.org>
Cc: Org Mode <emacs-orgmode@gnu.org>,
Marcelo de Moraes Serpa <celoserpa@gmail.com>
Subject: Re: Move to item to the bottom
Date: Sat, 02 Jul 2011 21:25:44 +0200 [thread overview]
Message-ID: <87wrg08oxz.fsf@gmail.com> (raw)
In-Reply-To: <87vcvmxs5h.fsf@gnu.org> (Bastien's message of "Fri, 01 Jul 2011 11:32:42 +0200")
Hello,
Bastien <bzg@altern.org> writes:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> It needs a better optimization (my excuse for
>> `org-list-delete-item'). I will work on it tonight.
>
> Thanks!
I've pushed a draft to:
git://github.com/ngz/org-mode-lists.git move-cycle
The branch is made of two patches. The first one implements the
all-mighty (but not-so useful) `org-list-send-item' function. Here is
its doc-string:
Send ITEM to destination DEST.
STRUCT is the list structure.
DEST can have various values.
If DEST is a buffer position, the function will assume it points
to another item in the same list as ITEM, and will move the
latter just before the former.
If DEST is `begin' (resp. `end'), ITEM will be moved at the
beginning (resp. end) of the list it belongs to.
If DEST is a string like "N", where N is an integer, ITEM will
be moved at the Nth position in the list.
If DEST is `kill-ring', ITEM will be deleted and its body will be
added to the kill-ring.
If DEST is nil, ITEM will be deleted.
This function returns, destructively, the new list structure.
The second one changes the behavior of `org-move-item-up' (and not
`org-move-item-down, for comparison). When the user tries to move the
first item of a list up, the function will ask him whether he wants to
roll it back to the end of the list, or not.
I'm not particularly convinced by that feature, but I implemented it
nonetheless for 2 reasons:
1. it doesn't add yet another key-binding;
2. it doesn't prevent macros to stop at the beginning of the list
(when using C-u 0 <F4>).
So, what do you all think about it?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2011-07-02 19:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 16:13 Move to item to the bottom Marcelo de Moraes Serpa
2011-06-30 18:55 ` Nicolas Goaziou
2011-07-01 6:35 ` Nicolas Goaziou
2011-07-01 8:57 ` Bastien
2011-07-01 9:10 ` Nicolas Goaziou
2011-07-01 9:32 ` Bastien
2011-07-02 19:25 ` Nicolas Goaziou [this message]
2011-07-03 2:02 ` Marcelo de Moraes Serpa
2011-07-03 9:39 ` Nicolas Goaziou
2011-07-05 3:27 ` Marcelo de Moraes Serpa
2011-07-07 15:51 ` Marcelo de Moraes Serpa
2011-07-20 16:05 ` Marcelo de Moraes Serpa
2011-07-27 11:22 ` Bastien
2011-07-27 23:12 ` Marcelo de Moraes Serpa
2011-07-01 9:34 ` Carsten Dominik
2011-07-01 9:46 ` Bastien
2011-07-01 10:25 ` Carsten Dominik
2011-07-01 16:07 ` Bastien
2011-07-01 16:59 ` Marcelo de Moraes Serpa
2011-07-01 19:25 ` Nicolas Goaziou
2011-07-01 22:58 ` Marcelo de Moraes Serpa
2011-07-02 8:05 ` Nicolas Goaziou
2011-07-02 9:06 ` Bastien
2011-07-01 10:14 ` Eric S Fraga
2011-07-01 10:27 ` Carsten Dominik
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrg08oxz.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@altern.org \
--cc=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).