From: Christian Moe <mail@christianmoe.com>
To: suleika@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Idea: insert "current sort order" property
Date: Wed, 12 Oct 2011 14:16:35 +0200 [thread overview]
Message-ID: <4E958523.60909@christianmoe.com> (raw)
In-Reply-To: <CAPQe_Uog=+rKqRtF_YgB3xAvWgfLau5vWFM4TvwdVwrxnd8VXg@mail.gmail.com>
Hi,
You can copy the code into a buffer and `evaluate' it, i.e. teach
Emacs the new function for this session. You evaluate an elisp
expression by placing point right after the last closing parenthesis
and pressing `C-x C-e'. When you do, the minibuffer should display the
name of the function.
After this, Emacs will only remember the function for the rest of the
session. If you like it and want it available the next time you start
Emacs, just copy it into your .emacs file (only the bit *between* the
#+BEGIN_SRC and #+END_SRC lines).
This is the basic drill for using little snippets of code that don't
merit a file of their own.
Since this is an interactive function, you can call it with `M-x'.
Place point in the appropriate parent entry in your music outline and
try `M-x cm/org-store-outline-order'.
Options:
- Since the code in this case is surrounded by a #+BEGIN_SRC block, if
you copy it into an Org buffer, you can also evaluate it simply by
`C-c C-c' with point anywhere on the code block.
- You can change the name and drop the `cm/' prefix if you like (I
just use it as a reminder this is my hack, not part of Org-mode).
Yours,
Christian
On 10/12/11 1:35 PM, Gez wrote:
> Thanks, Christian. Please forgive my ignorance but what should I do
> with the code? I've not done anything more advanced than
> org-customize before.
>
> Gez
>
> On 11 October 2011 20:46, Christian Moe <mail@christianmoe.com
> <mailto:mail@christianmoe.com>> wrote:
>
> Hi, Gez,
>
>
> On 10/7/11 5:02 PM, Gez wrote:
>
> What I'm imagining is a command executed on a headline to insert a
> property into each of its children "fixing" the current order;
> something like ":sorted:01", ":sorted:02" etc.
>
>
> I think this is a neat idea, and can see some uses for it for my
> own stuff. I've made a first pass below. Please test it and let me
> know how it works for you (and please *don't* test it on anything
> valuable without backing up first!).
>
> <snip>
>
>
> Code follows.
>
> Yours,
> Christian
>
> #+begin_src emacs-lisp
> (defun cm/org-store-outline-order (arg prop)
> "Store the outline of the subtree of the entry at point by
> setting the property PROP of each direct child entry to its
> current position in the tree. With prefix ARG, store the position
> of the whole subtree. The tree can be restored to the stored
> outline by sorting on the property with `C-c ^ r'. Note that this
> will only work properly on the order of each subtree; if headings
> are demoted, promoted, or moved into different subtrees, the
> result may or may not be nonsense, but it will be impossible to
> restore the original order by sorting."
> (interactive "P\nsProperty key (default OutlineIndex): ")
> (if (string= prop "") (setq prop "OutlineIndex"))
> (if (or (not (org-map-entries t (concat prop "={.}") 'tree))
> (y-or-n-p "Property exists; overwrite? "))
> (let* ((match (format "LEVEL%s%s"
> (if arg ">=" "=")
> (1+ (org-current-level))))
> (counter 1)
> (width (1+ (floor (log10 (length (org-map-entries t
> match 'tree))))))
> (fstr (concat "%0" (number-to-string width) "d")))
> (org-map-entries
> '(progn
> (org-set-property prop
> (format fstr counter))
> (setq counter (1+ counter)))
> match 'tree)
> (message ""))))
> #+end_src
>
>
next prev parent reply other threads:[~2011-10-12 12:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 15:02 Idea: insert "current sort order" property Gez
2011-10-11 19:46 ` Christian Moe
2011-10-12 11:35 ` Gez
2011-10-12 12:16 ` Christian Moe [this message]
2011-10-12 15:59 ` Gez
2011-10-12 19:51 ` Christian Moe
2011-10-13 11:40 ` Gez
2011-10-13 12:39 ` Christian Moe
2011-10-13 18:34 ` Gez
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=4E958523.60909@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=suleika@gmail.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).