I've also submitted a PR to remove include_all.lua :) Bill
On Tue, Jan 28, 2020 at 12:05 PM William Ferguson <[email protected]> wrote: > I've been seeing this conversation show up in many threads and was trying > to figure it out, without much luck. Then today there was a PR on the > lua-scripts repository and it all made sense. > > So I have some suggestions about how it could have come to a quicker > solution. > > If there is an issue with one of the scripts in the lua-scripts > repository, it would be a good idea to open an issue at > https://github.com/darktable-org/lua-scripts/issues. That way the > maintainers and possibly the author of the script can give support. > > The README.md at https://githib.com/darktable-org/lua-scripts provides a > lot of information about the scripts including how to install them, run > them, and avoid having to use the luarc file. > > The simple solution to the original problem was to run > tools/executable_manager.lua and use the exiftool file selector to select > the executable. Once that was done, contrib/autostyler.lua would have just > worked. > > The last recommendation is try and remember to reply to the list so that > there is only one thread to the conversation and all the information is > there. That way others might be able to help. > > Bill > > > > On Tue, Jan 28, 2020 at 11:49 AM Patrick Shanahan <[email protected]> > wrote: > >> * Patrick Shanahan <[email protected]> [01-28-20 11:41]: >> > * Subhash Fotografie <[email protected]> [01-28-20 10:26]: >> > > [Patrick Shanahan <[email protected]> schrieb am 28.1.2020 um 9:49 >> Uhr:] >> > > >> > > >I don't believe "all" is a good approach and cannot fathom why it >> would be >> > > >pursued. One should *only* activate scripts that provide a >> wanted/needed >> > > >function. Then test for compatability and deactivate if not >> compatible. >> > > >> > > This is what happened: >> > > 1) I missed functions in DT that I thought to be essential such as >> automatic backup at shutdown. >> > > 2) I found the mention of lua scripts in >> darktable.3.0.usermanual-de.pdf. >> > > 3) I found it very cumbersome to write requirements in luarc for each >> script I want to test. >> > > 4) I found the script include_all.lua and required it in luarc. So I >> had all scripts in DT preferences at the tab "Lua options" and enabled the >> ones I wanted. That were NOT all only some of them. >> > > 5) I thought only the enabled scripts are active. >> > >> > did you look at the script, include_all.lua? >> > The header has: >> > INCLUDE ALL >> > Automatically include all scripts in the script repository >> > >> > >> > >> > NOTE: some attention to detail is required of YOU. >> > repeat >> > repeat >> > repeat >> > >> > >> > The *enabled* scripts will all be listed in ~/.config/darktable/luarc as >> > require "contrib/autostyle" >> > require "contrib/clear_GPS" >> > require "contrib/copy_attach_detach_tags" >> > >> > enables/activates scripts: autostyle.lua >> > clear_GPS.lua >> > copy_attach_tags.lua >> >> that was a little heavy, sorry. I don't know about dt activating or not, >> have only used the luarc to control. >> >> If I was you I would go thru the luarc and only enable what you *really* >> need there and not the "script" >> >> -- >> (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri >> http://en.opensuse.org openSUSE Community Member >> facebook/ptilopteri >> Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet >> freenode >> 8 >> >> ____________________________________________________________________________ >> darktable user mailing list >> to unsubscribe send a mail to >> [email protected] >> >> ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
