Re: [racket-users] Package documentation link issue

On Wed, Apr 12, 2017 at 2:29 PM, Matthew Flatt wrote: > At Wed, 12 Apr 2017 14:17:39 -0400, Greg Hendershott wrote: >> On Tue, Apr 11, 2017 at 7:16 PM, Matthew Flatt wrote: >> > It's a bug in the pkg-build process, and I should have it fixed for the >> >

Re: [racket-users] Package documentation link issue

At Wed, 12 Apr 2017 14:17:39 -0400, Greg Hendershott wrote: > On Tue, Apr 11, 2017 at 7:16 PM, Matthew Flatt wrote: > > It's a bug in the pkg-build process, and I should have it fixed for the > > next build. > > It looks like that didn't run this (Wed) morning? The machine

Re: [racket-users] Package documentation link issue

On Tue, Apr 11, 2017 at 7:16 PM, Matthew Flatt wrote: > It's a bug in the pkg-build process, and I should have it fixed for the > next build. It looks like that didn't run this (Wed) morning? I only noticed and mention this because Tue evening I updated Frog. And this:

Re: [racket-users] Package documentation link issue

It's a bug in the pkg-build process, and I should have it fixed for the next build. At Tue, 11 Apr 2017 18:11:08 -0400, Tony Garnock-Jones wrote: > Thanks, Philip -- that could well be a bug in the catalog UI. I can't > check it out until after the OOPSLA deadline, so I've filed >

Re: [racket-users] Package documentation link issue

Thanks, Philip -- that could well be a bug in the catalog UI. I can't check it out until after the OOPSLA deadline, so I've filed https://github.com/tonyg/racket-pkg-website/issues/42 to keep track of it until then. Regards, Tony On 04/11/2017 01:21 PM, Philip McGrath wrote: > I recently

[racket-users] Package documentation link issue

I recently posted a package "recaptcha", and I noticed a problem with the documentation link that I'm not sure how to fix. Google stylizes the name as reCAPTCHA, and I've capitalized it that way in the title of the documentation, but I called the actual package "recaptcha" so that you can "raco