11:18:46beachminion: Please tell django_ about lisppaste.
11:18:47miniondjango_: have a look at lisppaste: lisppaste is an IRC bot that runs under the nickname "lisppaste" and can be used (only for the #lisp IRC channel!) at http://paste.lisp.org/new/lisp - or http://paste.lisp.org/ for other destinations
11:19:33beachActually, because of spam, the link no longer appears in the channel automatically. You need to give us the link yourself.
11:19:43django_ok so for this http://paste.lisp.org/display/332500
11:19:57django_i dont get why i have to wait for the loop-print to return to see the output
11:20:15django_i want to call print-exp everytime user inputs y
11:29:41beachOne space before '('. Two spaces indentation. But the forms in the body of a function, or a loop should be aligned.
11:31:04beachdjango_: If your editor doesn't understand how to indent Common Lisp code, you need to switch to one that does.
11:31:56beachdjango_: I mean, you can do what you want of course. But as I said above, it is impolite (you put a huge burden or the (human) reader of your code) to submit code that has incorrect indentation.
11:45:18beachIf your editor doesn't "know" Common Lisp, it can't really be done, because indentation is different for special operators, and for macros according to the number and role of arguments.
11:45:52beachdjango_: Yes. I have been using Emacs for the past 35 years.
11:46:00White_Flameemacs is the primary lisp dev environment
11:46:21beachFirst Multics Emacs, then Gosling Emacs, then GNU Emacs.
12:15:34White_Flameyou're going to have continual problems dealing with things others assume simple, as well as problems getting help if you're not using the same environment
12:16:22White_FlameSLIME actively connects to your running Lisp image, and knows the runtime state of definitions, integrates with the debugger, lets you jump to source of defitions for symbols (which is untractable for standalone editors), etc
12:21:10django_White_Flame: so are there any projects you chose lisp over other languages
12:21:17White_Flamedjango_: I have a company, and we primarily use common lisp to develop, unless client contracts want specific code modules for their project language