Bravo! Best use of decorated code I've heard for a long while.

Shouldn't be hard to implement in jios. The tricky part is keeping it
up-to-date, as Henry warns.

It would be good if all J platforms follow the same convention. I'd be
happy for jios to follow jQt.  How about italics? Both jQt and jios already
use italics in comments, and it would mix well with existing syntax
coloring -- though an italic dot doesn't look much different from a normal
dot. Off-the-cuff, I don't see that would matter a lot in practice.

Where would the definitive documentation reside? NuVoc, I suppose, in the *Use
These Combinations* sections. I don't want jios to need to trawl NuVoc
webpages at every launch. But a plain list of phrases kept as a literal
noun in ~addons/general would be quick and easy to download at app launch
time. Would such a list be too onerous for JE coders to maintain?

jios does not interrogate JE to determine how to color a sentence. It did
once – it doesn't now. I wouldn't like that to change. Henry uses the word
"evolving": I find that ominous. I'm trusting that a special combination
will be recognisable in principle by substring search of the sentence, or
at worst via a regex. Failing that, I hope the sky won't fall in if jios
fumbles the occasional special combination.

On Sun, 30 Jul 2023 at 23:45, Elijah Stone <elro...@elronnd.net> wrote:

> Detecting what's a fork and a hook requires information about name
> classes,
> which jqt may have, but which kakoune likely won't.  The problem exists in
> principal but less so in practice for special combinations.
>
> On Mon, 31 Jul 2023, 'Viktor Grigorov' via Programming wrote:
>
> > My twopence:
> > Worth confirming: did you mean syntax highlighting on wiki pages or for
> the various text editors? Can't speak for jQt IDE.The answer for both is
> 'yes', certainly for the simpler ones. Easier for the former, I reckon.
> Consider also: should special combinations receive one color, that of what
> they resolve to; or should they additionally be italicized, emboldened, or
> underlined?
> >
> > For my syntax highlighting code for kakoune, I'd considered indicating
> with straight and wavy underlines whether a verb train resolves to a hook
> or a fork. I'd decided against it to not add clutter.
> >
> >
> > Jul 30, 2023, 20:00 by akin...@gmail.com:
> >
> >> Hi all, I hope you are all well.
> >>
> >> Two questions.
> >>
> >> 1. Is there a way to include Special Combinations in Syntax
> Highlighting?
> >>
> >> Meaning some visual indicator that an arrangement of Operators triggers
> a
> >> Special Combination.
> >>
> >> 2. What page should I be looking up to understand the significance of
> >> Syntax Highlights.
> >> I am not sure what exactly that is called.
> >>
> >> For example:
> >> Something(...)          NB. Colour change to 'Something'
> >> Vs.
> >> Something   (...)       NB. No Colour changes to 'Something'
> >>
> >> Which page do I find that type of information?
> >>
> >>
> >> Thank you,
> >>
> >> AO.
> >> ----------------------------------------------------------------------
> >> For information about J forums see http://www.jsoftware.com/forums.htm
> >>
> >
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to