<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Agreed.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 21, 2022, at 10:01 AM, Shannon Spires <<a href="mailto:svs@bearlanding.com" class="">svs@bearlanding.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I can't speak to the issue of graphics, but for files and directories, dired in Emacs is quite handy. It's more convenient than the Finder in many ways IMO.<div class=""><br class=""></div><div class=""><a href="https://www.inmotionhosting.com/support/edu/emacs/dired/" class="">https://www.inmotionhosting.com/support/edu/emacs/dired/</a></div><div class=""><br class=""></div><div class="">-SS</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 21, 2022, at 8:29 AM, Joakim Sandgren <<a href="mailto:info@joakimsandgren.com" class="">info@joakimsandgren.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">precious info !!<div class=""><br class=""></div><div class="">true, that lispworks would be the easiest way. and I’m using the source code only to see how things work - since I’m not good at understanding documentation without examples.</div><div class=""><br class=""></div><div class="">but in emacs/slime, what I understand, it would be quite possible to have a bunch of buffers up, changing parameters in them…</div><div class=""><br class=""></div><div class="">but are there any possibilities to do graphics in emacs ? with some library somewhere or via open-nn… something ?</div><div class="">menu ? shortcuts to open directories and files ? </div><div class="">j</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">Le 21 févr. 2022 à 15:37, mikel evins <<a href="mailto:mevins@me.com" class="">mevins@me.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 21, 2022, at 8:13 AM, Joakim Sandgren <<a href="mailto:info@joakimsandgren.com" class="">info@joakimsandgren.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">is there a fee every year for lispworks ? /joakim</span><br class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">Sort of; not exactly.</div><div class=""><br class=""></div><div class="">There's an initial purchase price that varies from zero (for the crippled personal edition) to $4500 for the all-the-bells-and-whistles enterprise edition.</div><div class=""><br class=""></div><div class="">In addition, there is an optional annual maintenance subscription that is $375 (for 32-bit versions) or $750 (for 64-bit). You don't have to buy the annual maintenance, but if you do then you get free upgrades when new major versions are released. If you don't have a maintenance contract and want a new version, you have to pay full price.</div><div class=""><br class=""></div><div class="">You also don't have to upgrade to new versions. If you want to, you can buy a version of Lispworks, don't buy the maintenance contract, and never spend another dime on the product. If you buy the Professional or Enterprise edition, you can deliver all the apps you want and do whatever you like with them (except build and distribute a Lisp development environment) and you never owe them another dime.</div><div class=""><br class=""></div><div class="">But you don't get source code for the Lisp. You get sources for the editor, but that's all.</div><div class=""><br class=""></div><div class="">CCL's unique value proposition is that it's a free, open-source Lisp that integrates well with the native windowing system and other platform frameworks on macOS. Unfortunately, it looks like macOS is migrating to Apple Silicon and CCL isn't. As far as I know, there is no other Lisp that substitutes for CCL's unique combination of advantages.</div><div class=""><br class=""></div><div class="">If you want a good Common Lisp that is free and gives you all of its sources, SBCL is a good choice, but it doesn't offer good integration with native windowing systems and doesn't offer a built-in native windowing IDE. There are ways to build windowing apps with it, but they aren't built in like CCL's support for macOS, and they're more complicated to use.</div><div class=""><br class=""></div><div class="">If you want good integration with native windowing systems—arguably better than CCL, since it's cross platform—there's Lispworks, but it's not free and doesn't give you the sources.</div><div class=""><br class=""></div><div class="">If you want a free Lisp that offers at least some way to build native windowing apps, there's ECL plus Qt. ECL works natively on M1. However, setting up ECL with Qt is rather complicated, and ECL depends on the platform C compiler to generate native code, which adds to the configuration burden. Also, like SBCL, ECL lacks a windowing IDE, unless you count Emacs and SLIME.</div><div class=""><br class=""></div><div class="">So it looks like you can't get everything you want; you'll have to decide which things are most important to you.</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">Openmcl-devel mailing list<br class=""><a href="mailto:Openmcl-devel@clozure.com" class="">Openmcl-devel@clozure.com</a><br class=""><a href="https://lists.clozure.com/mailman/listinfo/openmcl-devel" class="">https://lists.clozure.com/mailman/listinfo/openmcl-devel</a><br class=""></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">Openmcl-devel mailing list<br class=""><a href="mailto:Openmcl-devel@clozure.com" class="">Openmcl-devel@clozure.com</a><br class="">https://lists.clozure.com/mailman/listinfo/openmcl-devel<br class=""></div></blockquote></div><br class=""></body></html>