Hi Jay,
Have not been following Racket development too closely lately, but
perhaps you might find this helpful?
http://planet.racket-lang.org/display.ss?package=while-loop.plt&owner=dyoo
_
Racket Developers list:
http://lists.racket-lang.org/dev
On Fri, Jun 27, 2014 at 8:40 PM, J. Ian Johnson wrote:
> One is that #:when in for-clauses allows you to skip iterations, but you want
> it in the body. This is a cosmetic difference that you can get around by
> doing #:when (begin imperative-stuff-before-guard guard). If you want ecs to
> esca
On Jun 27, 2014, at 5:29 PM, Robby Findler wrote:
> I've generally tried to keep the image arguments last to make nested
> compositions of functions easier to read. Since we have to keep frame
> for backwards compatibilities reasons regardless, I don't think we
> need to worry about making color
There are a couple issues here,
One is that #:when in for-clauses allows you to skip iterations, but you want
it in the body. This is a cosmetic difference that you can get around by doing
#:when (begin imperative-stuff-before-guard guard). If you want ecs to escape
an entire for loop, that's wh
PS: Sam, were you able to produce two pdfs (via scribble --dvipdf and
--pdf) and compare their output on your machine? Do you have
screenshots to share?
Robby
_
Racket Developers list:
http://lists.racket-lang.org/dev
I've generally tried to keep the image arguments last to make nested
compositions of functions easier to read. Since we have to keep frame
for backwards compatibilities reasons regardless, I don't think we
need to worry about making color-frame's color argument optional.
Robby
On Fri, Jun 27, 201
I am not understanding your question either but the two screenshots are
using the same fonts. Just one is being rendered poorly for unknown
reasons.
Robby
On Saturday, June 28, 2014, Sam Tobin-Hochstadt
wrote:
> On Fri, Jun 27, 2014 at 2:23 PM, Matthew Flatt > wrote:
> > At Fri, 27 Jun 2014 1
I've been converting a bunch of Python to Racket lately, and I have a
lot of loops that use break and continue. I end up turning them into:
(let/ec break
(for (...)
(let/ec continue
; do some work
(when this-iteration-isn't-what-i-want
(continue))
; do more expensiv
On Fri, Jun 27, 2014 at 2:23 PM, Matthew Flatt wrote:
> At Fri, 27 Jun 2014 13:43:46 -0400, Sam Tobin-Hochstadt wrote:
>> On Fri, Jun 27, 2014 at 12:30 PM, Matthew Flatt wrote:
>> > At Fri, 27 Jun 2014 11:56:39 -0400, Sam Tobin-Hochstadt wrote:
>> >> On Fri, Jun 27, 2014 at 11:45 AM, Matthew Flat
At Fri, 27 Jun 2014 13:43:46 -0400, Sam Tobin-Hochstadt wrote:
> On Fri, Jun 27, 2014 at 12:30 PM, Matthew Flatt wrote:
> > At Fri, 27 Jun 2014 11:56:39 -0400, Sam Tobin-Hochstadt wrote:
> >> On Fri, Jun 27, 2014 at 11:45 AM, Matthew Flatt wrote:
> >> > For some reason, the way that PDF fragments
On Fri, Jun 27, 2014 at 12:30 PM, Matthew Flatt wrote:
> At Fri, 27 Jun 2014 11:56:39 -0400, Sam Tobin-Hochstadt wrote:
>> On Fri, Jun 27, 2014 at 11:45 AM, Matthew Flatt wrote:
>> > For some reason, the way that PDF fragments are pulled in by `pdflatex`
>> > makes the fragments look worse in som
On Jun 22, 2014, at 9:42 PM, Robby Findler wrote:
> Thanks! I've added these two functions.
>
> Robby
>
> On Sun, Jun 22, 2014 at 12:26 PM, Kevin Forchione wrote:
>>
>> On Jun 21, 2014, at 5:02 PM, Robby Findler
>> wrote:
>>
>> What do you think about a variant on center-crop called crop/a
At Fri, 27 Jun 2014 11:56:39 -0400, Sam Tobin-Hochstadt wrote:
> On Fri, Jun 27, 2014 at 11:45 AM, Matthew Flatt wrote:
> > For some reason, the way that PDF fragments are pulled in by `pdflatex`
> > makes the fragments look worse in some PDF viewers/machines than the
> > way that PS fragments are
On Fri, Jun 27, 2014 at 11:45 AM, Matthew Flatt wrote:
> I will push a repair for that soon.
>
> Just to clarify a little, `--pdf` files generated on Robby's machine
> look fine in Preview on my machine, and `--pdf` files generated on my
> machine look bad in Preview on Robby's machine. The machin
I will push a repair for that soon.
Just to clarify a little, `--pdf` files generated on Robby's machine
look fine in Preview on my machine, and `--pdf` files generated on my
machine look bad in Preview on Robby's machine. The machine dependence
is in how the output is viewed, and not what is gene
I'm trying to determine how different they look on my machine, but
unfortunately the two processes put the lines at different places on
the page. Do you have an easy way to control that?
Sam
On Fri, Jun 27, 2014 at 10:47 AM, Robby Findler
wrote:
> No, the lower-down aspect is actually something
No, the lower-down aspect is actually something else. The "x" and the
"y" in the sans serif font on that line and the big "f" on the line
above are from picts. The other characters on those lines are directly
written in the latex code. The grammar is also a pict. The picts look
worse in one screen
And the one with the second x in the bottom line lower down is the one
that's from --pdf and is not intended? Are there other differences
between the pictures?
Sam
On Fri, Jun 27, 2014 at 9:02 AM, Robby Findler
wrote:
> On Fri, Jun 27, 2014 at 7:59 AM, Sam Tobin-Hochstadt
> wrote:
>> Is the pro
On Fri, Jun 27, 2014 at 7:59 AM, Sam Tobin-Hochstadt
wrote:
> Is the program in the commit message what I should try to see the difference?
It looks different for me, yes. I'm attaching two screenshots for the
difference I see between --pdf and --dvipdf.
Robby
_
Racket
Is the program in the commit message what I should try to see the difference?
Sam
On Fri, Jun 27, 2014 at 8:57 AM, Robby Findler
wrote:
> I can't explain, no. The pdfs don't actually seem to _be_ worse when
> printing, so this pathway just seems to encourage viewers somehow.
>
> But apparently i
I can't explain, no. The pdfs don't actually seem to _be_ worse when
printing, so this pathway just seems to encourage viewers somehow.
But apparently if you have a retina mac, this flag isn't necessary.
Robby
On Fri, Jun 27, 2014 at 7:22 AM, Sam Tobin-Hochstadt
wrote:
> On Fri, Jun 27, 2014 at
On Fri, Jun 27, 2014 at 4:30 AM, wrote:
>
>
> 5280395 Robby Findler 2014-06-27 03:25
> :
> | add the --dvipdf flag to scribble
> |
> | This adds a new back-end pipeline for generating pdf to
> | scribble, with the hope that included picts (e.g., those
> | generated by Redex) will look better whe
22 matches
Mail list logo
