Hi, The Emacs integration for Windows now tries to find your emacsclient binary by recursively searching through the "Program Files\Emacs" and "Program Files(x86)\Emacs" directories. This is the default path for emacs-w32, which is the emacs that worked the best out of the box on Windows and the one several people in the #concatenative channel liked best.
On Windows, it seems the emacs-w32 emacsclient.exe starts Emacs for you if it's not already running. On other platforms this does not seem to be the case. Also on Windows, running emacsclient with the -- no-wait parameter causes emacsclient to exit with exit code 1, so on Windows this exit code is ignored. On Unix platforms the behavior should be the same. Finally, if your emacsclient is not just "emacsclient" or in the mentioned location on Windows, you will need to set the path. There is a new "SYMBOL: emacsclient-path" for this: "/home/erg/funky/emacs/emacsclient" emacsclient-path set-global Of course I tested on Windows and Mac, but if I messed up anyone's Emacs integration beyond repair, let me know. Doug ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
