If I remember correctly when you run darktable on MacOS it uses a "system"
version of the path and not the user's path. We used to try and use which
to find commands and it would work on the command line, but not from a
script.
Bill
On Tue, Jan 28, 2020 at 11:45 AM August Schwerdfeger <
aug...@s
It appears that I need to update the usermanual too... :/
On Tue, Jan 28, 2020 at 12:18 PM William Ferguson
wrote:
> I've also submitted a PR to remove include_all.lua :)
>
> Bill
>
> On Tue, Jan 28, 2020 at 12:05 PM William Ferguson
> wrote:
>
>> I've been seeing this conversation show up in
I've also submitted a PR to remove include_all.lua :)
Bill
On Tue, Jan 28, 2020 at 12:05 PM William Ferguson
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 i
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 o
* Patrick Shanahan [01-28-20 11:41]:
> * Subhash Fotografie [01-28-20 10:26]:
> > [Patrick Shanahan 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/need
If this is a Lua script trying to invoke 'exiftool', the Lua API uses the
'system()' function as its method of running external programs. I believe
'system()' is required by the POSIX standard to pass its argument to 'sh'
rather than any shell the user might define.
--
August Schwerdfeger
aug...@s
* Subhash Fotografie [01-28-20 10:26]:
> [Patrick Shanahan 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
On 2020-01-28 5:17 a.m., Subhash Fotografie wrote:
> [Matt Maguire schrieb am 28.1.2020 um 8:27 Uhr:]
>
>> So, easiest way around this is to define the location of exiftool in your
>> preferences file …
>
> OK, very fine, this did it for the error message to disappear! Thank you
> again!
>
> B
[Patrick Shanahan 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 happe
* Matt Maguire [01-28-20 09:11]:
> So Patrick, I think the issue is that Subhash had all the scripts from the
> contrib archive enabled, but some of them are not very robustly coded and
> so fail on a Mac (eg. autostyle will look in darktablerc for a path to the
> exiftool binary, and if it doesn’
So Patrick, I think the issue is that Subhash had all the scripts from the
contrib archive enabled, but some of them are not very robustly coded and
so fail on a Mac (eg. autostyle will look in darktablerc for a path to the
exiftool binary, and if it doesn’t find it, then on Linux systems only it
w
* Subhash Fotografie [01-28-20 05:19]:
> [Matt Maguire schrieb am 28.1.2020 um 8:27 Uhr:]
>
> >So, easiest way around this is to define the location of exiftool in your
> >preferences file …
>
> OK, very fine, this did it for the error message to disappear! Thank you
> again!
>
> But… now I g
[Matt Maguire schrieb am 28.1.2020 um 8:27 Uhr:]
>So, easiest way around this is to define the location of exiftool in your
>preferences file …
OK, very fine, this did it for the error message to disappear! Thank you again!
But… now I get another one importing an new image which is so long and
[Patrick Shanahan schrieb am 27.1.2020 um 18:04 Uhr:]
>grep -ir exiftool ~/.config/darktable/*
>autostyle.lua
>enfuseAdvanced.lua
>fujifilm_ratings.lua
Indeed!
So I learned, searching with Spotlight is not accurate.
--
Photography is the only language,
which can be misunderstood all around th
* Subhash Fotografie [01-27-20 13:43]:
> AND disabling the LUA script control_exiftool_export, close and open DT new
> did NOT let the error disappear! It has to be another problem, I think.
>
>
> [Subhash Fotografie schrieb am 27.1.2020 um 19:32
> Uhr:]
>
> >Hm,
>
> >exif_cmd = "/usr/local
AND disabling the LUA script control_exiftool_export, close and open DT new did
NOT let the error disappear! It has to be another problem, I think.
[Subhash Fotografie schrieb am 27.1.2020 um 19:32 Uhr:]
>Hm,
>exif_cmd = "/usr/local/bin/exiftool "..options..options2.." -
>overwrite_original "
On Sun, 26 Jan 2020 at 23:26, Subhash Fotografie
wrote:
> [Matt Maguire schrieb am 25.1.2020 um 9:17
> Uhr:]
>
> >And how exactly are you
> >"opening an image" when you see the error message?
>
> Clicking on "Import image" choosing the image and import it.
>
> Maybe it has to do with "enable con
So you have installed some lua script that requires exiftool. You
should check how that lua plugin calls exiftool, then you can fix the
issue either by moving exiftool, so it could be found, or by modifying
the script. Or just remove that lua script, if you are not using it
(why did you enable it t
[Matt Maguire schrieb am 25.1.2020 um 9:17 Uhr:]
>What was the exact text in the error message?
"Can't find exiftool"
>And how exactly are you
>"opening an image" when you see the error message?
Clicking on "Import image" choosing the image and import it.
Maybe it has to do with "enable contr
19 matches
Mail list logo
