commands VS portacle

It's CodeMirror! All I had to do was write a Janet grammar for it -- very easy to do. CodeMirror is pretty amazing -- I was able to implement the "edit values with your mouse" by just asking CodeMirror for the syntax node under the cursor, checking if it parsed as a number, and if so replacing it with a different string.

https://codemirror.net/

https://github.com/ianthehenry/codemirror-lang-janet

I went with CodeMirror after reading this post that compares a few different editor components: https://blog.replit.com/codemirror and I've been super happy with it.

The wrighter editor is built on top of codemirror and bytemd. codemirror is the go-to choice when it comes to flexible/hackable text editing and bytemd provides a nice wrapper for codemirror using react with some extra functionalities. I wanted to create a fork of bytemd that includes all the WYSIWYM features that I built for wrighter, but it was out of scope and takes too much time.

I will just use technology I am familiar with. Tauri + CodeMirror + CM's Common Lisp mode should hopefully get me a long way.

And the second video is an example of me converting some messy vanilla JavaScript code for initializing and accessing multiple CodeMirror code editors to clean, encapsulated, well-organized web component code. (Still vanilla!)

You can check out the CodeMirror library - https://codemirror.net/ It seems to be great match for this case.

Try it out in your editor and it should work a dream. For all of the possible commands, you can add check out the command repo's README.

I agree that it's a hurdle.

Portacle, https://portacle.github.io/ , is a way around config and whatnot, lowering the threshold a little.

Reminder that Portacle is a way to try Common Lisp (and its tooling!) in a portable, self-contained way, on all platforms.

https://portacle.github.io/

Thanks for your work! I can definitely see how your project improve CL's accessibility. Not sure if you're aware of the Portacle project, but I think there is an opportunity merging two projects together.

Also it is not much of a kit either since the user is left to install all the tools on their own. User who wants an easy to start kit with Emacs baked in is much better using Portacle or clean Emacs, or some of more polished Emacs distributions like Doom or Prelude together with Roswell for the "kit" part.

Then there's Portacle, a portable Emacs with SBCL, Quicklisp and Emacs goodies (magit, file-tree…) pre-installed. https://portacle.github.io/

There are some updates about Portacle last year. The latest is 1.4c Pre-release. https://github.com/portacle/portacle/releases Without Mac, can not verify it.

See also Portacle: https://portacle.github.io/ It is a portable Emacs that is ready-to-use for CL: it comes with Slime, some Emacs packages, Quicklisp and git.

Others have covered the language, but you'll also want tooling. An easy one to get started with is Portacle. It's a Lisp compiler, emacs with Lisp plugins, QuickLisp package manager, etc. so you don't have to spend time setting it all up.

1) I also love VSCode ... but for Lisp Emacs really is so much better. Look at Portacle. It basically is Emacs that's well configured for Common Lisp with SBCL right out of the box. You'll have to learn how SLIME work (the shortcuts to recompile running Lisp, etc).