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
Fixed on the trunk at rev 4720. I had forgotten I was responsible
I just pulled rev 4739 and I get now:
Unexpected docutils exception
Traceback (most recent call last):
File /home/dalcolmo/programs/leo-editor/leo/core/leoRst.py, line
1906, in writeToDocutils
settings_overrides=overrides)
On Mon, Oct 17, 2011 at 6:24 PM, Matt Wilkie map...@gmail.com wrote:
[...]
launchLeo\dist\launchLeo\launchLeo.exe --debug
*** isPython3: False
scanOptions: *** debug mode on
Traceback (most recent call last):
[...]
File
On Sat, Nov 5, 2011 at 6:14 AM, Josef joe...@gmx.net wrote:
Fixed on the trunk at rev 4720. I had forgotten I was responsible
I just pulled rev 4739 and I get now:
docutils.languages.get_language(doctree.settings.language_code,self.reporter)
TypeError: get_language() takes exactly 1
On Sat, Nov 5, 2011 at 6:07 AM, Josef joe...@gmx.net 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
On Nov 5, 7:09 pm, Edward K. Ream edream...@gmail.com wrote:
Just found another bit of grit: there is little or no machinery to
set up config settings in external unit tests.
On second thought, this really isn't such a big deal. It was always
obvious that today's unit test had to simulate
On Nov 5, 7:16 pm, Edward K. Ream edream...@gmail.com wrote:
On Nov 5, 7:09 pm, Edward K. Ream edream...@gmail.com wrote:
Just found another bit of grit: there is little or no machinery to
set up config settings in external unit tests.
It may be useful to create a method called
