On Wed, Feb 15, 2023 at 8:09 AM Thomas Passin <[email protected]> wrote:
> @ekr: "I suspect that adding a node @font rest fonts will suffice."
>
> I must be missing the magic way to do this
>
It looks like there is a bug somewhere. I expected the following to work:
1. Create a test node (headline doesn't matter, but mine is --- tests of
@language rest) containing:
@language rest
**Bold**
plain rest text.
*Italics*
2. Save your test file with the test node selected.
3. Restart your test file with --trace=coloring in effect.
On startup, the trace will show a large trace of the configDict, containing
many keys. The start of this trace will looks something like this:
configDict: {'blank': '#E5E5E5',
'comment': 'solarized-orange',
'comment.hashbang': '#408080',
...
Then you'll see the usual syntax coloring trace. Something like this:
mainLoop
NEW NODE: --- tests of @language rest
setTag: rest.leokeyword 0 14 '@language rest'
rest_main:
setTag: rest.keyword2 0 8 '**Bold**'
rest_main:match_at_language
setTag: rest.keyword4 0 9 '*Italics*'
rest_main:rest_rule14
Your task is to set these key/value pairs to your liking.
A. In myLeoSettings.leo, under the node Language-specific fonts and colors,
create an organizer node (with rest as the headline)
B. Under this rest organizer node, create other nodes to set specific
settings. Use the traces as your guide.
For example, I created the node: @color rest-keyword3-color = red
The body text doesn't matter: put any comments there you like.
*Bug: *settings don't affect the configDict. I'll investigate.
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/CAMF8tS35Gh%2B4RpK2Q-zZ4c41ZWtwRdm9bBChvKPoekkJdxkuOQ%40mail.gmail.com.
