You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be little reason to use these escape sequences directly, as for a terminal "foo", %i is implicitly %cfoo%r, i.e. coloring is handled automatically.
Preliminaries
One situation in which it can be useful though is to give some color to otherwise uncolored non-terminals.
In cases (1) and (2) bar baz should be purple, and in (3) it should be white.
Possible solutions
Remove the special meaning of these escape sequences. This either requires dropping them from KORE as well, or some extra processing in ModuleToKore (basically replace %{c,r} by {c,r}).
Come up with a more modular semantics for coloring.
The text was updated successfully, but these errors were encountered:
There seems to be little reason to use these escape sequences directly, as for a terminal
"foo"
,%i
is implicitly%cfoo%r
, i.e. coloring is handled automatically.Preliminaries
One situation in which it can be useful though is to give some color to otherwise uncolored non-terminals.
Here, a reasonable, modular behavior would be to either
Bar
to purple, orBar
to purple, orThe problem
However, in the above example
produces
In cases (1) and (2)
bar baz
should be purple, and in (3) it should be white.Possible solutions
ModuleToKore
(basically replace%{c,r}
by{c,r}
).The text was updated successfully, but these errors were encountered: