[digiKam-users] filtering pictures modified today

[Marc Palaus]

Hi Dougie,

My simple script was from back in 2019 and did not work anymore. I 
checked, and yes, I had to run that same line to get the debug output.

Basically It's a wrapper script that launches digikam in debug mode, and 
greps the lines that match new or removed items:

#!/bin/bash
export QT_LOGGING_RULES="digikam*=true"
~/Applications/digiKam-7.8.0-20220729T111547-x86-64_7f3f87dbfb7a3c7c7354f5517a91c209.appimage 
--database-directory ~/Imatges/digikam-proves > digikamoutput.txt 2>&1 &

tail -f digikamoutput.txt | grep -E 'Adding new item|Removed items'

For the removed items, you will only get a number (the image id). You 
can find the filename using sqlite3 and running a simple query:

sqlite3 -line ~/path/to/digikam4.db 'select * from Images where id = 16328;'

Someday I'll make a nicer version. I hope it helps,

Marc

El 26/7/22 a les 12:00, Dougie Nisbet ha escrit:
> On 23/07/2022 00:45, Marc Palaus wrote:
>> In my case, I have a simple script that wraps digikam during startup, 
>> reads the output log, and lists which files have been added and which 
>> files have been removed during that launch.
>
> Out of interest, how do you log output? I'm using the appimage and I 
> don't know if that affects things. The only way I can find of logging 
> is to use the
>
> |export QT_LOGGING_RULES="digikam*=true"|
>
> line as suggested for debugging and that's very verbose. I have a 
> separate bash script that processes all the image files modified since 
> the last time it was run and that works ok for me.
>
> Dougie
> ||
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220809/3da96cdb/attachment.htm>