I see it and use it a lot. Maybe that's not significant to you, but it's
significant to me.
Zach
On Tue, Dec 8, 2020 at 2:51 PM Jean-Claude Beaudoin <
jean.claude.beaud...@gmail.com> wrote:
>
> Hello Pros of Common Lisp,
>
> Here is my attempt at starting a significant (and hopefully useful) deb
; http://cliki.net/Quicklisp%20tutorial. I imagine (ql:update-client) does more
> than I realized? Mebbe not.
>
> Anyway, back to work...
>
> -kt
>
> On Wed, Dec 27, 2017 at 10:30 AM, Zach Beane wrote:
>
>> I don't recommend using update-all-dists as the default. I
Thanks, I updated that section.
Zach
On Wed, Dec 27, 2017 at 10:40 AM, Luís Oliveira wrote:
> On Wed, Dec 27, 2017 at 3:30 PM, Zach Beane wrote:
> > I don't recommend using update-all-dists as the default. I prefer to
> > recommend (ql:update-dist "quicklisp"),
I don't recommend using update-all-dists as the default. I prefer to
recommend (ql:update-dist "quicklisp"), which updates all projects in the
quicklsp dist.
There can be multiple dists installed, and update-all-dists calls
update-dist on all of them.
See blog.quicklisp.org for news about what is
Erik Huelsmann writes:
> Hi Zach,
>
>
>> > But I agree that library quality / support are important parts of
>> > library discovery: if you don't know which ones are generally thought
>> > of as good, or which ones have an active support network, how can you
>> > ever choose between them? Solving
Nick Levine writes:
>> It doesn't seem so obvious as to where to find who might have
>> unpicked this already. Or find documentation behind a system and its
>> design intent. I.e. although perhaps nothing should be in Quicklisp
>> unless pure and solid, it can be quite a goose chase to try to hun
Faré writes:
> In ASDF 3.1.0.14, I introduced a macro :DBG (in uiop/utility.lisp).
> Yes, it's in the keyword package. Why?
> Because it's the one and only macro I want to be accessible from everywhere
> without a prefix, yet without modifying existing defpackage forms to make
> it accessible — b
Faré writes:
> Finally, if you're ready to accept SBCL only, Xach has something as
> part of buildapp.
> http://www.xach.com/lisp/buildapp/
Buildapp doesn't really do anything reusable for command-line arguments.
Robert Brown's "lisp-gflags" seems interesting.
Zach
___
Hi,
I've been trying to learn more about how Quicklisp has changed how
Common Lisp hackers work. When I posed the question on the Quicklisp
list, I got a response from Elliot Slaughter with a point that I hadn't
considered before:
> I think part of what makes Quicklisp successful (in my opinion)
Faré writes:
> What's so special about Lisp here? How do other languages do it?
./configure --with-foo=/bar/baz
Zach
___
pro mailing list
pro@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/pro
Faré writes:
>> I am looking for a portable way to specify configuration for a library
>> before/during loading with ASDF2. It would be sufficient if the user
>> could specify an ALIST (or something similar) somewhere and I could read/
>> use it when the library is loaded. Does ASDF2 have a "st
Raymond Wiker writes:
> On Jun 14, 2011, at 19:30 , Martin Simmons wrote:
>
>>> On Tue, 14 Jun 2011 09:32:50 -0400, Daniel Weinreb said:
>>>
>>> But Fare pointed out to me that being able to add generic functions
>>> specialized on these would be a good thing. This would mean making them us
Yakov Zaytsev writes:
> Hello, all
>
> Scott gave me a hint in previous topic and I've came across this
> interesting video by Daniel while googling.
>
> http://www.youtube.com/watch?v=xquJvmHF3S8
>
> There are many links to it on the Internet, but it's marked as
> "private" now. I was disappoint
Daniel Weinreb writes:
> However, in a situation I'm working on now, that
> doesn't work, because package X has
> (:import-from :y :a1 :a2), and the symbols
> :a1 and :a2 are not exported from :y. That
> is, X is exporting internal symbols of Y.
> This fails, because the symbols :a1 and :a2
> do
Alexandre Rademaker writes:
> Hello,
>
> Sorry if this list is not the best place to ask this question... Maybe
> we should create a newbie lisp list!
I don't think this is a good place for the question; there's a list for
slime questions, and lots of places to ask emacs questions.
> What is th
Nick Levine writes:
>We're getting there. See http://www.quicklisp.org/
>
>Especially, see http://www.quicklisp.org/beta/releases.html
>
> It doesn't say what any one of them do. There's no way (am I right?)
> to look up form what I want to do to what exists to do it.
Very true, and some
"Drew Csillag (sounds like cheese-log)" writes:
> Not to sound like I'm complaining (quicklisp is awesome btw), but if http://
> www.quicklisp.org/beta/releases.html had descriptions of what the packages
> actually did (or links to their respective homepage, or docstrings, or
> something), that w
Nick Levine writes:
>> I can't find any libraries.
>
> I think this is one of the most serious issues which is blocking the
> growth of lisp use. Speaking as someone who recently gave up trying to
> write a book on how to use CL's libraries: locating them and knowing
> in advance of downloading t
Faré writes:
> More importantly, we keep matching versions of swank and slime
> in our version control system. If you want to attach to a server,
> make sure you're using the appropriate SLIME. This way we could debug
> years-old production servers using obsolete versions of SWANK,
> if only we h
Alexandre Rademaker writes:
> This is an old issue! We now have quicklisp!
Quicklisp doesn't solve that particular problem. You can still get
different versions of slime between different people, even with
Quicklisp. (It just depends who updates when.)
Zach
Steve Morin writes:
> How to interact with a running lisp instance? I have been trying to figure
> this out. I know this is being done with slime. Does any one have any good
> pointer on this. I am thinking of writing a web application and would like to
> be able to update it on the fly for u
21 matches
Mail list logo
