Remember what I said about the debugging messages all starting with LUA ERROR even though they weren't necessarily errors? :-)
The first message means that the GIMP executable was found. The next message is the command that the system is going to execute to launch GIMP and open the file. When you closed GIMP, did it import the file and group it with the original? Things to try: try and display the file with another program and make sure it's a valid jpg file run the command that the debugger shows (i.e. gimp /Users/heviiguy/.local/tmp/HVI_7012.jpg) and see if it opens the file if GIMP opens without the file try opening it from the menu Bill On Wed, Jan 11, 2017 at 6:54 PM, J Albrecht <[email protected]> wrote: > > On 11 Jan 2017, at 17:25, J Albrecht <[email protected]> wrote: > > I attempted to solve it by including GIMP in my Path. > > > # Setting PATH for GIMP to be used with darktable (Jan 11, 2017) > PATH=$PATH:/Applications/McGimp-2.9.app/Contents/MacOS/Gimp > > > Okay: I now know how to properly set my Path. The correct edit is: > > PATH=$PATH:/Applications/McGimp-2.9.app/Contents/MacOS/ > > > Gimp now starts from the darktable export module but, it doesn’t go all of > the way. Here’s the error thrown at me: > > LUA ERROR true checkIfBinExists: gimp > > LUA ERROR gimp /Users/heviiguy/.local/tmp/HVI_7012.jpg > > The image was indeed saved (to tmp) but Gimp started without it. > > Although it’s kinda cool to figure this stuff out, I’m now well beyond my > level of comfort… > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
