scicloj / clay.el

Emacs bindings for the Clojure Clay tool
GNU General Public License v3.0
9 stars 2 forks source link

Clay package gives error, but (copied and pasted) code gives expected results #2

Open light-matters opened 7 months ago

light-matters commented 7 months ago

clay-error

Installing the package using (doom) emacs (nativecomp, 29.1-4), I get the error: "Wrong type argument: commandp, clay/" when trying the relevant function, f.

If I just copy and paste the contents of clay.el into emacs and run it however, the functions seem to work and there is no '(nil)' argument seen in the M-x list.

There is also no documentation available (e.g. when using describe function) when importing the package in the normal way, using doom.

daslu commented 7 months ago

@light-matters thanks.

How do you install the package? By simply M-x package-refresh-contents and then M-x package-install, or some other method?

Could you try reinstalling?

(Probably you've noticed -- the API has changed, and functions now are called clay-make-ns-html rather than clay/make-ns-html, etc. So you will need to update your key bindings.)

light-matters commented 7 months ago

I install (in doom emacs) by using

(package! clay
  :recipe (:type git
           :host github
           :repo "scicloj/clay.el"))

Indeed, the API change means that functions are duplicated above. I'm not entirely sure why the old functions are still available though as they're not in my config. It's maybe some kind of doom emacs caching.

daslu commented 7 months ago

@light-matters thanks.

Probably, somewhere under your ~/.emacs.d directory (or wherever the emacs config lives), there are subdirectories of installed packages.

I would look for a clay subdirectory:

find ~/.emacs.d/ -name clay

erase it, and reinstall.

Does this work for you?

light-matters commented 4 months ago

Not sure if this is a local problem, but clay still doesn't play nicely for me with doom emacs. I still have to manually eval the .el file, rather than the usual way of installing packages. The installation instructions on the main page don't work for me either.