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 <
[email protected]> wrote:

> 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
> [email protected]
>
> On Tue, Jan 28, 2020 at 10:25 AM Anton Aylward <[email protected]>
> wrote:
>
>> On 2020-01-28 5:17 a.m., Subhash Fotografie wrote:
>> > [Matt Maguire <[email protected]> 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
>> quickly disappearing that I cannot read it. And I do not know where to find
>> it in a log.
>> >
>> > Looking at the console I find many many error reports for darktable.
>> Among others:
>> >
>> > 28.1.2020 10:55:30,840 [0x0-0x4f04f].org.darktable: sh: exiftool:
>> command not found
>> >
>> > I don't know what that means. (I can work with exiftool in the terminal
>> using the tcsh shell.)
>>
>> I *think" what that means is when DT invokes an system service such as
>> exiftool
>> it is using a shell that calls itself "sh" such as the BASH shell.  I'd be
>> curious what the value of SHELL is in the environment when DT is invoked
>> and
>> whether DT uses that or if the shell to use or it's absolute address
>> (ignoring
>> PATH) is hard coded.
>>
>> I'm also curious as to how your tcsh finds exiftool.  Is it aliased or is
>> on via
>> PATH?  If the latter, this raises questions about how DT's shell,
>> whatever it
>> its mechanism, isn't finding it.  Perhaps the ~/.tcshrc  sets it in a way
>> that
>> the ~/.bashrc that 'sh' uses doesn't.
>>
>>
>> --
>> The illegal we do immediately. The unconstitutional takes a little longer.
>>     -- Henry Kissinger, New York Times, Oct. 28, 1973
>>
>> ____________________________________________________________________________
>> darktable user mailing list
>> to unsubscribe send a mail to
>> [email protected]
>>
>>
> ____________________________________________________________________________
> darktable user mailing list to unsubscribe send a mail to
> [email protected]
>

____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to