rev bcf0f36, Leo build: 20140924100720, fixes the viewrendered plugin,
destroyed by a so-called "little fix" at rev 62984f9.
So the culprit was not docutils, but viewrendered. It's possible that the
viewrendered2.py plugin needs fixing, but I have no more time today.
Here is the checkin log fo
On Wed, 24 Sep 2014 07:46:34 -0700 (PDT)
Todd Mars wrote:
> Hello! How do I do this?
>
> global to an outline:
> Find text (with multiple results)
> Display next/previous results (go to location in the outline for each
> search found)
The Nav pane sounds like the best match, particularly if b
Hello! How do I do this?
global to an outline:
Find text (with multiple results)
Display next/previous results (go to location in the outline for each
search found)
Thanks,
Todd.
P.S. Good luck to Edward on the vacation!!
--
You received this message because you are subscribed to the Google
Am Mittwoch, 1. April 2009 19:36:25 UTC+2 schrieb Edward K. Ream:
>
> On Fri, Mar 27, 2009 at 9:22 PM, Largo84 >
> wrote:
>
>>
>> I use Leo to help me with multi-output document creation using the
>> rst3 plugin to create TEX and HTM files. I also would like an output
>> to be something a word p
On Tue, Sep 23, 2014 at 4:55 PM, lewis wrote:
> Even if [docutils] is loaded (but not reported) it doesn't appear to working
> when
> rendering rst nodes; the rendering pane appears blank.
Ah. At last I understand you. The viewrendered plugin does not seem
to be working for @rst nodes.
I've
On Tuesday, September 23, 2014 10:59:39 AM UTC-5, Edward K. Ream wrote:
>
>
> One concession: all the tests of @auto-rst are skipped when running
> externally. These are fantastically complex tests of way-too-complex code
> that alters the outline. I'm not thrilled with disabling these tests, b
