On Mon, Jan 5, 2009 at 7:16 AM, Matthew Lundin wrote:
>
> When I include diary entries in the agenda, I get the following error
> while calling columns view in the agenda:
>
> org-entry-properties: Wrong type argument: stringp, nil
>
> When I turn off diary inclusion by typing "D",
I have a reply under the subject, "extensible syntax".
One possibility is this: if the syntax exists in a given language
(fairly unlikely), then you simply escape like this: \c = c for all c
(including \ itself).
--
For personal gain, myalgic encephalomyelitis denialists are knowingly
causing fu
>
> On Jan 4, 2009, at 3:33 PM, Steven E. Harris wrote:
> [...]
>> Without knowing what the enclosing `quote' form means, how do know
>> that
>> "((def))" is not part of it?
>
> Hi Steven,
>
> good question, and the answer is that is does not know,
> cannot know, because this is a feature that is
When I include diary entries in the agenda, I get the following error
while calling columns view in the agenda:
org-entry-properties: Wrong type argument: stringp, nil
When I turn off diary inclusion by typing "D", the problem goes away.
Certainly, it is trivial to turn off diary inclusion be
Hi Carsten,
After some additional testing of footnote options, I discovered
another minor quirk. It occurs when org-footnote-section is set to a
value such as "Footnotes" (the default value). When
org-footnote-action is called for the very first time in an org
buffer, the "Footnotes" headline is
Hi all,
For printing custom agenda commands, I like to set the local option
org-agenda-with-colors to nil.
This works fine for single agenda commands, such as
(setq org-agenda-custom-commands
'(("o" "Office" tags-todo "office"
((org-agenda-with-colors nil)
But I ca
On Sun, Jan 4, 2009 at 10:01 AM, Carsten Dominik wrote:
>
> On Jan 4, 2009, at 3:33 PM, Steven E. Harris wrote:
>
>> Carsten Dominik writes:
>>
>>> Code references use special labels embedded directly into the source
>>> code. Such labels look like "((name))" and must be unique within a
>>> docu
A general idea, which might or might not be useful.
There are occasionally questions about syntax, like this:
Also, I'm afraid definition matching regexp won't play
nicely with text indentation, ... -- Paul
Or this:
What would be safer? -- Carsten
I like the footnote implementation, so
Carsten Dominik writes:
> This idea is to make this work in a heuristic way, by using something
> that is unlikely enough to occur in real code.
And that is a tough problem, as code is usually defined as stuff that
contains all kinds of weird (and often paired) delimiters.
[...]
> What would b
Carsten> On Jan 4, 2009, at 3:33 PM, Steven E. Harris wrote:
>> > Carsten Dominik writes: >
>>> >> Code references use special labels embedded directly into the
source
>>> >> code. Such labels look like "((name))" and must be unique
within a
>>> >> document.
>> > > How doe
On Jan 4, 2009, at 3:33 PM, Steven E. Harris wrote:
Carsten Dominik writes:
Code references use special labels embedded directly into the source
code. Such labels look like "((name))" and must be unique within a
document.
How does the parser know that, say, "((def))" is not a valid
expr
Carsten Dominik writes:
> Code references use special labels embedded directly into the source
> code. Such labels look like "((name))" and must be unique within a
> document.
How does the parser know that, say, "((def))" is not a valid expression
in the surrounding Lisp forms? Is it important
I jumped into some elisp, and eventually I might get it, but while I think
I'm close, my vacation is over, and I'm going to call "uncle".
Here is some crummy code I started putting together to try to pause the
relative timer in org-timer.el. Can someone give me a nudge, and suggest
what's wrong?
On Jan 4, 2009, at 9:13 AM, Carsten Dominik wrote:
Hi,
I am releasing version 6.17 of Org-mode.
[...]
Line numbers and references in literal examples
[...]
Here is an example:
#+begin_src emacs-lisp -n -r
(defmacro org-unmodified (&re
Hi,
I am releasing version 6.17 of Org-mode.
Besides the footnote support discussed already extensively here,
this release also contains a new feature to make Org-mode
more usable for writing tutorials and similar documents with
code examples. Lines in code examples can now be numbered,
and you
15 matches
Mail list logo
