Future of the emacs library

Hi guys, it seems this thread has freezed long time ago, and I am curious if there are some plans with scel.

From my point of view, I miss only one thing, and thats the reason I am writing here.
I see no ability to run a code block within parentesis, without selecting whole thing. I think if it is possible in vim, in emacs it should be easy to implement. Or am I missing something?

C-M-x doesn’t work? it does in my scel. :grin:

1 Like

thanks Luka, I am a new guy in emacs, and somehow I was not able to find this.
best!

paum

I have the impression that Emacs can have a renaissance now, as it has the best conditions to absorb the most advanced tools today, the same ones we have in vscode.

Scel can become much superior than scide. Also, there is a lot of potential integrating Sc and vscode.

Let’s take very good care of scel. That’s how I see it.

2 Likes

Hi all, I was tinkering with Emacs widgets, implemented in Scel, and the result are some new docs files. You can check the xmass edition PRs Pull requests Ā· supercollider/scel Ā· GitHub , comments are welcomed.

1 Like

Are scel widgets working correctly right now? I thought there were some problems (some minor) there right now.

you’re right. there are some minor bugs on lisp side. I just put together documentation, so one can easily see and try what is available and how it works. seems that scel github repository has no active admin. or maybe I am too pushy:)

I’m not sure why this never happened. Could it be a deliberate decision by the developers? Perhaps it’s because the Emacs mode and the SC classes need to always be shipped together to avoid potential issues. (Although there is a PR in this direction right now)…

Interestingly, there is a sclang-extensions package available on Melpa, but it’s a somewhat puzzling situation. I’m uncertain about whether it’s actively maintained.

No, it’s good to have more documentation. Well done.

I checked and it seems there are people there, but not much activity. I don’t know how it’s organized. It would be good to know.

What does the stewardship of the library currently look like? Are there multiple maintainers, do they feel fine in their position? I just submitted a small PR and saw that there are a frew open pull requests which are left unanswered for some months.

1 Like

I would like to know more about it too. We should improve how we contribute to scel and make it more convenient.

I’m looking at this now as the README currently is not applicable or sufficiently explanatory so writing this answer to be helpful for future readers.

I’m not sure why this never happened.

Compatibility with MELPHA guidelines [1].

Perhaps it’s because the Emacs mode and the SC classes need to always be shipped together to avoid potential issues. (Although there is a PR in this direction right now)…

sclang-vars.el.in used to be necessarily filled in by CMake as part of build process. Now it is not necessary, fixed via [2]. So it is how it is now for historical reasons and to support different means of install.

Configurable via those custom variables if the default doesn’t work.

Looks like all the sclang* packages currently available on Melpa/el-get are crufty and/or unusable.

With Doom Emacs the package directive should be along the lines of:

(package! scel :recipe (:host github :repo "supercollider/scel" :files ("el/*.el")) :pin "a5c178bdc7ffe01c19ad7b42218cc62e68320e75")

Other examples of package consumption are scattered, they should be put in the README perhaps along with those custom variables.

2 Likes