> The "[email protected]" on "pkgs.racket-lang.org" means that third party
> package authors are effectively credited less than before. Perhaps names
> should be displayed instead?
Where do you see this? I see email addresses at places like
- https://pkgs.racket-lang.org/
- https://pkgd.racket
Many good ideas here! A couple suggestions:
1. I recommend not assuming screen sizes.
Right-click, choose Inspect Element, and click the little mobile icon.
Try various sizes, from a little mobile phone on up to an iPad. (This
sort of tool is available in Firefox and Chrome.)
The current experi
Sam Tobin-Hochstadt writes:
> I just tested this, with the subject "CI improved for Racket" (from
> April, on this list). For me, the Google Groups archive entry is the
> first result for that query, when quoted.
I see that reuslt, too. (I thought the difference might arise from using
Google se
hypothesis might be right. :/
>
> ~Leif Andersen
>
>
> On Thu, Mar 22, 2018 at 4:16 PM, Greg Hendershott
> wrote:
>> FWIW it works for me, too.
>>
>> Couple random ideas:
>>
>> 1. What if you try using https instead of http?
>>
>> 2. From
FWIW it works for me, too.
Couple random ideas:
1. What if you try using https instead of http?
2. From the headers, I see Cloudflare is involved. Although I don't
know much about it, I think part of what they do is try to prevent
DDOS attacks. Is there any chance they put your network in a pena
p.s. Although I'd be fine using a mailing list, I could see using
Slack for this? IIUC, if you don't pay for it, it's archived only up
to the X most-recent messages. But maybe that's still too much
retention for people.
--
You received this message because you are subscribed to the Google Groups
I'd sign up and participate, whether it were wide-open like
racket-users or something invite-only and "private"-ish.
For a few months now, I've had a small, (barely) commercial web app
that is all Racket plus Postgres hosted on AWS and using Stripe:
https://deals.extramaze.com/
I don't have a
On Thu, Nov 12, 2015 at 6:02 PM, Thomas Lynch
wrote:
> It is not the very nature of errors that we do not expect them, and do not
> predict them with specificity, so it is incumbant upon racket to give
> location infomration with errors, rather than for the programmer to do so?
> Or am I missing s
On Fri, Oct 30, 2015 at 7:55 AM, Robby Findler
wrote:
> Hi Thomas: you may wish to use errortrace to get more source locations
> for error messages. It is enabled by default in DrRacket, but you have
> to load it explicitly when you are working with the command-line
> racket. Probably racket-mode
Oh then maybe I'm misunderstanding "deprecated".
I was thinking of it from the narrow/selfish point of view of a (new
system) package developer. In that system, deprecated can't mean "will
be removed soon", because you can't ever remove things from a package.
(Packages are supposed to be backward
Only recently did I learn about and start to use `history`:
http://docs.racket-lang.org/scribble/Version_History.html
This could be used as-is with the `#:changed` clause:
@history[#:changed "1.7"]{Deprecated. Instead use @racket[shiny-thing].}
But now that you mention it, a new explicit `#
> You may notice that I only mention define-syntax-rule and
> syntax-parse. That was on purpose.
Aha. Nice.
> I read this as a suggestion that I
> should replace define-syntax-rule with define-simple-macro.
Yes, after expanding my ramble to actionable primitives, that is
really all that remains.
This is wonderful!!
p.s. Opinion ahead:
Someday soon syntax/parse/* (including define-simple-macro) should be
promoted (in both senses of that word) as "the" Racket macro system.
As in, if you only learn about one, at first, you learn about that.
With syntax-case, syntax-rules, etc. being "depr
I think it would be a big improvement over the status quo, even if the
only rule were dumb, simple equality: "Check whether all these
packages use the exact same license."
Even just that would probably help most of the people most of the time?
Mixing licenses, yeah I don't really know. I want to
The following may seem like a random feature request. But it does
relate to dependencies and backward compatibility. (And as long as
people are talking about enhancing, and/or layering something on top
of, the existing package system)
Licenses.
Licenses determine what packages you may depend
What happens to the version in info.rkt?
Does a foo2 package have version "2.x" in info.rkt?
Or does it get reset to "1.x"? (On the theory that there's no such
thing as a backward-incompatible version of a package, just a new
package. And on the assumption a major version change implies
backward
I don't mean to discourage you from splitting.
I'm just not sure it's worthwhile for most packages. As a result, I
wouldn't want people to feel it's generally expected.
(I wouldn't want that to discourage someone from making a package at
all. Or to divert too much time from other ways to make the
> Now another point of confusion, setup made a directory called 'compiled' so
> I gather raco setup is compiling modules into the compiled directory. Will
> raco setup do this in an incremental fashion. Say if I mod one module then
> run raco setup, will it just compile the one? Or will all the
> Exposing submodules is becoming more prevalent in Racket,
That's interesting, I hadn't noticed this trend yet, what are some examples?
I feel like the downside you mentioned is significant. I guess instead
I wish it were possible for this to be totally up to the implementor
-- and not require
p.s. I guess a third way is to always use prefix-in, which IIUC is the
convention in Clojure. (I feel having prefixes on everything is
distracting, but, it's another possible way.)
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscr
If I understand correctly, the way to silence the warning would be to
change the require to use only-in or except-in?
So in a sense, the new behavior is a sort of implicit transformation
of (require x) => (require (except-in x (all-defined-here))) [where
"(all-defined-here)" is something I just ma
> yes geiser in emacs .. I better move to Dr Racket IDE so I'm in the same
> boat with most everyone else.
Actually, Matthew and I were suggesting that you try using
command-line Racket with xrepl.
For example:
$ cat file.rkt
#lang racket
(define x 10)
$ racket
Welcome to Racket v6.1.1.
> (requ
> As you observe, `racket` doesn't track changes to files, and `require`
> doesn't re-load a module that it has previously loaded (even if the
> module's source changed).
>
> You might want to try a tool like `xrepl`, which supports re-loading
> changed modules:
>
> http://docs.racket-lang.org/xr
I like this idea, too.
I think the existing syntax/parse documentation is a good example of
how this can work well. It has an excellent introduction, numerous
examples, and then it gets into explicit reference material. It seems
natural to have this grouped together, in that order, and it's very
Is there any chance this is related to using pretty-print-hook and
pretty-print-size-hook?
https://github.com/racket/drracket/commit/89df6b8cca0f862e52d22db1da733524ebf95d80
That change is very recent; maybe more recent than what John is using.
--
You received this message because you are su
I also found this confusing when becoming familiar with Racket.
1. I wonder if some diagram(s) could help organize this cluster of
concepts with has-a and is-a(-kind-of) relations?
2.
>> So trying to put this together. In racket then, there is a unique special
>> place called "The Library". On
> For the actual commands, see
>
>
> http://www.greghendershott.com/2013/04/a-guide-for-infrequent-contributors-to-racket.html
>
> I am not 100% sure that everything is up-to-date though.
I _believe_ that's still accurate for the (now much smaller) main
plt/racket repo.
But I haven't yet gotten h
27 matches
Mail list logo
