[Pharo-dev] [Pharo 9.0] Build #259: #5952-PharoEnvironmentHelp-outdated

There is a new Pharo build available! The status of the build #259 was: FAILURE. The Pull Request #6225 was integrated: "#5952-PharoEnvironmentHelp-outdated" Pull request url: https://github.com/pharo-project/pharo/pull/6225 Issue Url: https://github.com/pharo-project/pharo/issues/5952 Build

[Pharo-dev] [Pharo 9.0] Build #258: 6165-Spotter-stopped-to-react-on-full-method-name

There is a new Pharo build available! The status of the build #258 was: FAILURE. The Pull Request #6226 was integrated: "6165-Spotter-stopped-to-react-on-full-method-name" Pull request url: https://github.com/pharo-project/pharo/pull/6226 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #257: ReBasicTreeRule-Cleanup

There is a new Pharo build available! The status of the build #257 was: FAILURE. The Pull Request #6227 was integrated: "ReBasicTreeRule-Cleanup" Pull request url: https://github.com/pharo-project/pharo/pull/6227 Issue Url: https://github.com/pharo-project/pharo/issues/ReBasicTreeRule Build

[Pharo-dev] [Pharo 9.0] Build #256: 6184-Cursor-doesnt-blink-in-the-inspector

There is a new Pharo build available! The status of the build #256 was: FAILURE. The Pull Request #6224 was integrated: "6184-Cursor-doesnt-blink-in-the-inspector" Pull request url: https://github.com/pharo-project/pharo/pull/6224 Issue Url: https://github.com/pharo-project/pharo/issues/6184

[Pharo-dev] [Pharo 9.0] Build #255: 5898-Intersection-of-SortedCollection-forgets-the-sorting-block-in-the-new-collection

There is a new Pharo build available! The status of the build #255 was: FAILURE. The Pull Request #6215 was integrated: "5898-Intersection-of-SortedCollection-forgets-the-sorting-block-in-the-new-collection" Pull request url: https://github.com/pharo-project/pharo/pull/6215 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #254: [cleanup] remove comment following #5244 and #6147

There is a new Pharo build available! The status of the build #254 was: FAILURE. The Pull Request #6217 was integrated: "[cleanup] remove comment following #5244 and #6147" Pull request url: https://github.com/pharo-project/pharo/pull/6217 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #253: [fix] beginsWith: deverses executable comments

There is a new Pharo build available! The status of the build #253 was: FAILURE. The Pull Request #6223 was integrated: "[fix] beginsWith: deverses executable comments" Pull request url: https://github.com/pharo-project/pharo/pull/6223 Issue Url:

[Pharo-dev] [Pharo 9.0] Build #252: Fix #5854. SycMethodNameEditor fails with DNU in some cases

There is a new Pharo build available! The status of the build #252 was: FAILURE. The Pull Request #6216 was integrated: "Fix #5854. SycMethodNameEditor fails with DNU in some cases" Pull request url: https://github.com/pharo-project/pharo/pull/6216 Issue Url:

Re: [Pharo-dev] Programmatically change display size in Pharo 8 / 9

Hi Sven, On 24 Apr 2020, at 11:08, Sven Van Caekenberghe wrote: > Hi Max, > > Not an answer, but do you really need VNC to deploy on a server ? It's certainly debatable. We're used to having it, that's the main reason. > > This is often unreliably and a bit overkill, it is also alien to the

[Pharo-dev] [Pharo 9.0] Build #251: 6172-Syntax-highlighter-doesnt-work-with-capitalised-symbols

There is a new Pharo build available! The status of the build #251 was: FAILURE. The Pull Request #6212 was integrated: "6172-Syntax-highlighter-doesnt-work-with-capitalised-symbols" Pull request url: https://github.com/pharo-project/pharo/pull/6212 Issue Url:

Re: [Pharo-dev] Programmatically change display size in Pharo 8 / 9

Hi Max, Not an answer, but do you really need VNC to deploy on a server ? This is often unreliably and a bit overkill, it is also alien to the rest of the server world. Provided you can build your project automatically from a single Metacello invocation, you can build server side, command

[Pharo-dev] Programmatically change display size in Pharo 8 / 9

Hi all, I'm trying to change the size of the display programmatically but am having some trouble. It used to be possible to do `Display setExtent: 50@50 depth: 16` and that would take care of everything. I can still do that but 1. the renderer reverts the changes immediately and 2. if I