When I went to rebuild the latest source this morning, I got the
following error from 'make install':
racket/racket3m -X "/home/samth/sw/plt/collects" -N "raco setup" -l- setup
raco setup: bootstrapping from source...
/home/samth/sw/plt/collects/unstable/private/compiled/expand_ss.zo::0:
read (com
I saw this problem yesterday, too, but I thought I had fixed it.
For me, commit fe60da72c8d6525954f965144ea4dc49b6cf40a4 created the
problem. Commit e78b5d722eb7396478cd8558b2b9786ce9c52537 fixed it.
If you already have the latter, though, there must be some other problem.
At Tue, 29 Jun 2010 09:
On Tue, Jun 29, 2010 at 9:46 AM, Matthew Flatt wrote:
> I saw this problem yesterday, too, but I thought I had fixed it.
>
> For me, commit fe60da72c8d6525954f965144ea4dc49b6cf40a4 created the
> problem. Commit e78b5d722eb7396478cd8558b2b9786ce9c52537 fixed it.
> If you already have the latter, th
At Tue, 29 Jun 2010 09:40:54 -0400, Sam Tobin-Hochstadt wrote:
> When I went to rebuild the latest source this morning, I got the
> following error from 'make install':
>
> racket/racket3m -X "/home/samth/sw/plt/collects" -N "raco setup" -l- setup
> raco setup: bootstrapping from source...
> /home
On Tue, Jun 29, 2010 at 11:11 AM, Matthew Flatt wrote:
> At Tue, 29 Jun 2010 09:40:54 -0400, Sam Tobin-Hochstadt wrote:
>> When I went to rebuild the latest source this morning, I got the
>> following error from 'make install':
>>
>> racket/racket3m -X "/home/samth/sw/plt/collects" -N "raco setup"
I haven't been able to replicate the problem, so I'm stumped. For now,
it's probably best to just delete .zo files, and we'll watch out for
the problem on the next version change.
_
For list-related administrative tasks:
http://lists.racket-lang.
On Sat, Jun 26, 2010 at 2:30 PM, Robby Findler
wrote:
>
> Saving comment boxes requires the file to be saved in our fancy file
> format and it adds a fair amount of overhead to do that.
My impression is that all overhead would pretty much disappear if the
binary format was gzipped.
I would like
Some kind of compression could help, but at the moment the format is
designed so that if someone were to copy and paste the contents of a
file into an email window and send it to us, we could still use it
(wierd linebreaks and all) and even if it gets truncated there is some
hope of recovering some
Part of the need for this is the bug report system doesn't allow
attachments, which I have sometimes sorely missed. Of course, it isnt the
only usecase.
On Jun 29, 2010 1:05 PM, "Robby Findler"
wrote:
Some kind of compression could help, but at the moment the format is
designed so that if someo
gzip compression (from file/gzip) followed by mime encoding (from
net/base64) results in an average size reduction of 74%, on average,
across 600 assignment submissions that were saved in Racket's "binary"
format.
On Tue, Jun 29, 2010 at 1:27 PM, Shriram Krishnamurthi
wrote:
> Part of the need
I've been kinda hoping that someday the "binary" format is turned into a
plain text format that's usable in any editor or other tool.
For example, DrRacket comment boxes could be stored as normal Scheme
comments with a cookie token in the comment that is a hint to DrRacket
to treat it as a com
Today, I've started seeing output from 'mzc' like the following:
[sa...@punge:~/sw/plt/collects/tests/typed-scheme (master) plt] mzc -kv main.rkt
mzc v5.0.0.2 [3m], Copyright (c) 2004-2010 PLT Scheme Inc.
"main.rkt":
making "/home/samth/sw/plt/collects/tests/typed-scheme/main.rkt"
making "/hom
On Jun 29, Shriram Krishnamurthi wrote:
> Part of the need for this is the bug report system doesn't allow
> attachments, which I have sometimes sorely missed. Of course, it
> isnt the only usecase.
1. The "thanks" replies to bug submitters now have a reply-to header
that should make it easy t
> 1. The "thanks" replies to bug submitters now have a reply-to header
> that should make it easy to post a reply with an attachement.
But there are no instructions in the bug submission form to this
effect: "if you wish to attach a file, please send it using your mail
program in response to the
On Jun 29, Shriram Krishnamurthi wrote:
> > 1. The "thanks" replies to bug submitters now have a reply-to
> >header that should make it easy to post a reply with an
> >attachement.
>
> But there are no instructions in the bug submission form to this
> effect: "if you wish to attach a file,
Yes, #2 would be ideal. But until then, apparently, I was not clear.
There are no instructions *in the bug submission form*: "if you wish
to attach a file, please send it using your mail program in response
to the acknowledgement mail you receive".
Receiving the instructions AFTER you have submi
Eli Barzilay wrote at 06/29/2010 04:46 PM:
2. Gnats *does* know how to deal with attachements. The problem is
that our cgi library cannot handle a multipart/form-data encoding.
(If you convince the author to add support for that, I'll do the
rest and add a file attachement option to the
On Jun 29, Shriram Krishnamurthi wrote:
> Yes, #2 would be ideal. But until then, apparently, I was not
> clear.
>
> There are no instructions *in the bug submission form*: "if you wish
> to attach a file, please send it using your mail program in response
> to the acknowledgement mail you receiv
The Web server implements the multipart/form-data reading as well.
Jay
On Tue, Jun 29, 2010 at 3:07 PM, Neil Van Dyke wrote:
> Eli Barzilay wrote at 06/29/2010 04:46 PM:
>>
>> 2. Gnats *does* know how to deal with attachements. The problem is
>> that our cgi library cannot handle a multipart/
Either way, what I need is some way to pull out the bindings (with the
attachment) from a cgi script in some form. Once I can do that, I'll
be able to add the attachement field.
On Jun 29, Jay McCarthy wrote:
> The Web server implements the multipart/form-data reading as well.
>
> Jay
>
> On T
20 matches
Mail list logo