On 20 Sep 2013, at 08:05, Georg Bauhaus <[email protected]> wrote: > > Am 20.09.2013 um 08:32 schrieb Simon Wright: > >> On 20 Sep 2013, at 02:32, Stephen Leake <[email protected]> >> wrote: >> >>> Simon Wright <[email protected]> writes: >>>> >>>> The stumbling block was that build/wisi/Makefile does the byte >>>> compilation using plain "emacs" which, on Mac OS X, opens the >>>> command-line version which is 22.1.1 :-) >>> >>> Can't you set PATH? >> >> I get a dialog box "This application will not run on your computer. Sorry!"; >> will have to leave this for later! >> > > This looks like a message from that Emacs start script (in Ruby) > which is part of the Pure Emacs for Mac made by David Caldwell. > FTR, he has just now added a fix, which may help in this case, > too, announced for a nightly build, probably using the [cmdname, > argv0], arg1, ... form of exec. > (The occasion for the change is a bug in the script triggered > by spaces in the path to the executable and an empty ARGV.) > > One of his hints was to try passing some option, then ARGV is > not the empty list. The above effect is caused by how > Ruby's exec interacts with the shell (if ARGV is []). > > I'll see if my own, dumb workaround will do, > - exec versions[highest_compatible_version], *ARGV > + executable = versions[highest_compatible_version], *ARGV > + exec %("#{executable}")
My workround is to invoke Emacs rather than emacs. The joys of HFS ... _______________________________________________ Emacs-ada-mode mailing list [email protected] http://host114.hostmonster.com/mailman/listinfo/emacs-ada-mode_stephe-leake.org
