Just realized there is a bug in the bookmarks for subtrees. So the 5-26 
link goes just to node 5 and the 4-23 links to node 4.

5-26 is supposed to go the = leo4sqlite script = / << docstring >>

You'll see that the version in the link below has the correct formatting.

4-23 points to the Sqlite3 node, under leo4sqlite local, which I edited to 
have the @language python directive + ''' in order to get LeoVue to 
recognize that it is a docstring.

Joe

On Saturday, March 3, 2018 at 2:48:40 PM UTC-5, Joe Orr wrote:
>
> I fixed the handling of docstrings (at least the multiline ones)
>
> I put a demo on the leo-examples repo:
>
> See https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/5-26/
>
> The latter page shows that the docstring is being properly formatted for 
> the web.
>
> To get this to work with your version, just update the CDN to 
> https://cdn.jsdelivr.net/npm/[email protected]
>
> Also, on this page:
> https://kaleguy.github.io/leo-examples/leo4sqlite/#/t/4-23/
> you need to add @language python + ''' on beginning and end of the page. 
>
> The demo file is also an example of making a general leo file and then 
> adding the coding leo file as a node:
>  https://kaleguy.github.io/leo-examples/leo4sqlite
>
> You can see that the first page is the repo README.
>
> -Joe
>
>
>
>
> On Wednesday, February 28, 2018 at 4:26:43 PM UTC-5, tscv11 wrote:
>>
>> The script 'leo4sqlite' is now online using leovue - the syntax 
>> highlighting works well.
>> I'm looking forward to trying some of leovue's more advanced capabilities.
>>
>> My leovue/leo4sqlite demo lives here: 
>> https://tscv11.github.io/leo4sqlite/#/t/23/
>>
>> tscv11
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to