From: Gez <suleika@gmail.com>
To: mail@christianmoe.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Idea: insert "current sort order" property
Date: Wed, 12 Oct 2011 16:59:35 +0100 [thread overview]
Message-ID: <CAPQe_UpwfwDpcWtmngVmXw1vMA9dQJm665i0f+Y5u6qZDTiB+g@mail.gmail.com> (raw)
In-Reply-To: <4E958523.60909@christianmoe.com>
On 12 October 2011 13:16, Christian Moe <mail@christianmoe.com> wrote:
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).
It's in my .emacs now - I have just tested it and it seems to work
perfectly. Thank you so much for it. And thanks for explaining what
to do with code snippets.
I do use revisioning, but Is there a protocol I should use for testing
code snippets before using them on my original data or can they be
considered safe after being run once?
One thing that might be useful to add to the code please ... If when
prompting for the property key, TAB brought up the list of
auto-complete keys (like when using C-c C-x p) that would make for
easier maintenance and consistency; e.g. when I deliberately want to
overwrite a previous outline index it would avoid a second set of
properties being written accidentally if I made a typo.
Gez
> 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
>
next prev parent reply other threads:[~2011-10-12 16:00 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
2011-10-12 15:59 ` Gez [this message]
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=CAPQe_UpwfwDpcWtmngVmXw1vMA9dQJm665i0f+Y5u6qZDTiB+g@mail.gmail.com \
--to=suleika@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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).