"Steven E. Harris" writes:
> Also, that one would tolerate anything but a closing parenthesis in a
> label;
That was a mistake to propose. I had forgotten that I intended the label
to run to the end of the line, not to a bounding parenthesis. So much
for writing code in haste without testing it
Hi Steven,
thank you for your thoughtful post and everyone else for chiming in with
useful suggestions.
I have just uploaded 6.17a which revamps the codeline references stuff,
in the following way:
1. The default label now looks like (ref:name)
2. The default format is defined in org-code
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
document.
How does the parser know that, say, "((def))"
Carsten,
2009/1/4 Carsten Dominik :
>
> <>like the other Org-mode targets? That would make sense.
> Does anyone know a language where this would be used
> in real life? It would make it harder to write about
> Org-mode, though.
Yes, Oracle pl/sql uses th
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
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
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
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
10 matches
Mail list logo
