Comments on: Sleeping Too Much and Fighting With Emacs and ASDF http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/ Peter Christensen's Blog Fri, 02 Jul 2010 12:02:26 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Chris http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-485 Chris Sat, 17 May 2008 17:33:33 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-485 I use Cygwin's Clisp in Cygwin's Emacs with Slime (I'm also running Cygwin's X11 to get the Emacs gui). I tell Slime where Clisp is in my slime.el, then load that. Works fine. ASDF works without issue for me under Cygwin. In .clisprc (which must be in the Cygwin home directory) I put - #-:asdf (load "/home/Chris/asdf/asdf") (pushnew "/home/Chris/asdf/asdf_registry/" asdf:*central-registry* :test #'equal) The forward-slash after asdf_registry indicates that it's a directory, not a file. It contains symlinks (NOT Windows shortcuts) to all my .asd files (create symlinks under cygwin with this command: ln -s /path/to/relevant/asd-file). I haven't yet tried ASDF-Install, so can't comment on that (suspect it won't work, though). I have also managed to get ASDF to work with the Win32 port of SBCL. SBCL comes bundled with a version of ASDF, but I could never get it to work. A patched version of asdf.lisp which DOES work can be found here - http://www.lichteblau.com/blubba/shortcut/asdf.lisp Create a .sbclrc file in your home directory (find out where SBCL thinks that is by evaluating (user-homedir-pathname)), and add the following - (require 'asdf) pushnew "/path/to/asdf/central-registry/" asdf:*central-registry* :test #'equal) I have symlinks in my asdf registry, so I can't vouch for ordinary Win32 shortcuts with SBCL. Hope some of that helps anyone who's understandably experienced difficulty with this issue (quite a few people, it seems). I use Cygwin’s Clisp in Cygwin’s Emacs with Slime (I’m also running Cygwin’s X11 to get the Emacs gui). I tell Slime where Clisp is in my slime.el, then load that. Works fine. ASDF works without issue for me under Cygwin. In .clisprc (which must be in the Cygwin home directory) I put -

#-:asdf (load “/home/Chris/asdf/asdf”)
(pushnew “/home/Chris/asdf/asdf_registry/” asdf:*central-registry* :test #’equal)

The forward-slash after asdf_registry indicates that it’s a directory, not a file. It contains symlinks (NOT Windows shortcuts) to all my .asd files (create symlinks under cygwin with this command: ln -s /path/to/relevant/asd-file). I haven’t yet tried ASDF-Install, so can’t comment on that (suspect it won’t work, though).

I have also managed to get ASDF to work with the Win32 port of SBCL. SBCL comes bundled with a version of ASDF, but I could never get it to work. A patched version of asdf.lisp which DOES work can be found here -

http://www.lichteblau.com/blubba/shortcut/asdf.lisp

Create a .sbclrc file in your home directory (find out where SBCL thinks that is by evaluating (user-homedir-pathname)), and add the following -

(require ‘asdf)
pushnew “/path/to/asdf/central-registry/” asdf:*central-registry* :test #’equal)

I have symlinks in my asdf registry, so I can’t vouch for ordinary Win32 shortcuts with SBCL.

Hope some of that helps anyone who’s understandably experienced difficulty with this issue (quite a few people, it seems).

]]> By: Installing CLISP, Emacs, and SLIME on Windows XP » What’s In Peter’s Head http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-464 Installing CLISP, Emacs, and SLIME on Windows XP » What’s In Peter’s Head Fri, 16 May 2008 15:48:56 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-464 [...] week, I had been putting off setting up a CL/Emacs/SLIME environment from scratch ever since I had trouble getting ASDF to work with Lispbox. Every time I tried, I ran into some will-sapping problem like needing to find a good [...] [...] week, I had been putting off setting up a CL/Emacs/SLIME environment from scratch ever since I had trouble getting ASDF to work with Lispbox. Every time I tried, I ran into some will-sapping problem like needing to find a good [...]

]]> By: Peter http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-274 Peter Mon, 03 Mar 2008 16:38:57 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-274 novaburst - I'm using Windows because it's one constraint that's not that flexible, plus it's one more thing to learn while I'm already juggling several. My best machine is my work laptop (can't muck with OS), then my home desktop (share with wife, can't do Linux there), then my home laptop (weird hardware that has never run Linux well) and then my other home desktop (it has Linux on it but it's hard to get excited about your 4th best computer). Johnny - Sorry for the posting problem - I think it's the Apache setup on my shared host. You may have inspired me to finally deal with it (but it's one more painful thing taking me away from fun stuff). Thanks for the tips so far, that jives with mostly with what I've already read. I especially appreciate the cygwin tips. The one tip I would give you (based on reading lots of discussions on the intarweb) is that IF YOU'RE ON WINDOWS, DON'T BOTHER WITH ASDF-INSTALL. The process relies way too much on the Linux toolchain that trying to force Windows/Cygwin to use it just isn't worth it. Just download packages manually and set up ASDF by hand. When I get around to posting about my ASDF experiences, I'll link to references there. novaburst – I’m using Windows because it’s one constraint that’s not that flexible, plus it’s one more thing to learn while I’m already juggling several. My best machine is my work laptop (can’t muck with OS), then my home desktop (share with wife, can’t do Linux there), then my home laptop (weird hardware that has never run Linux well) and then my other home desktop (it has Linux on it but it’s hard to get excited about your 4th best computer).

Johnny – Sorry for the posting problem – I think it’s the Apache setup on my shared host. You may have inspired me to finally deal with it (but it’s one more painful thing taking me away from fun stuff). Thanks for the tips so far, that jives with mostly with what I’ve already read. I especially appreciate the cygwin tips.

The one tip I would give you (based on reading lots of discussions on the intarweb) is that IF YOU’RE ON WINDOWS, DON’T BOTHER WITH ASDF-INSTALL. The process relies way too much on the Linux toolchain that trying to force Windows/Cygwin to use it just isn’t worth it. Just download packages manually and set up ASDF by hand. When I get around to posting about my ASDF experiences, I’ll link to references there.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-273 Johnny Kwan Mon, 03 Mar 2008 06:24:22 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-273 ASDF is where I'm stuck. I tried following these directions for installing ASDF-INSTALL: http://common-lisp.net/project/asdf-install/tutorial/setup.html However, CLisp seems to be ignoring my .clisprc. Also, there's a package called slime-asdf which comes with SLIME. This is how to load it: http://bc.tech.coop/blog/070927.html However, it doesn't install ASDF itself, it just makes SLIME aware of ASDF. That's all I've got. Please let me know if you get any further or exhaust any leads. ASDF is where I’m stuck. I tried following these directions for installing ASDF-INSTALL:

http://common-lisp.net/project/asdf-install/tutorial/setup.html

However, CLisp seems to be ignoring my .clisprc.

Also, there’s a package called slime-asdf which comes with SLIME. This is how to load it:

http://bc.tech.coop/blog/070927.html

However, it doesn’t install ASDF itself, it just makes SLIME aware of ASDF.

That’s all I’ve got. Please let me know if you get any further or exhaust any leads.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-272 Johnny Kwan Mon, 03 Mar 2008 06:21:54 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-272 Get SLIME. Unzip it to the site-lisp directory, in its own slime directory. In your .emacs: (add-to-list 'load-path "C:/Program Files/emacs-22.1/site-lisp/slime") (require 'slime) (slime-setup) Now SLIME should be all set. Restart Emacs, and issue M-x slime. Emacs should start a Clisp process and hook a SLIME REPL to the CLisp port. Get SLIME. Unzip it to the site-lisp directory, in its own slime directory.

In your .emacs:

(add-to-list ‘load-path “C:/Program Files/emacs-22.1/site-lisp/slime”)
(require ’slime)
(slime-setup)

Now SLIME should be all set. Restart Emacs, and issue M-x slime. Emacs should start a Clisp process and hook a SLIME REPL to the CLisp port.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-271 Johnny Kwan Mon, 03 Mar 2008 06:19:51 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-271 Before getting SLIME, you have to tell Emacs to use your Lisp binary. I use CLisp from Cygwin for convenience and cost. To get Emacs to pick it up, I add this to my custom-set-variables command in my .emacs: '(inferior-lisp-program "C:/cygwin/bin/clisp.exe -K full") You can, of course, use setq if you want. Before getting SLIME, you have to tell Emacs to use your Lisp binary. I use CLisp from Cygwin for convenience and cost. To get Emacs to pick it up, I add this to my custom-set-variables command in my .emacs:

‘(inferior-lisp-program “C:/cygwin/bin/clisp.exe -K full”)

You can, of course, use setq if you want.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-270 Johnny Kwan Mon, 03 Mar 2008 06:16:21 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-270 Oops, I meant http://ftp.gnu.org/pub/gnu/emacs/windows/emacs-22.1-bin-i386.zip. Oops, I meant http://ftp.gnu.org/pub/gnu/emacs/windows/emacs-22.1-bin-i386.zip.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-269 Johnny Kwan Mon, 03 Mar 2008 06:15:24 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-269 XEmacs doesn't feel right. The GNU Emacs that comes with Cygwin can be run in two modes: console and X-window. Neither feel right in Windows. So I use native Windows GNU Emacs. (You can drag-and-drop lists of files from Windows Explorer onto the Emacs window to open them, among other things.) Download http://ftp.gnu.org/pub/gnu/emacs/windows/emacs-21.3-bin-i386.tar.gz, which contains the Windows binaries. Use the Cygwin bash prompt to unzip and untar this file into its own folder (tar -xvf). I rename the folder to emacs-22.1 and move it into C:\Program Files. Modules intended for use by all users of the PC should be maintained in the site-lisp directory of the emacs directory. That's where I put everything. Native Windows Emacs has to be "cygwinized", i.e. convert Unix paths to Windows paths. To do this, get the cygwin-mount.el and setup-cygwin.el files from the Emacs Wiki and download them to site-lisp. Then put the following in your .emacs: (require 'setup-cygwin) Unfortunately, there's a bug (unhandled case?) that SLIME trips across. I'm unclear on the specifics, but here's the workaround: http://www.cliki.net/SLIME%20Tips in the Cygwin section You essentially tell Cygwin that /c is the same as C:\. XEmacs doesn’t feel right. The GNU Emacs that comes with Cygwin can be run in two modes: console and X-window. Neither feel right in Windows. So I use native Windows GNU Emacs. (You can drag-and-drop lists of files from Windows Explorer onto the Emacs window to open them, among other things.)

Download http://ftp.gnu.org/pub/gnu/emacs/windows/emacs-21.3-bin-i386.tar.gz, which contains the Windows binaries. Use the Cygwin bash prompt to unzip and untar this file into its own folder (tar -xvf). I rename the folder to emacs-22.1 and move it into C:\Program Files.

Modules intended for use by all users of the PC should be maintained in the site-lisp directory of the emacs directory. That’s where I put everything.

Native Windows Emacs has to be “cygwinized”, i.e. convert Unix paths to Windows paths. To do this, get the cygwin-mount.el and setup-cygwin.el files from the Emacs Wiki and download them to site-lisp. Then put the following in your .emacs:

(require ’setup-cygwin)

Unfortunately, there’s a bug (unhandled case?) that SLIME trips across. I’m unclear on the specifics, but here’s the workaround:

http://www.cliki.net/SLIME%20Tips
in the Cygwin section

You essentially tell Cygwin that /c is the same as C:\.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-268 Johnny Kwan Mon, 03 Mar 2008 06:05:07 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-268 Ah, to hell with it. I don't think I can get around this, and I need all the help I can get, so I'll be commenting again in chunks. Get Cygwin Windows command line sucks. Bash is much better. Also, Cygwin comes with a package installer, a la RPM, APT, and YUM. Also, the utilities can't be beat, so get Cygwin. Run the setup.exe installer. By default, the installer and all installation sources are downloaded to C:\Program Files\cygwin. Cygwin itself is installed to C:\cygwin. Only the core stuff is installed by default. When you want to add another Cygwin program (like CLisp), you have to specifically enable it. You can rerun C:\Program Files\cygwin\setup.exe at any time for this purpose. Ah, to hell with it. I don’t think I can get around this, and I need all the help I can get, so I’ll be commenting again in chunks.

Get Cygwin

Windows command line sucks. Bash is much better. Also, Cygwin comes with a package installer, a la RPM, APT, and YUM. Also, the utilities can’t be beat, so get Cygwin.

Run the setup.exe installer. By default, the installer and all installation sources are downloaded to C:\Program Files\cygwin. Cygwin itself is installed to C:\cygwin.

Only the core stuff is installed by default. When you want to add another Cygwin program (like CLisp), you have to specifically enable it. You can rerun C:\Program Files\cygwin\setup.exe at any time for this purpose.

]]> By: Johnny Kwan http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/comment-page-1/#comment-267 Johnny Kwan Mon, 03 Mar 2008 06:00:32 +0000 http://www.pchristensen.com/blog/articles/sleeping-too-much-and-fighting-with-emacs-and-asdf/#comment-267 http://bc.tech.coop/blog/070927.html http://common-lisp.net/project/asdf-install/tutorial/setup.html I'm facing the same challenges and had a long involved comment on how to install Cygwin, Cygwin-CLisp, Windows native Emacs, and SLIME. But the submit failed, and I lost it, and I don't feel like typing it again. http://bc.tech.coop/blog/070927.html

http://common-lisp.net/project/asdf-install/tutorial/setup.html

I’m facing the same challenges and had a long involved comment on how to install Cygwin, Cygwin-CLisp, Windows native Emacs, and SLIME. But the submit failed, and I lost it, and I don’t feel like typing it again.

]]>