On jeudi 12 janvier 2017 08:50:03 CET J Albrecht wrote: > > On 11 Jan 2017, at 22:46, William Ferguson <[email protected]> wrote: > > > > You could ask the MacOS GIMP packagers about the error and see if they > > have any ideas > I wouldn’t know where to begin to ask. Seems that something like this would > require a certain degree of coordination between the Mac OS packagers of > both Gimp and darktable. Based on similar User requests for > interoperability between programs (a current one relating to darktable and > DigiKam comes to mind) I can appreciate that the packagers have more > pressing matters to contend with. > > Well, this inability to call Gimp from Darktable isn’t a critical issue in > any case. Back to the old way of doing things…
In an earlier message you posted : > Python quit unexpectedly while using the libglib-2.0.0.dylib plug-in. as part of the error messages you received. Some use of Google seems to show that this error occurs when the python you have was compiled against a different version of libglib-2.0.0.dylib than the one you have installed. And if using "Gimp <file>" on the command line gives the same error, then it's not a Darktable problem, but a version mismatch on your system. (starting gimp from the command line doesn't touch Darktable in any way) ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
