At Wed, 31 Jul 2013 15:02:34 -0400, Tony Garnock-Jones wrote:
> > Finally, there's the question of inference that `raco pkg install' and
> > other tools perform on a string that represents a package source.
> > Keeping the package-name grammar simple makes that inference more
> > predictable.
>
>
On 07/26/2013 03:39 PM, Ryan Culpepper wrote:
* Neil Toronto
- Plot Tests
- Images Tests
- Inspect icons
- Math tests
All pass.
_
Racket Developers list:
http://lists.racket-lang.org/dev
I like this change; thanks for suggesting it!
Robby
On Wed, Jul 31, 2013 at 1:38 PM, Tony Garnock-Jones wrote:
> On 07/31/2013 02:24 PM, Matthew Flatt wrote:
>
>> I think it often
>> makes sense for command-line tools to have weird rules[*],
>>
>
> I agree with you. UIs have to be humane and er
On 07/31/2013 02:42 PM, Matthew Flatt wrote:
Package names show up in all sorts of other contexts, too, such as
filesystem paths.
Sure, but if there's something that won't work as a filesystem path, the
developer finds that out awfully quickly.
Note that the programming language in which we
At Wed, 31 Jul 2013 14:17:18 -0400, Tony Garnock-Jones wrote:
> On 07/31/2013 02:11 PM, Jay McCarthy wrote:
> > The restriction is primarily because they appear in URLs as single
> > path segments.
>
> Could we then widen the restriction to be [-A-Za-z0-9._~!$&'()*+,;=],
> following http://tools.
On 07/31/2013 02:24 PM, Matthew Flatt wrote:
I think it often
makes sense for command-line tools to have weird rules[*],
I agree with you. UIs have to be humane and ergonomic for our weak,
squishy meat-bodies to cope. (Though of course the underlying model has
to be sensible too ;-) )
espe
At Wed, 31 Jul 2013 13:47:41 -0400, Tony Garnock-Jones wrote:
> When I have a directory foo/, containing a single-collect package, and I
> install it with "raco pkg install foo/", it seems to copy the contents
> of the directory, meaning local edits are not found by the system.
> Instead I have
On 07/31/2013 02:11 PM, Jay McCarthy wrote:
The restriction is primarily because they appear in URLs as single
path segments.
Could we then widen the restriction to be [-A-Za-z0-9._~!$&'()*+,;=],
following http://tools.ietf.org/html/rfc3986#section-3.3 (but
disallowing percent-escaping)?
I
The restriction is primarily because they appear in URLs as single
path segments.
Jay
On Wed, Jul 31, 2013 at 11:50 AM, Tony Garnock-Jones wrote:
> Hi all,
>
> Package names are restricted as follows, per the documentation:
>
> "a package name — a string made of the characters a through z, A thr
Hi all,
Package names are restricted as follows, per the documentation:
"a package name — a string made of the characters a through z, A through
Z, 0 through 9, _, and -."
Why does this restriction exist? Programmers never see package names
when using (require); Operators see package names o
Hi all,
When I have a directory foo/, containing a single-collect package, and I
install it with "raco pkg install foo/", it seems to copy the contents
of the directory, meaning local edits are not found by the system.
Instead I have to "raco pkg install --link foo/".
I would prefer it if "-
On 26 Jul 2013, at 22:39, Ryan Culpepper wrote:
> * Kathy Gray
> - Test Engine Tests
Done
_
Racket Developers list:
http://lists.racket-lang.org/dev
12 matches
Mail list logo