I understand that he new site is unusable if tools do not get the expected
input. Sorry for the inconvenience. I was just not aware of this as Pharo uses
the raw format.
I had to set up a CGI to produce an html listing from the raw file.
It should now be ok. Could you tell me if it works in
Christophe,
I appreciate your effort, but I assume that you aren't finished yet?
When I use the url from your message I get a `Not Found` error (note
that I explicitly included a trailing slash in the url):
This is a bug (or omission) as well, since other Monticello sites
produce the
There is a new Pharo build available!
The status of the build #628 was: SUCCESS.
The Pull Request #7192 was integrated: "CompiledMethod-isFaulty"
Pull request url: https://github.com/pharo-project/pharo/pull/7192
Issue Url: https://github.com/pharo-project/pharo/issues/CompiledMethod
Build
I got it. To determine the range of the selection the tools now use the AST.
So this is fair.
S
> On 27 Aug 2020, at 20:51, Martin McClure wrote:
>
> This is not definite knowledge, but some code I was digging through yesterday
> suggests that it *might* be for syntax highlighting of the
There is a new Pharo build available!
The status of the build #627 was: FAILURE.
The Pull Request #7120 was integrated: "Missing offsets when mapping
ast<->bytecode and when the first node is a fullblock"
Pull request url: https://github.com/pharo-project/pharo/pull/7120
Issue Url:
There is a new Pharo build available!
The status of the build #626 was: FAILURE.
The Pull Request #7195 was integrated: "sendsToSuper-CleanBlockClosure"
Pull request url: https://github.com/pharo-project/pharo/pull/7195
Issue Url: https://github.com/pharo-project/pharo/issues/sendsToSuper
There is a new Pharo build available!
The status of the build #625 was: FAILURE.
The Pull Request #7189 was integrated: "Cleanup-reflective-pragma"
Pull request url: https://github.com/pharo-project/pharo/pull/7189
Issue Url: https://github.com/pharo-project/pharo/issues/Cleanup
Build Url:
There is a new Pharo build available!
The status of the build #624 was: FAILURE.
The Pull Request #7197 was integrated:
"7196-IconStyler-is-missing-visitEnglobingErrorNode"
Pull request url: https://github.com/pharo-project/pharo/pull/7197
Issue Url:
> Le 28 août 2020 à 10:15, Sven Van Caekenberghe a écrit :
>
>
>
>> On 28 Aug 2020, at 10:13, Christophe Demarey
>> wrote:
>>
>> Smalltalkhub is now to able to distinguish between raw and not raw mcz
>> listing requests.
>> Ex:
>>
> On 28 Aug 2020, at 10:13, Christophe Demarey
> wrote:
>
> Smalltalkhub is now to able to distinguish between raw and not raw mcz
> listing requests.
> Ex:
> http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw
>
Smalltalkhub is now to able to distinguish between raw and not raw mcz listing
requests.
Ex:
http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main?format=raw
http://smalltalkhub.com/mc/Seaside/Seaside30LGPL/main/
I already use the apache directory index for another page so I
Hi Dale,
I would not call it a bug but an omission ;)
It is hard to guess that a tool is scraping an html page to get data.
Nevertheless, I will take a look today to find a solution for Glass to work
again with smalltalkhub.
Could you tell me what is the expected output? What is the html
12 matches
Mail list logo
