From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: adding subheadings
Date: Sun, 15 Jul 2007 20:07:44 +0100 [thread overview]
Message-ID: <20070715190744.GA10139@atlantic.linksys.moosehall> (raw)
Hi all,
First post so go easy on me ;-)
Would something like the following be of use to anyone other than me?
(Suggested key-bindings at the bottom of the code.)
--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------
(defun org-new-subheading ()
"Add a new heading, demoted from the current heading level."
(interactive)
(org-insert-heading)
(org-demote-subtree))
(defun org-new-subheading-todo (&optional arg)
"Add a new TODO item, demoted from the current heading level.
The TODO keyword for the new item can be specified by a numeric
prefix argument, as with `org-todo'.
Otherwise, if `org-subheading-todo-alist' is non-nil, it is used
to map the new keyword from the current one, and if it is nil,
the next TODO keyword in the sequence is used, or the first one
if the current heading does not have one.
This allows a TODO keyword hierarchy to be imposed, e.g.
if org-subheading-todo-alist is
'((\"MASTERPLAN\" . \"PROJECT\")
(\"PROJECT\" . \"NEXTACTION\")
(\"NEXTACTION\" . \"NEXTACTION\"))
then invoking this function four times would yield:
* MASTERPLAN
** PROJECT
*** NEXTACTION
**** NEXTACTION"
(interactive "P")
(save-excursion
(org-back-to-heading)
(looking-at org-todo-line-regexp))
(let* ((current-keyword (match-string 2))
(new-keyword
(if arg
(nth (1- (prefix-numeric-value arg))
org-todo-keywords-1)
(or
(and current-keyword
(or (car (assoc current-keyword org-subheading-todo-alist))
(cadr (member current-keyword org-todo-keywords-1))))
(car org-todo-keywords-1)))))
(org-new-subheading)
(insert new-keyword " ")))
(defcustom org-subheading-todo-alist nil
"An associative map to help define which TODO keyword should be
used for new subheadings, depending on the current heading's TODO
keyword. See the documentation for `org-new-subheading-todo' for
an example."
:group 'org-todo
:type '(alist :key-type (string :tag "Current heading keyword")
:value-type (string :tag "New sub-heading keyword")))
(org-defkey org-mode-map [(meta j)] 'org-new-subheading)
(org-defkey org-mode-map [(shift meta j)] 'org-new-subheading-todo)
--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------
I would have preferred to make the defcustom have a radio button list
of existing TODO keywords for the alist keys and values, rather than
freeform strings, but I couldn't figure out how to get it to refer to
to org-todo-keywords-1.
Finally, what's the preferred way to submit patches? Is there a
revision-controlled repository available anywhere?
Cheers,
Adam
next reply other threads:[~2007-07-15 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 19:07 Adam Spiers [this message]
2007-07-15 23:42 ` adding subheadings Adam Spiers
2007-07-17 20:58 ` Scott Jaderholm
2007-07-20 16:53 ` Adam Spiers
2007-08-12 6:31 ` 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=20070715190744.GA10139@atlantic.linksys.moosehall \
--to=orgmode@adamspiers.org \
--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).