>
> I did a major change to a file under an @clean node (it was almost empty
> and I copied medium size file over it externally), Leo asked to reload, but
> the content did not change until I forced Leo to re-read from disk. I have
> never seen this behaviour before.
>
Sounds similar to
>
> Leo directives are not always being colored any more (@others, @language
>> makefile)
>>
>
> I'll need more details. Everything seems to work for me.
>
In nodes under @language latex @others does not always seem to be colored,
using pygments.
I won't be able to do any tests until after
On Tue, Mar 26, 2019 at 11:06 AM Josef wrote:
> Great work Edward!
>
Glad you like it.
Leo directives are not always being colored any more (@others, @language
> makefile)
>
I'll need more details. Everything seems to work for me.
Rev 8555f9e0 colors only known languages in @language
Great work Edward!
the latex coloring is now much better!
I have seen some inconsistencies, though:
Leo directives are not always being colored any more (@others, @language
makefile)
Btw. when importing a "Makefile" leo places @language unknown_language,
instead of @language makefile - but
On Mon, Mar 25, 2019 at 12:41 PM Edward K. Ream wrote:
- Previously, I wondered whether it would be possible to add Leonine
> coloring rules to *all* standard pygments lexers. Here's how, modulo
> error handling:
>
> def patch_lexer(self, language, lexer):
>
> class
On Monday, March 25, 2019 at 7:18:27 AM UTC-5, john lunzer wrote:
Thank you for this. Sorry that it was kind of a let down beyond
> colorization for more languages.
>
As I said, I'm glad I did this project:
- Technically, it was a big step forward, and it turned out to be
surprisingly
On Mon, Mar 25, 2019 at 8:37 AM lewis wrote:
> Yes, that's fixed.
>
Thanks for the confirmation.
Edward
--
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
Yes, that's fixed.
Thanks
Lewis
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to
On Monday, March 25, 2019 at 8:09:25 AM UTC-5, lewis wrote:
>
> Leo launches but if I copy text ctrl-c and then ctrl-v it crashes
> immediately.
>
Fixed at rev 884082b2 in devel.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To
On Monday, March 25, 2019 at 8:09:25 AM UTC-5, lewis wrote:
Leo launches but if I copy text ctrl-c and then ctrl-v it crashes
> immediately.
>
>
>
>
>
>
> *Leo Log WindowLeo 5.8.1-b2 devel, build 20190227233831, Wed Feb 27
> 23:38:31 PST 2019Git repo info: branch = devel, commit =
And here is the console log with leo running. I haven't done ctrl-v yet.
*N:\git\leo-editor>launchleo.pyEmpty setting name in Falseset parent
@settingsextractExecutableString rest restextractExecutableString rest
pythonextractExecutableString rest restextractExecutableString
Here is full leo log:
Leo Log Window
Leo 5.8.1-b2 devel, build 20190227233831, Wed Feb 27 23:38:31 PST 2019
Git repo info: branch = devel, commit = 95ef89bc33b6
Python 3.7.2, PyQt version 5.12.2
Windows 10 AMD64 (build 10.0.17134) SP0
isPython3: True
current dir: N:/git/leo-editor
load dir:
In myLeoSettings file I have
*@bool use-pygments = True*
--
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 leo-editor+unsubscr...@googlegroups.com.
To post to this
On Mon, Mar 25, 2019 at 8:09 AM lewis wrote:
> Leo launches but if I copy text ctrl-c and then ctrl-v it crashes
> immediately.
>
Works for me on a similar system, regardless of @bool use-pygments.
Please run Leo from a console and report the full log and console.
Edward
--
You received this
Leo launches but if I copy text ctrl-c and then ctrl-v it crashes
immediately.
*Leo Log WindowLeo 5.8.1-b2 devel, build 20190227233831, Wed Feb 27
23:38:31 PST 2019Git repo info: branch = devel, commit = 95ef89bc33b6Python
3.7.2, PyQt version 5.12.2Windows 10 AMD64 (build 10.0.17134)
Thank you for this. Sorry that it was kind of a let down beyond
colorization for more languages.
On Monday, March 25, 2019 at 7:13:29 AM UTC-4, Edward K. Ream wrote:
>
> I plan no further work on this project. Please report any problems
> immediately.
>
> *Summary of this project*
>
> This
I plan no further work on this project. Please report any problems
immediately.
*Summary of this project*
This project is technically useful and interesting. I'm glad I did it.
Using pygments (*@bool use-pygments = True*) makes syntax coloring
available for many more languages.
Bypassing
On Monday, March 25, 2019 at 6:13:29 AM UTC-5, Edward K. Ream wrote:
> I plan no further work on this project.
I should add that by default everything should work *exactly* as before.
If not, please report a bug.
*- *@bool use-pygments is False in leoSettings.leo.
- All old @color settings
18 matches
Mail list logo
