Permalink
Browse files

Update "Caveats" section to reflect successful testing on OSX with Aq…

…uamacs.
  • Loading branch information...
1 parent 371875f commit a13012646bb5da494ce2b8aab41681c48eb19568 niels giesen committed May 19, 2010
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.markdown
View
@@ -179,7 +179,7 @@ Input history (which is saved on `,quit`).
* Caveats
-1. The main mode is developed on and for a GNU/Linux environment, on GNU Emacs version 22 and above. I only have had very little time to test this on a win32 machine. The problem on that 'system' is that somehow the GIMP opens a second 'console', so it does not return anything useful to the calling program. I do not know about the behaviour on OSX. Not tested on BSD either. If you have any results (or a spare MacBook), please let me know.
+1. The main mode is developed on and for a GNU/Linux environment, on GNU Emacs version 22 and above. I only have had very little time to test this on a win32 machine. The problem on that 'system' is that somehow the GIMP opens a second 'console', so it does not return anything useful to the calling program. I do not know about the behaviour on OSX. Not tested on BSD either. If you have any results (or a spare MacBook), please let me know. UPDATE: gimp-mode is reported to 'seem to work just fine under Mac OS X 10.5.8 with gimp 2.6.8 and Aquamacs 2.0' (thanks Kevin B. Unhammer)!.
To overcome the problem of not being able to interact with the GIMP as a subprocess, Gimp Mode comes with another, similar, mode that hooks into the script-fu server provided by the GIMP as a client. You can start this mode with `M-x gimp-cl-connect` (after having started the server from within the GIMP). It was a PITA to get this to work well. The mode lacks some features of the `normal' `inferior-gimp-mode` and has some idiosyncrasies due to the behaviour of the server: the GIMP script-fu server produces a new call frame each time around, making it unable (or possibly: quite hard) to define variables, functions and macros and saving their new values without hacking the gimp source. The way around this is the macro `emacs-cl-output` in `emacs-interaction.scm`, that writes the form (wrapped in another `(with-output-to-file ...)` ) to evaluate to a temporary file, and subsequently loads that file, so that the new definition will be part of any new call frame. I'd love to be able to work something out using continuations, but I have not yet found out whether that is at all possible technically.

0 comments on commit a130126

Please sign in to comment.