Hello,
Sorry for the late reply on this. Haven't got that much time lately to
experiment.
So actually I got it working in any of the versions (1.0, 1.1RC1,
1.1.0-1). The trick is simply to right-click and 'Run as admin'.
Somehow, on Windows 7, emacs won't start when using a non-privileged
On Sat, Jan 30, 2010 at 10:11 PM, Shawn Hoover shawn.hoo...@gmail.comwrote:
On Sat, Jan 30, 2010 at 5:48 PM, Rollo rollo.toma...@gmail.com wrote:
Hi Shawn,
Just tried with 1.1.RC1 - no luck. Emacs server won't start and system
will start spawning thousands of cmdproxy processes again.
Hi Shawn,
You're right - my problems are with 1.1.0 on win7.
I see you've updated your page (http://clojure.bighugh.com/) with
instructions recommending using 1.1.RC1 for the moment. I'll try that
and report back here.
Thanks for your help!
Rollo
On Jan 30, 4:37 pm, Shawn Hoover
Hi Shawn,
Just tried with 1.1.RC1 - no luck. Emacs server won't start and system
will start spawning thousands of cmdproxy processes again.
Where does that bad condition comes from?
Let me know if I can help diagnose or test further.
Thanks,
Rollo
On Jan 30, 4:37 pm, Shawn Hoover
On Sat, Jan 30, 2010 at 5:48 PM, Rollo rollo.toma...@gmail.com wrote:
Hi Shawn,
Just tried with 1.1.RC1 - no luck. Emacs server won't start and system
will start spawning thousands of cmdproxy processes again.
Where does that bad condition comes from?
Let me know if I can help diagnose or
Seconded. I have the same problem on win7, augmented by the fact that
emacs spawns thousands of cmdproxy.exe...
Depending on your machine capabilities, the only thing to do then is a
hot reboot (try killing 5000 processes with new ones starting off
every second).
Works fine on winxp though...
On
when i start the clojure box 1.0, the emacs client window stay on the
top of all the other windows, eventually it display a message **
ERROR ** Timeout wating for server, but 1.0RC1 no that issue.
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
