On Mon, Nov 14, 2011 at 11:49 AM, Josef wrote:
> Well, unfortunately the comment delimiters are the problem. When
> trying to embed SQL or Lua in Python strings, this means the resulting
> strings contain comments starting with "#", which is not recognized as
> a valid comment delimiter in either
> In fact, this *must* be so: Leo's read and write logic are completely
> independent of language, except for comment delimiters. In
> particular, they knows absolutely *nothing* about strings. Thus,
> @others and section references are valid *everywhere*, even in
> comments and strings.
Well,
On Sat, Nov 5, 2011 at 6:07 AM, Josef wrote:
> So I misinterpreted the lack of colorizing in strings as not
> recognizing of the directives.
> Sorry for not testing this before posting.
No problem. It's an interesting idea, and the ability to colorize
inside Python docstrings would be useful. So
So I misinterpreted the lack of colorizing in strings as not
recognizing of the directives.
Sorry for not testing this before posting.
- Josef
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googleg
On Fri, Nov 4, 2011 at 11:31 AM, Josef wrote:
> So, I am looking for a way to enable all the usual Leo goodies inside
> Python strings.
Certainly the colorizer could be expanded to handle this, at least for
Python strings. It involves creating a so-called delegate colorizer.
Already on the to-d
