VS Code & related editor syntax highlighting extension for slim/eidos

[Christopher McAllester]

Hi Ben, All,

I wrote a syntax highlighter extension for VS Code a couple years ago and recently extended it to do some basic code snippet completion and highlighting. I don't think there's an alternative available online yet, and wanted to share and get some input: https://github.com/csmcal/slim-eidos-vsc-extension

1) Publishing it on VS Code Marketplace, which makes it downloadable (free, under GPL) from any VS Code instance. Would this be alright? It requires registering a 'publisher' name and I wondered if you (Ben) wanted to do that instead.

2) A check that the keywords/etc specified within syntaxes/eidos.tmLanguage.json are correct and comprehensive. Anything missing?

3) If there's any interest in adding more code snippets or built in functions, feel free to clone and pull request.

Thanks!

Chris 

[Andrew Kern]

Hey Chris-

Wow, some synchronicity here-- I just pushed a similar package, but haven't yet released it to the VS Code Marketplace!

My extension is here: https://github.com/andrewkern/slim-vscode-tools

Looking over what you've done, it seems like you have many more snippets in yours, and I've concentrated on getting the documentation in, offering it on hover over, autocompletion, syntax checking, etc... Also I've gotten an Status bar / Activity bar command that offers the user the ability to run the script and am hoping to offer real-time linting... At any rate there seems like there is a lot of complementarity to what we've each done so far. 

Maybe we should join forces and develop one extension for the community to use? How would you feel about that? 

cheers!
Andy 

[Christopher McAllester]

Hey Andy,

Sure, happy to join forces, I just wanted it public as I had started sharing it within the lab/department recently. The timing is a little spooky :P

One thing I would note looking at your repo, VS Marketplace won't accept .svg files generally, if the .svg is going to be used in the .vsix.

How do you propose collaborating? I was going to suggest Ben host a repo if he was interested in maintaining it communally, but I'm open to ideas.

Best,

Chris

[Christopher McAllester]

I definitely prefer your formatting within hover text

[Andrew Kern]

oops didn't send this to all:

Ben, what do you think of hosting a repo?

Chris, one way to go might be to merge the stuff we like about them into a new extension? For instance, I really like all the snippets you have in, but prefer the doc structure I've put together (although it probably could use a refactor down the line to deal with the object orientation of SLiM). I haven't spent enough time looking at your code and will try to over the weekend. 

As for the .svg and the market place-- the svg file I have in there is for the Activity Bar icon-- I thought that's what they want us to use for that? e.g., https://github.com/microsoft/vscode-icons

cheers,
Andy 

--
SLiM forward genetic simulation: http://messerlab.org/slim/
---
You received this message because you are subscribed to the Google Groups "slim-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to slim-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/slim-discuss/7eb6c273-de2b-420c-9831-305ddf8662den%40googlegroups.com.

[Ben Haller]

Hi folks!  Sorry I've been offline for a while in this discussion!  Friends visiting from out of town, plus my car needed four new tires in a sudden emergency, so it has been a busy time.  :->

It's awesome what you two have put together, and great that it sounds like you'll try to fuse your work together into an even more awesome tool.  :->  I don't think I ought to host the repo.  I don't think I'd add any value to the project; I'm not a VS Code user, and I've got no real understanding of the details of what you've done, etc.  I'd just get in the way; it doesn't make sense for this to be under my umbrella, I don't think.  :->  But I'll be happy to give this project some publicity in the SLiM manual's section 1.10 (online resources for SLiM users), and that sort of thing.

I'd suggest taking the discussion off-list at this point; this list has a lot of subscribers :->.  You can use the GitHub issue (https://github.com/MesserLab/SLiM/issues/424) for discussion for now, perhaps?  Anybody else who is interested in this thread should subscribe to notifications for that issue.  Once you guys have a repo, you can put issues and discussions there.  Does that sound good?  (If you see a real value in me hosting the repo, I suppose I'm not opposed, I just don't see any utility to it.)  When the work gets to the point where it makes sense to close issue #424, go for it; this is in your hands now!  :->

(And thank you for contributing this to the community, it makes me really happy to see this kind of thing going on!  Please let me know if you need anything from me.)

Cheers,
-B.

Benjamin C. Haller
Messer Lab
Cornell University


Andrew Kern wrote on 3/14/25 7:50 PM:

To view this discussion visit https://groups.google.com/d/msgid/slim-discuss/CAGpG5go8sSEFTH3K1HN-R_agR3023e7uxfqiPLKbRqz8QEaoww%40mail.gmail.com.