I have some scripts that still use planet. I use development links as
a substitute for a local PLaneT-like capability and have scripts to do
this for me. Some of these are on production servers. I would create
an alias for it anyway, but would rather it stayed as is.
Doug
On Sun, Jul 29, 2012 at
It will stay 'as is' for this release. But we intend to deprecate 'planet' so
that people begin to switch to 'raco planet'. -- Matthias
On Jul 30, 2012, at 9:43 AM, Doug Williams wrote:
> I have some scripts that still use planet. I use development links as
> a substitute for a local PLaneT-l
Thanks! Inspired by this information, I've managed to produce a
consistent crash on my machine by attempting to render the "plot"
documentation concurrently in three places.
My guess is that it's a thread-safety problem in Cairo. That is, Cairo
is supposed to be thread-safe, but maybe we're trippi
At Fri, 20 Jul 2012 16:33:54 -0400, Vincent St-Amour wrote:
> How about having a `compatibility' collect, which would include this and
> things like `racket/package' (compatibility with Chez) and `racket/mpair'
> (compatibility with Scheme)? It would be harder to confuse these things
> with blessed
At Mon, 30 Jul 2012 13:10:28 -0600,
Matthew Flatt wrote:
>
> At Fri, 20 Jul 2012 16:33:54 -0400, Vincent St-Amour wrote:
> > How about having a `compatibility' collect, which would include this and
> > things like `racket/package' (compatibility with Chez) and `racket/mpair'
> > (compatibility wit
On Jul 30, 2012, at 3:52 PM, Vincent St-Amour wrote:
> The main advantage (IMO) of having, say, mutable lists in
> `compatibility' is that searching the docs points there instead of to
> `racket'. This makes it clear that they are not a blessed Racket
> feature. This is (IMO) the main point of th
At Mon, 30 Jul 2012 15:52:52 -0400, Vincent St-Amour wrote:
> The main advantage (IMO) of having, say, mutable lists in
> `compatibility' is that searching the docs points there instead of to
> `racket'. This makes it clear that they are not a blessed Racket
> feature. This is (IMO) the main point
DrDr now has green buttons to go between times the file's output has
changed. Hopefully this will help you find problematic commits easier.
Jay
--
Jay McCarthy
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay
"The glory of God is Intelligence" - D&C 93
At Mon, 30 Jul 2012 16:00:12 -0400,
Matthias Felleisen wrote:
> Having said that, I would like to propose that we COPY
> files/subcollections from racket/ to compatibility/ (and keep them in
> sync) if we wish to indicate that they are not really rackety.
Assuming you mean keeping the same interfa
At Mon, 30 Jul 2012 14:52:06 -0600,
Matthew Flatt wrote:
> At Mon, 30 Jul 2012 16:00:12 -0400, Matthias Felleisen wrote:
> > I fully and enthusiastically agree with this perspective but I don't think
> > this
> > is high on our list of things to do.
> >
> > When we consider such moves, we shoul
On Jul 30, 2012, at 5:42 PM, Jay McCarthy wrote:
> DrDr now has green buttons to go between times the file's output has
> changed. Hopefully this will help you find problematic commits easier.
Here's what I think is a super-minor request. When I view the diff of two DrDr
outputs; say:
http://d
Hi. I've a question about --enable-backtrace in the configure step. Is
it useful for the users or only is useful for the racket developers?.
This option affect to the performance of racket?.
I'm not a scheme/racket developer. I'm just the racket maintainer on
OpenBSD [1]. I'm using this configure
12 matches
Mail list logo
