Thanks for the reminder!
A few things about the scripts repo… The first thing I tried was to symlink individual scripts into my
~/.config/darktable/lua directory, but that really breaks down when you hit scripts that require stuff from the
lib folder. The best way really is to just clone the repo straight in there or symlink it. e.g. a simpler setup instruction would be:
git clone https://github.com/darktable-org/lua-scripts/
ln -s lua-scripts lua
Then individual plugins can be enabled with:
echo 'require "contrib.rate_group"' >> luarc
Changes need Darktable to be restarted of course.
luarc currently has this:
local dt = require "darktable"
I found it useful to give visual feedback for process because, as it turns out, I had trouble loading some plugins when using the first approach (of symlinking individual scripts instead of the whole repo). Using
dartable -d lua is also essential in debugging issues with those scripts, which are totally silent (even on failure) by default.
Of the above, I think the “group rate” plugin is the most important, and should really be enabled by default… I haven’t tried the others just yet, but I’m curious to see where it brings me.
So thanks for bringing up this topic again, I was just trying to figure out how to “group rate” recently and I am really happy to have found that little gem!
(PS: I wonder how much of the above would belong in the README file? It would certainly have saved me some time if this was spelled out a little more clearly…)