Re: It's time to use "use v6.c"

2016-02-07 Thread Steve Mynott
The windows p6doc fix at http://perl6.org/downloads/ has been updated. On 6 February 2016 at 21:17, Steve Mynott wrote: > Are you using windows? > > From the recently updated http://perl6.org/downloads/ > > "p6doc was broken on Windows. Fix is to, with Git in the %PATH%,

Re: It's time to use "use v6.c"

2016-02-07 Thread yary
"panda --force install p6doc" fixed it for me!

Re: It's time to use "use v6.c"

2016-02-06 Thread Darren Duncan
On 2016-02-06 11:35 AM, Brandon Allbery wrote: On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 study group, and a helpful neighbor asked me to start up p6doc. This is something of an edge case. It is

Re: It's time to use "use v6.c"

2016-02-06 Thread Brandon Allbery
On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: > this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 > study group, and a helpful neighbor asked me to start up p6doc. > This is something of an edge case. It is reasonable for stuff that is supposed to ship *with*

Re: It's time to use "use v6.c"

2016-02-06 Thread Steve Mynott
Are you using windows? >From the recently updated http://perl6.org/downloads/ "p6doc was broken on Windows. Fix is to, with Git in the %PATH%, "panda --force install p6doc" and delete C:\rakudo\bin\p6doc.bat." S On 6 February 2016 at 19:30, yary wrote: > this morning I