That was my duh - I accidentally left a # in when copying to my
.emacs. It works fine now. Thank you.
Gez
On 13 October 2011 13:39, Christian Moe wrote:
> Hi,
>
> Not sure I can help; I don't quite see how this error could be caused by
> anything in the code I sent you. Is this happening on th
Hi,
Not sure I can help; I don't quite see how this error could be caused
by anything in the code I sent you. Is this happening on the same
system as you used before? What version of Emacs are you on when this
happens?
Yours,
Christian
On 10/13/11 1:40 PM, Gez wrote:
Thanks. I got it to
On 12 October 2011 20:51, Christian Moe wrote:
>
> Then we need a way to keep track of what property keys are used to store
> outlines in, so we can offer those and only those for completion. (We don't
> want to offer all the property keys used in the buffer -- that's an
> invitation to overwrite
On 10/12/11 5:59 PM, Gez wrote:
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?
Save often; backup/commit often; be ready to hit 'undo'...? Do the
first test run on
On 12 October 2011 13:16, Christian Moe 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. T
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
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 wrote:
> Hi, Gez,
>
>
> On 10/7/11 5:02 PM, Gez wrote:
>
>> What I'm imagining is a command executed o
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.
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. Ideally there would be a prompt for the
property key (or part of it) so that there could be more than one such
property
