From: James TD Smith <ahktenzero@mohorovi.cc>
To: emacs-orgmode@gnu.org
Subject: Re: RFC: Improvements to org-remember
Date: Sun, 30 Nov 2008 02:00:51 +0000 [thread overview]
Message-ID: <20081130020051.GG62148@yog-sothoth.mohorovi.cc> (raw)
In-Reply-To: <21E07097-0FF3-40E1-8BD8-A12B7D5099BC@alexanderonline.org>
Hi Ben,
On 2008-11-24 11:50:53(+0200), Ben Alexander wrote:
> On 2008-Nov-24, at 04:25, emacs-orgmode-request@gnu.org wrote:
> > ** Automatic sorting
> >
> Right now, I have a :SORT: property in my property drawer which looks
> like:
> :SORT: C-c S-6 p
> This is just a reminder to me for the key chord I need to play to get
> the sort I want. It's conveniently located near the headline and not
> too hard to open and read when I need to resort manually.
>
> It seems to me that having an hook like 'org-remember-after-filing
> would allow people to choose what kinds of updating they wanted done
> after a remember template was used. Mixing this with different types
> of templates may take some care: you don't want to run all the hooks
> inside a save-excursion if the point to to allow the hook to move
> point to a special place, but then all hooks would have to be written
> with that in mind. Perhaps the hooks should be run inside a (let )
> with some official bindings for markers for the following:
> - org-remember-marker-to-beginning-of-new-text
> - org-remember-marker-to-end-of-new-text
> - org-remember-marker-to-parent-headline (perhaps most useful for
> non-headline remember templates)
> - org-remember-template-type
This is basically how I was thinking of implementing the sort after filing (and
the other post-commit update functions).
> But automatic sorting seems useful in many other contexts (like after
> scheduling or rescheduling an item, or changing priority, or editing
> the headline text) so perhaps some wishes/ideas from the list would be
> appropriate. Could org-mode take ownership of the :SORT: property for
> headlines, and have a org-sort-file-using-property (or a org-sort-
> headline-using-property) which could be added to hook lists where-ever
> the user wanted?
I think it would be rather difficult to get automatic sorting working for
editing the headline text. Org doesn't have hook lists for priority or
scheduling changes either.
I do like the idea of defining a default sort for a tree. We would need
a :SORT_KEY: property as well, for sorting by property or table column, and a
#+SORT: facility for file level sorting. The property could be used to determine
a default sort for org-sort, with a new option added to select the default
(maybe C-c ^ RET).
> Or is this too specific? Would it be nice to have plain lists (or
> checkboxed lists) have some kind of sort property too? Where could a
> user store this data so it could be easy to see but also easy to ignore.
I'm not sure it's necessary to be able to do this in plain lists. If a plain
list item has enough activity under it to need sorting on a regular basis its
probably worth promoting it to a headline.
--
|-<James TD Smith>-<email/ahktenzero@mohorovi.cc>-|
prev parent reply other threads:[~2008-11-30 2:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 23:25 RFC: Improvements to org-remember James TD Smith
2008-11-24 0:23 ` Samuel Wales
2008-11-24 10:02 ` James TD Smith
2008-11-24 19:29 ` Samuel Wales
2008-11-24 21:11 ` Carsten Dominik
2008-11-24 21:41 ` Samuel Wales
2008-11-30 1:03 ` James TD Smith
2008-12-03 20:36 ` Samuel Wales
2008-11-24 3:05 ` Sebastian Rose
2008-11-24 3:09 ` Sebastian Rose
2008-11-24 8:58 ` Carsten Dominik
2008-11-24 16:57 ` Russell Adams
2008-11-25 11:46 ` James TD Smith
2008-11-25 19:27 ` Carsten Dominik
2008-11-30 2:32 ` James TD Smith
2008-12-03 6:42 ` Carsten Dominik
2008-12-12 14:48 ` Carsten Dominik
2008-11-24 9:50 ` Ben Alexander
2008-11-30 2:00 ` James TD Smith [this message]
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=20081130020051.GG62148@yog-sothoth.mohorovi.cc \
--to=ahktenzero@mohorovi.cc \
--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).