From: Bastien <bzg@altern.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Jeff Horn <jrhorn424@gmail.com>,
Org-mode ml <emacs-orgmode@gnu.org>,
nicholas.dokos@hp.com
Subject: Re: Refiling list items
Date: Wed, 17 Aug 2011 11:32:19 +0200 [thread overview]
Message-ID: <87ty9gfknw.fsf@gnu.org> (raw)
In-Reply-To: <87aabhlgy8.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 10 Aug 2011 12:05:35 +0200")
Hi Jeff,
thanks for bringing up this issue, and thanks all for the input.
I pushed three small changes to the org-refile interface:
1. before prompting the user for a refile target, put the point at the
beginning of the region/subtree to refile. This will make sure
everyone understands we are refiling headlines, not text.
2. Improve the prompt itself, explicitely saying whether we are refiling
a subtree or a region (containing subtree(s)).
3. Add a new option `org-refile-active-region-within-subtree' which,
when turned on, allows the user to refile the active region, turning
the first line into a headline using `org-toggle-heading'.
I think these are improvements going in the right direction -- let me
know what you think. On the overall, I'm with Nicolas in thinking that
we need to be extra careful when we try to extend a functionality to
heterogeneous elements.
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> My point is that outside of its list, an item is just plain text.
Yes!
« Outside of the hive, a bee is just a fly. » (René Descartes)
:)
> Thus, why not take that into account? Instead of creating a magical
> function to refile items anywhere, let's just extend `org-refile' to
> work on a region of text which is not a sub-tree.
This is what I tried to achieve with the new option.
> At the moment, org-refile understands the concept of region, but checks
> if that region holds a sub-tree. What about removing that check, and
> adapt the code to text without trees? It will then be the user's problem
> if he wants to match apples and oranges. Furthermore, as a side effect,
> refiling an item would simply mean selecting it and using refile
> interface.
Thanks for this idea!
Best,
--
Bastien
next prev parent reply other threads:[~2011-08-17 9:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 18:54 Refiling list items Jeff Horn
2011-08-08 4:09 ` Jeff Horn
2011-08-08 9:48 ` Nicolas Goaziou
2011-08-08 22:35 ` Jeff Horn
2011-08-08 23:03 ` Nicolas Goaziou
2011-08-08 23:47 ` Jeff Horn
2011-08-09 0:02 ` Nick Dokos
2011-08-09 2:31 ` suvayu ali
2011-08-09 0:20 ` Nick Dokos
2011-08-09 0:40 ` Jeff Horn
2011-08-09 0:45 ` Jeff Horn
2011-08-10 10:05 ` Nicolas Goaziou
2011-08-10 15:16 ` Jeff Horn
2011-08-17 9:32 ` Bastien [this message]
2011-08-22 16:12 ` Jeff Horn
2012-01-18 4:56 ` Jeff Horn
2013-06-28 21:09 ` Samuel Wales
2013-06-30 23:16 ` Bastien
2013-07-01 21:35 ` Samuel Wales
2013-07-02 7:32 ` Bastien
2011-08-09 1:07 ` Florian Beck
2011-08-08 16:12 ` Florian Beck
2011-08-08 17:05 ` Nicolas Goaziou
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=87ty9gfknw.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jrhorn424@gmail.com \
--cc=n.goaziou@gmail.com \
--cc=nicholas.dokos@hp.com \
/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).