From ron at flownet.com Mon Sep 4 10:46:25 2017 From: ron at flownet.com (Ron Garret) Date: Mon, 4 Sep 2017 10:46:25 -0700 Subject: [Openmcl-devel] Where does CCL development stand? In-Reply-To: References: Message-ID: <28BAA931-E821-477C-8411-CB3BED1D5776@flownet.com> This list has been awfully quiet lately. Is CCL still under active development? If so, where is the trunk nowadays? Has it officially moved to github? The docs still refer to the SVN repo but there doesn?t seem to have been any code checked in there for quite a while. rg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: Message signed with OpenPGP using GPGMail URL: From rwiker at gmail.com Mon Sep 4 10:53:43 2017 From: rwiker at gmail.com (Raymond Wiker) Date: Mon, 4 Sep 2017 19:53:43 +0200 Subject: [Openmcl-devel] Where does CCL development stand? In-Reply-To: <28BAA931-E821-477C-8411-CB3BED1D5776@flownet.com> References: <28BAA931-E821-477C-8411-CB3BED1D5776@flownet.com> Message-ID: <15D71DF5-4ABD-42E8-B681-EA65858B8E55@gmail.com> > On 4 Sep 2017, at 19:46 , Ron Garret wrote: > > This list has been awfully quiet lately. Is CCL still under active development? If so, where is the trunk nowadays? Has it officially moved to github? The docs still refer to the SVN repo but there doesn?t seem to have been any code checked in there for quite a while. https://github.com/Clozure/ccl , perhaps? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rme at acm.org Mon Sep 4 11:30:30 2017 From: rme at acm.org (R. Matthew Emerson) Date: Mon, 4 Sep 2017 11:30:30 -0700 Subject: [Openmcl-devel] Where does CCL development stand? In-Reply-To: <15D71DF5-4ABD-42E8-B681-EA65858B8E55@gmail.com> References: <28BAA931-E821-477C-8411-CB3BED1D5776@flownet.com> <15D71DF5-4ABD-42E8-B681-EA65858B8E55@gmail.com> Message-ID: <2FB9A068-A09D-4B66-A29F-6D8983C783FB@acm.org> > On Sep 4, 2017, at 10:53 AM, Raymond Wiker wrote: > > >> On 4 Sep 2017, at 19:46 , Ron Garret wrote: >> >> This list has been awfully quiet lately. Is CCL still under active development? If so, where is the trunk nowadays? Has it officially moved to github? The docs still refer to the SVN repo but there doesn?t seem to have been any code checked in there for quite a while. > > https://github.com/Clozure/ccl, perhaps? Yes, that's correct. Further development of CCL is taking place on GitHub. Your point about needing to update the documentation (and various web sites) to make that clear is a good one. From ron at flownet.com Mon Sep 4 12:20:00 2017 From: ron at flownet.com (Ron Garret) Date: Mon, 4 Sep 2017 12:20:00 -0700 Subject: [Openmcl-devel] *echo-expression-to-listener* Message-ID: I just filed this ticket: https://trac.clozure.com/ccl/ticket/1420 Some time between version 1.10 and 1.11 the *echo-expression-to-listener* functionality of the "Editor Execute Expression" Hemlock command stopped working. This seems to be because writing to (HEMLOCK-EXT:TOP-LISTENER-OUTPUT-STREAM) inside the context of a Hemlock command is no longer working. I started looking through the commit log (hooray git!) and found this: commit 70dac57d412f3952771a42884511ce9ae32d1006 Author: Bill St. Clair Date: Tue Sep 1 15:31:53 2015 +0000 Radically speed up IDE listener output and make it interruptible. The IDE listener output is now double-buffered. Printing threads fill one buffer, and the GUI thread empties the other. To avoid me having to hurt my brain preventing deadlock, output from the GUI thread to an IDE listener is dropped on the floor; you'll never see it. Since it's unusual to output from the GUI thread to an IDE listener (the default is the AltConsole, or, if you started CCL from a command-line shell, that shell), this shouldn't be a practical problem. Fixes #1307. Which is awesome because 1307 was also driving me nuts, but I think this may have broken *echo-expression-to-listener*. Is there no way to have our cake and eat it too? rg From ron at flownet.com Mon Sep 4 12:28:54 2017 From: ron at flownet.com (Ron Garret) Date: Mon, 4 Sep 2017 12:28:54 -0700 Subject: [Openmcl-devel] *echo-expression-to-listener* In-Reply-To: References: Message-ID: On Sep 4, 2017, at 12:20 PM, Ron Garret wrote: > I just filed this ticket: > > https://trac.clozure.com/ccl/ticket/1420 > > Some time between version 1.10 and 1.11 the *echo-expression-to-listener* functionality of the "Editor Execute Expression" Hemlock command stopped working. This seems to be because writing to (HEMLOCK-EXT:TOP-LISTENER-OUTPUT-STREAM) inside the context of a Hemlock command is no longer working. > > I started looking through the commit log (hooray git!) and found this: > > commit 70dac57d412f3952771a42884511ce9ae32d1006 > Author: Bill St. Clair > Date: Tue Sep 1 15:31:53 2015 +0000 > > Radically speed up IDE listener output and make it interruptible. > > The IDE listener output is now double-buffered. Printing threads fill > one buffer, and the GUI thread empties the other. > > To avoid me having to hurt my brain preventing deadlock, output from > the GUI thread to an IDE listener is dropped on the floor; you'll > never see it. Since it's unusual to output from the GUI thread to an > IDE listener (the default is the AltConsole, or, if you started CCL > from a command-line shell, that shell), this shouldn't be a practical > problem. > > Fixes #1307. > > Which is awesome because 1307 was also driving me nuts, but I think this may have broken *echo-expression-to-listener*. > > Is there no way to have our cake and eat it too? Hm, this seems to do the trick, though it seems rather hacky: (defcommand "Editor Execute Expression" (p) "Executes the current region in the editor Lisp. Ensures the result is visible." (declare (ignore p)) (let* ((region (copy-region (current-form-region))) (form (when *echo-expression-to-listener* (region-to-string region))) (doc (gui::top-listener-document)) (buf (when doc (gui::hemlock-buffer doc)))) (when buf (let ((HI::*CURRENT-BUFFER* buf)) (move-mark (current-point) (region-end (buffer-region buf))))) (when form (let ((s (HEMLOCK-EXT:TOP-LISTENER-OUTPUT-STREAM))) (ccl:process-run-function "foo" #'format s "~A~&" form))) (eval-region region))) From jmbaddoura at yahoo.com Sun Sep 24 08:53:15 2017 From: jmbaddoura at yahoo.com (jamil baddoura) Date: Sun, 24 Sep 2017 15:53:15 +0000 (UTC) Subject: [Openmcl-devel] How to write a ccl program using windows References: <1476350775.8245518.1506268395259.ref@mail.yahoo.com> Message-ID: <1476350775.8245518.1506268395259@mail.yahoo.com> I am new to clozure common lisp I would like to know how to edit a lisp file, how to save it, how to compile it and how to run it from ccl-1.11-windows\ccl\wx86cl.exe using windows vista. Best Regards. Jamil. From lsxvdqe at gmail.com Sun Sep 24 10:39:48 2017 From: lsxvdqe at gmail.com (lsxvdqe) Date: Sun, 24 Sep 2017 17:39:48 +0000 (UTC) Subject: [Openmcl-devel] How to write a ccl program using windows In-Reply-To: <1476350775.8245518.1506268395259@mail.yahoo.com> References: <1476350775.8245518.1506268395259.ref@mail.yahoo.com> <1476350775.8245518.1506268395259@mail.yahoo.com> Message-ID: On Sun, 24 Sep 2017, jamil baddoura wrote: > I am new to clozure common lisp I would like to know how to edit a lisp > file, how to save it, how to compile it and how to run it from > ccl-1.11-windows\ccl\wx86cl.exe using windows vista. Best Regards. Jamil. To edit a lisp file you need an editor. Any text/code editor should work. Better to use editors with some support for lisp syntax. Ability to highlight matching parens and jump between them is HIGHLY useful. Most people use emacs, which is good, but it isn't required. If you want full-blown IDE there is SLIME for emacs (SLIMV for vim). This is for any CL implementation. Clozure also has Mac-specific IDE. Lisp is highly interactive - you run code from REPL. It's like python, ruby or shell, not like C++ or pascal. To load file just use function LOAD. You'll need some docs: cliki.net - Common Lisp Wiki - tips, docs, libs and other info. www.gigamonkeys.com/book - Practical Common Lisp - great book, but might require some programming knowledge. There are also other books and tutorials - see CLiki. www.lispworks.com/documentation/common-lisp.html - The Standard, comprehensive docs of Common Lisp language. MUST HAVE. Quicklisp has offline version. clqr.boundp.org - Quick Reference, very useful cheat sheat. ccl.clozure.com/docs and trac.clozure.com/ccl - CCL implementation-specific docs. Also, CCL is now on GitHub: https://github.com/Clozure/ccl Well, this should cover most points for beginner. You don't need any fancy IDE to start. Happy hacking :)