On 3/29/21 12:28 AM, Bill Wohler wrote:
I like it. A lot.
Rather than have a single ~/.config/darktable directory, I'd have a
.darktable directory in each of my photo directories (I have several)
that contains relative references to the images. If the top-level
directory moves, the database moves with it.
To follow with the Git analogy, I would do this:
cd ~/...photo-directory-1; darktable --init
cd ~/...photo-directory-2; darktable --init
can you tell me where & how to use --init ? seems logical, but no --init
here :(
> [darktable@omen-gatworks a]$
/home/darktable/rpmbuild/BUILD/darktable-3.4.1/x86_64-redhat-linux-gnu/bin/darktable
--init
usage:
/home/darktable/rpmbuild/BUILD/darktable-3.4.1/x86_64-redhat-linux-gnu/bin/darktable
[options] [IMG_1234.{RAW,..}|image_folder/]
options:
--cachedir <user cache directory>
--conf <key>=<value>
--configdir <user config directory>
-d {all,cache,camctl,camsupport,control,dev,fswatch,imageio,input,
ioporder,lighttable,lua,masks,memory,nan,opencl,params,perf,
pwstorage,print,signal,sql,undo}
--d-signal <signal>
--d-signal-act <all,raise,connect,disconnect,print-trace>
--datadir <data directory>
--disable-opencl
-h, --help
--library <library file>
--localedir <locale directory>
--luacmd <lua command>
--moduledir <module directory>
--noiseprofiles <noiseprofiles json file>
-t <num openmp threads>
--tmpdir <tmp directory>
--version
[darktable@omen-gatworks a]$
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
