We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu 20.04, emacs 27.1, supercollider 3.10
After installing, using cmake to build the *.el files, when I do m-x sclang-mode on a buffer I'm getting:
defconst: Symbol's function definition is void: sclang-make-buffer-name
I'm willing to debug, but I'm hoping somebody has some clues to what the problem might be.
The text was updated successfully, but these errors were encountered:
Me too, here is the backtrace:
Debugger entered--Lisp error: (void-function sclang-make-buffer-name) (sclang-make-buffer-name "PostBuffer") (defconst sclang-post-buffer (sclang-make-buffer-name "PostBuffer") ("/Users/.emacs.d/.local/straight/buil..." . 408)) require(sclang-interp) byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\207" [require cl-lib sclang-interp sclang-language sclang-dev] 2) #<subr autoload-do-load>((autoload "sclang-mode" ("/Users/.emacs.d/.local/autoloads.27...." . 886063) t nil) sclang-mode nil) apply(#<subr autoload-do-load> ((autoload "sclang-mode" ("/Users/.emacs.d/.local/autoloads.27...." . 886063) t nil) sclang-mode)) autoload-do-load((autoload "sclang-mode" ("/Users/.emacs.d/.local/autoloads.27...." . 886063) t nil) sclang-mode) command-execute(sclang-mode record) counsel-M-x-action("sclang-mode")
Sorry, something went wrong.
Does M-x sclang-start give similar errors?
M-x sclang-start
No branches or pull requests
Ubuntu 20.04, emacs 27.1, supercollider 3.10
After installing, using cmake to build the *.el files, when I do m-x sclang-mode on a buffer I'm getting:
defconst: Symbol's function definition is void: sclang-make-buffer-name
I'm willing to debug, but I'm hoping somebody has some clues to what the problem might be.
The text was updated successfully, but these errors were encountered: