Lorenzo, thank you for the solution. I think I understood the idea behind.
It took some time to search for WIN 10 equivalent tools and all the translations for the related darktable module names. One problem with removing a deactivated module is the fact, that it is visible but deactivated in the history stack but no longer attached to the active module group. Therefore I have to find it, what I personally think is not too logic at all. In other words, used but deactivated modules should stay in the activated modules group. Haribo M Am 22.07.2018 um 13:01 schrieb Lorenzo Bolzani: > > I doubt this is an existing functionality. If you are comfortable with > shell programming you could try this: > > > - Go into core options and enable: "look for updated xmp files on startup" > > https://www.darktable.org/usermanual/en/core_options.html > <https://www.darktable.org/usermanual/en/core_options.html> > > This will make the next startup very slow and may find other "out of > synch" xmp files around. It won't make any changes unless you say so later. > > - close darktable > > - grep the xmp files to find the ones with the module > > - use xmlstarlet or something like that to add a "darktable tag" > ("dc:subject" block) or a color ("darktable:colorlabels") > > Of course do this on a couple of test files first and triple check the > result. Have the script making a backup copy of the xmp too (only if a > backup is not already there). > > - start darktable and choose to reload the recently modified xmp files > from the dialog you'll see > > - now you can search and sort your files from darktable > > - now you can disable the "look for updated xmp files on startup" > > > If you want something simpler, from the root of all your images folders: > > mkdir xmp_export > > grep -lr --include="*.xmp" 'darktable:operation="YOUR_MODULE"' | sed > 's/.xmp//' | xargs -I% bash -c "cp --parents %* xmp_export/" > > > This will find all the matching xmp and corresponding images and copy > them into the export folder (keeping the folder structure). It's a > different thing, but if you just want to have a quick look at the > situation this will work. > > > One last thing, to "remove" a module from DT history I do this, similar > to what Remco wrote: > > - deactivate the module > - compress history > - select the history line just below the deactivated module (the second one) > - compress history > > yes, it's horrible. > > BTW, I think compress history should do this automatically (I mean > removing modules that are off). > > > > > Bye > > Lorenzo > > > > 2018-07-22 11:26 GMT+02:00 Harald <mj...@email.de <mailto:mj...@email.de>>: > > Hi, > > I was trying / using far too many modules in the past. > > Today I would like to find all my images using a specific module > (several modules and hundreds of images, to be honest). > > What do I need to do to find all my current images using a specific > module? I would like to have this search (image list) for later removing > a specific module from all related images? > > Can I therefore narrow down the 'history' image attribute or would this > be a new and - in my understanding - very helpful extension of > functionality? > > Thanks for your help and nice weekend > > Haribo M > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > <mailto:darktable-user%2bunsubscr...@lists.darktable.org> > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
