What would it take to set up some batch files in the windows environment to perform this extending task automatically? It seems that part of the problem is the command line windows versus unix as well is directory naming issues and exact lisp syntax for installing packages. Yet Lispbox works wonders getting emacs/slime/and clisp working together like clockwork.
On 12/18/05, Peter Seibel <[EMAIL PROTECTED]> wrote:
On Dec 18, 2005, at 3:27 PM, LeAnthony Mathews wrote:
> Hey Surendra,
> At this point I think i'm on the edge of giving up. If it takes
> this much to install files to make lispbox have a GUI interface,
> then it is not worth it. I have been trying different combinations
> all day. I would suggest that a GUI be added to the distribution
> so it's part of the initial emacs/clisp/slime/wxCL distribution.
> As a new user I want to play with application design examples, not
> walk through confusing setups.
FWIW, my Lispbox was designed much more to "just work" than to be
extensible. There really is no official provision for installing new
stuff into it. So one thing that might be worth doing is to make a
Lispbox with some thought toward extensibility via ASDF install, etc.
-Peter
--
Peter Seibel * [EMAIL PROTECTED]
Gigamonkeys Consulting * http://www.gigamonkeys.com/
Practical Common Lisp * http://www.gigamonkeys.com/book/
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners
_______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
