So I've Gnu Emacs 21.3.1 running on windows and I'm interested in learning scheme. I went into the Control Panel > System > Environmental Variables and edited the PATH variable to include petite. So if I typed petite in a command prompt - up would come the interpretter - great! Or so I thought.
Next I wanted to have it runnable from Emacs, running as a child process so I can compile my code as I type it.
(custom-set-variables '(scheme-program-name "petite"))
Emacs is already preset up for such tinkery so all I need do, is tell it what my scheme program is called. This is where it all went wrong. I could tell emacs to run a shell command, type petite, and it would run it, but tell it to M-x run-scheme, and it failed with the error "spawning child process invalid argument" or a "could not find petite message" depending on if I located gave the full path to petite or just the file name and hoping the windows "path" variable would sort it out.
So various head bangings later and it turns out that emacs doesn't like the quotation marks that I put around the path in the Windows PATH variable. So remember don't to this:
PATH="path1";"path2"
do this
PATH=path1;path2
2 comments:
Anything linux == a pain in the ass, even on Windows =)
Just kidding!
Nice to see you back posting at full-speed.. been waiting for more intresting things to read from you.
I'll comment here on your post before this one too: I've been trying to get DX working inside a windows app like a map editor too but so far there's always been some glitches in the winforms buttons and such. I'll test your loop, maybe it works better.
btw, could you reduce the line-spacing in the code blocks? It's a tad annoying to read them with such huge gaps between lines.
Yeah, I've no idea where that spacing came from, as it looked alright when I previewed it.
It might be something in my blog template. I'll see if I can get it worked out next time I post some code :D
Post a Comment