Regarding keeping editor and tooling info on the front-page up-to-date about janet-lang.org HOT 15 OPEN

There is definitely some work to do here, and really I need to go an do some maintenance on the website to update that info. I personally maintain and use only some of the tooling, so it needs to be up to other people to let me know of tooling that they use and its quality.

As for the trial kits, we should update that.

from janet-lang.org.

Thanks for the feedback.

I'll work on gathering a list of bits that might be relevant. Perhaps it can be used as a source for one or more updates.

from janet-lang.org.

I've made an initial summary here.

I'll ask around a bit to see if other useful things turn up.

from janet-lang.org.

I gave the current situation a bit more thought.

If only listing editors, there are some that it would be easy to just have a link for, e.g.

• CudaText (link to issue in janet's repository)
• Helix (link to helix's repo or home page)
• TIC-80 (contains an editor; just link to TIC-80's repo)
• Sublime Text (link to sublime-janet)
• Vim (link to janet.vim)

Not so clear are the remaining:

• Emacs
• Kakoune
• Neovim
• VSCode

Kakoune [1] and VSCode each have a couple of efforts, so the single link approach may not be appropriate. I suppose since it's just two links each, may be that's ok.

However, Emacs and Neovim have a variety of pieces that probably make sense for people to be aware of -- I suppose if the trial kits were linked to, I could try to provide info about the various components of interest at the trial kit repositories...

[1] I'm not sure if both Kakoune efforts are currently recommended. I'm waiting on a response about this.

from janet-lang.org.

To be honest, I'm not sure. I will make sure this week, and let you know

from janet-lang.org.

Your findings are correct. It is filetype detection, syntax highlighting and indentation.

from janet-lang.org.

Thanks a lot for the clarification.

from janet-lang.org.

Ok, may be I'll work on a draft PR that tries to incorporate some of the above.

from janet-lang.org.

It may be obvious, but FWIW, #225 is a draft PR for this issue.

from janet-lang.org.

I am on pause with Kakoune. But I think it is still relevant.

from janet-lang.org.

@pepe Thanks for the follow-up -- so do you think both JaKoune and janet.kak should be listed?

from janet-lang.org.

However, Emacs and Neovim have a variety of pieces that probably make sense for people to be aware of -- I suppose if the trial kits were linked to, I could try to provide info about the various components of interest at the trial kit repositories...

I've adapted this idea a bit so that in the top section of the janet-neovim-trial-kit README, there is this:

Or...learn about existing Neovim plugins with Janet features by reading some docs.

The link should take one to a page that describes some Janet-related plugins for Neovim. Perhaps this is a good compromise.

I plan to do something similar for janet-emacs-trial-kit.

from janet-lang.org.

I've expanded the purposes of the two trial kits to also provide some guidance [1] about what plugins / packages exist for the two respective editors. If the trial kits are linked to from janet-lang.org, then followers of such links should end with some relevant hints.

A bit indirect perhaps...

One idea about what to do for Kakoune and VSCode is to link to this page and this page, repsectively.

If that's palatable, possibly a similar thing could be done for Emacs and Neovim...since they both have pages (Emacs, Neovim) similar to those for Kakoune and VSCode.

[1] Actually, I cheated by linking to certain parts of janet-editor-and-tooling-info :P

from janet-lang.org.

After some thinking, I would say that neither janet.kak nor JaKoune should be part of the documentation. First is superseded by the kakoune default janet.kak, and second, I will sunset soon.

from janet-lang.org.

Thanks for looking into the situation.

So to summarize then, in Kakoune's case, we can just say that there is functionality built into the editor itself?

Ah also, do you know what functionality the default janet.kak provides? I found this file but I'm not quite sure what I'm looking at (^^;

I think I'm seeing some syntax highlighting along with some indentation may be?

from janet-lang.org.