Search found 8 matches
- Tue Oct 20, 2015 11:47 am
- Forum: Common Lisp
- Topic: Clcon - new Common Lisp IDE under construction
- Replies: 7
- Views: 19734
Re: Clcon - new Common Lisp IDE under construction
Hi! We have 0.2.6 file release for Windows. And, as usual, you can clone repository and build clcon at Linux. Installation page (with link to release archive): https://bitbucket.org/budden/clcon/src/default/doc/INSTALL.md?fileviewer=file-view-default Screenshots: https://bitbucket.org/budden/clcon/w...
- Thu Oct 01, 2015 3:01 pm
- Forum: Common Lisp
- Topic: Clcon - new Common Lisp IDE under construction
- Replies: 7
- Views: 19734
Re: Clcon - new Common Lisp IDE under construction
Hi! I have some experimental source highlighting. https://bitbucket.org/repo/E4aRar/images/2463267509-syntax-highlight.png It starts well and shows entire buffer colored, but hangs up as I try to edit file. Reworking of client-server dialog is needed. Also we have file release for windows, see downl...
- Tue Sep 22, 2015 2:50 pm
- Forum: Common Lisp
- Topic: Clcon - new Common Lisp IDE under construction
- Replies: 7
- Views: 19734
Re: Clcon - new Common Lisp IDE under construction
Some bits of lisp mode:
Auto-indent works, first of all.
Auto-indent works, first of all.
- Tue Sep 15, 2015 7:51 am
- Forum: Common Lisp
- Topic: Clcon - new Common Lisp IDE under construction
- Replies: 7
- Views: 19734
Re: Clcon - new Common Lisp IDE under construction
This is just pure pragmatism: 1. Tcl/Tk is the only permissively-licensed, C compiler independent, mature, cross-platform GUI toolkit I know. 2. There are no good bindings of CL to this toolkit. In fact, IDE is not written entirely in tcl. Only appropriate parts are written. IDE stays on SWANK, whic...
- Mon Aug 31, 2015 5:37 pm
- Forum: Common Lisp
- Topic: Clcon - new Common Lisp IDE under construction
- Replies: 7
- Views: 19734
Clcon - new Common Lisp IDE under construction
Hi! I'm writing a new cross-platform Common Lisp IDE. Current features: - REPL with command history and history substitution - debugger prototype (show condition, list frames, invoke restarts) - completion for lisp symbols and filenames in REPL - find source in REPL - swank-based inspector - compila...
- Fri Jan 31, 2014 9:09 am
- Forum: Common Lisp
- Topic: Macro function executed twice in SBCL
- Replies: 4
- Views: 9127
Re: Macro function executed twice in SBCL
Hi!
Bugs are quite possible in SBCL.
Try putting (break) instead of (print ...) and when (break) invokes a debugger, look at the stack trace.
Do that from SBCL console, not from SLIME. If there are filters on debug frames listed in stack trace,
disable them (read SBCL manual to check for that).
Bugs are quite possible in SBCL.
Try putting (break) instead of (print ...) and when (break) invokes a debugger, look at the stack trace.
Do that from SBCL console, not from SLIME. If there are filters on debug frames listed in stack trace,
disable them (read SBCL manual to check for that).
- Sat Jan 04, 2014 8:38 am
- Forum: Common Lisp
- Topic: Structs pointing to each other, stack overflow
- Replies: 5
- Views: 9734
Re: Structs pointing to each other, stack overflow
You do all ok, stack overflow is just as lisp tries to print your circular graph
of structures.
Set *print-circle* to t and all would work.
Answer by edgar-rft is wrong.
of structures.
Set *print-circle* to t and all would work.
Answer by edgar-rft is wrong.
- Sat Jan 04, 2014 8:30 am
- Forum: Common Lisp
- Topic: Conflict between iterate and cl-containers
- Replies: 4
- Views: 9780
Re: Conflict between iterate and cl-containers
Hi! I use patched version of iterate, http://sourceforge.net/projects/iteratekeywords/
It allows using keywords in head clauses.
So I write
(iter (:for x :in ...) (:collect ...))
instead of
(iter (iter:for x :in ...) (iter:collect ... ))
so no obfuscation and no conflicts.
It allows using keywords in head clauses.
So I write
(iter (:for x :in ...) (:collect ...))
instead of
(iter (iter:for x :in ...) (iter:collect ... ))
so no obfuscation and no conflicts.