Christopher Lemmer Webber wrote on 9/19/18 8:15 AM:
#:keyword matches other Schemes I've used.
If other Scheme precedent is a factor... Before Racket (PLT Scheme) did
it the way it does, I only recall Guile supporting that way. I recall
every other implementation doing it differently than th
I was specifying a collection, and `--tidy` did the trick! Thanks.
-Philip
On Wed, Sep 19, 2018 at 1:18 PM Matthew Flatt wrote:
> At Wed, 19 Sep 2018 13:12:58 -0500, Philip McGrath wrote:
> > I've renamed a Scribble file documenting a package, and now I'm getting
> > warnings from `raco setup`
At Wed, 19 Sep 2018 13:12:58 -0500, Philip McGrath wrote:
> I've renamed a Scribble file documenting a package, and now I'm getting
> warnings from `raco setup` of the form: "WARNING: duplicate tag:" [some tag
> from this document] "in: in:" [the document I just renamed]. Is
> there a cache somewh
I've renamed a Scribble file documenting a package, and now I'm getting
warnings from `raco setup` of the form: "WARNING: duplicate tag:" [some tag
from this document] "in: in:" [the document I just renamed]. Is
there a cache somewhere that I need to delete? I've already tried using the
`--doc-ind
On 9/19/2018 11:31 AM, Alexis King wrote:
I’m surprised this hasn’t been discussed yet:
I'm not. Racket (and contributions) has so many nifty features that it
could take years to browse all the documentation.
On a related topic, the persistent problem with keyword search engines
is: if y
I’m surprised this hasn’t been discussed yet: Alex Knauth has a set of
meta-languages that add support for :kw or kw: syntax for keywords to arbitrary
#langs (assuming they use readtables).
http://docs.racket-lang.org/colon-kw/index.html
Whether or not actually using these meta-languages is
For whatever it's worth, I don't care about this issue for it's own sake
and would prefer that it not be implemented because (a) I would see it as a
waste of resources, (b) it would have unpredictable effects on existing
code, and (c) it means one more thing to keep in mind when reading other
peopl
Hm. As to the stretching -- sounds like there may be a significant
difference between Racket 6.11 and 7, or else a significant different
between Racket's drawing on Windows and Mac. I'll try it under 7.
As to the failure to touch, yes. That gap is the issue, although on 6.11 /
Mac it's very pro
On 9/19/2018 8:29 AM, Laurent wrote:
I don't mind `#:`, but I'd prefer to write `[#:foo 5]` rather than
`#:foo [foo 5]`, that is, I don't like the repetition of the name (I
first came to Racket precisely to avoid repeating code).
When I expressed that a few years ago, I was told it would be
Hi David,
I am running your example code on a Windows machine with Racket 7.0, and
the buttons do stretch vertically and horizontally when I resize the
window. There is a small gap between the buttons, but I think this is how
the native buttons are drawn. Is the problem that there is this ga
I don't mind `#:`, but I'd prefer to write `[#:foo 5]` rather than `#:foo
[foo 5]`, that is, I don't like the repetition of the name (I first came to
Racket precisely to avoid repeating code).
When I expressed that a few years ago, I was told it would be unlikely to
change in the future though, wh
I am wary of this. I really don't have a strong preference either way,
my suspicion is it's mostly "what did you become famliar with initially"
kind of thing. :keyword is more Common Lisp'ish, #:keyword matches
other Schemes I've used.
But:
- I'd rather not have *two* keyword syntaxes in Racket
I recall multiple discussions about colon keywords over the many years,
but (it's 5am) temporarily forgot that Jay did a poll 3 years ago.
Jay's results summary quoted and linked below.
I think 3 years means it's time to go from these results, to either
changing Racket, or expecting "preferenc
On 9/19/2018 4:56 AM, Neil Van Dyke wrote:
Currently, in main Racket reader, `#:` starts a keyword, as in `#:foo`.
Who on this email list would also like (or not like) `:` to start a
keyword, as in `:foo`?
And, if you want the reader to also support `:foo`, would you want the
writer to def
Currently, in main Racket reader, `#:` starts a keyword, as in `#:foo`.
Who on this email list would also like (or not like) `:` to start a
keyword, as in `:foo`?
And, if you want the reader to also support `:foo`, would you want the
writer to default to writing `:foo` rather than `#:foo` (an
15 matches
Mail list logo
