Re: [Pharo-dev] pharo-contribution CI machines out of disk space

> On 17 Apr 2018, at 06:02, monty wrote: > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console Yes, I know, the whole CI infrastructure is down I guess ...

Re: [Pharo-dev] File path encoding

Actually, (from another thread) I think that it is related to how environment variables are accessed. Consider: $ FOO=benoît ./pharo Pharo.image eval 'OSEnvironment current associations' {'TERM_PROGRAM'->'Apple_Terminal'. 'TERM'->'xterm-256color'. 'SHELL'->'/bin/bash'.

[Pharo-dev] [Pharo 7.0-dev] Build #770: 21710-evaluate-should-use-compile-

There is a new Pharo build available! The status of the build #770 was: SUCCESS. The Pull Request #1201 was integrated: "21710-evaluate-should-use-compile-" Pull request url: https://github.com/pharo-project/pharo/pull/1201 Issue Url: https://pharo.fogbugz.com/f/cases/21710 Build Url:

Re: [Pharo-dev] [Pharo-users] [Pharo-Launcher] call for tests on Windows

I ran the launcher against my Windows 7 office computer and have created an issue with my feedback. https://github.com/pharo-project/pharo-launcher/issues/93 On Mon, Apr 16, 2018 at 7:13 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi, > > Regarding the various problems Pharo

Re: [Pharo-dev] File path encoding

On 16 April 2018 at 18:52, Ben Coman wrote: > On 16 April 2018 at 17:51, Sven Van Caekenberghe wrote: >> Hi, >> >> Some people raise issues with file path encoding with non-ASCII characters. >> >> The following works fine for me (macOS, Pharo 7, using new File

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

I guess that it is what I installed and it works fine on my Win 10 system. Nice icon BTW. Now there is an issue with the mouse pointer in the launcher and all pther images (so maybe a VM problem). The cursor is all black and tiny and has no white surroundings. In a dark theme the cursor is

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Hi Phil, > On Apr 16, 2018, at 8:16 AM, philippe.b...@highoctane.be > wrote: > > I guess that it is what I installed and it works fine on my Win 10 system. > > Nice icon BTW. > > Now there is an issue with the mouse pointer in the launcher and all pther > images (so

Re: [Pharo-dev] Esteban's ChangeLog week of 9 April 2018

EstebanLM wrote > 13 April 2018… I just promoted new VMs as stable. Weren't those reverted? - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] [ANN] New VM stables promoted

Sean P. DeNigris wrote >> but you can always use vmLatest instead stable > Is anyone using vmLatest 32-bit on Mac for Pharo 6.1/7? Any problems? I > would like to upgrade… Bump :) I am eager to upgrade if save, but have some mission critical things I don't want interrupted. Thanks! -

[Pharo-dev] [Pharo-Launcher] call for tests on Windows

Hi, Regarding the various problems Pharo Launchers had on Windows, we worked on a new installer based on Advanced Installer [1] to avoid UAC (User Account Control) and write permissions problems. This new installer now installs Pharo Launcher in the user’s local app data folder (where for

Re: [Pharo-dev] File path encoding

On 16 April 2018 at 17:51, Sven Van Caekenberghe wrote: > Hi, > > Some people raise issues with file path encoding with non-ASCII characters. > > The following works fine for me (macOS, Pharo 7, using new File class): > > "works" > > (FileLocator temp / 'foo' , 'txt') writeStreamDo:

[Pharo-dev] [Pharo 7.0-dev] Build #768: 21698-ClassDefinitionShouldHideSlots

There is a new Pharo build available! The status of the build #768 was: SUCCESS. The Pull Request #1196 was integrated: "21698-ClassDefinitionShouldHideSlots" Pull request url: https://github.com/pharo-project/pharo/pull/1196 Issue Url: https://pharo.fogbugz.com/f/cases/21698 Build Url:

Re: [Pharo-dev] Critiques - Temporaries read before written.

On 04/15/2018 05:02 PM, Ben Coman wrote: > On 16 April 2018 at 03:07, Denis Kudriashov wrote: >> >> >> >> 2018-04-15 20:40 GMT+02:00 Martin McClure : >>> >>> On 04/15/2018 07:42 AM, Ben Coman wrote: >>> >>> The greater prominence of Critiques in

Re: [Pharo-dev] File path encoding

Ben, On my machine, macOS 10.13.4, $ pwd /tmp/benoît $ curl get.pharo.org/70+vm | bash % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3036 100 30360 0 38694 0

Re: [Pharo-dev] File path encoding

>> On 16 Apr 2018, at 13:05, Ben Coman wrote: >> >> On 16 April 2018 at 18:52, Ben Coman wrote: >>> On 16 April 2018 at 17:51, Sven Van Caekenberghe wrote: Hi, Some people raise issues with file path encoding with

Re: [Pharo-dev] File path encoding

> On 16 Apr 2018, at 14:51, Alistair Grant wrote: > > Hi Sven, > > On 16 April 2018 at 13:57, Sven Van Caekenberghe wrote: >> >> Technically, at the File (FilePlugin) level we seem to be able to handle >> paths with strange characters, even on Windows,

Re: [Pharo-dev] Esteban's ChangeLog week of 9 April 2018

yes, but I didn’t write it in my log so is not reported ;) > On 16 Apr 2018, at 17:55, Sean P. DeNigris wrote: > > EstebanLM wrote >> 13 April 2018… I just promoted new VMs as stable. > > Weren't those reverted? > > > > - > Cheers, > Sean > -- > Sent from:

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Eliot, Thx for the pointer. No, there is no such file in the vm folder that is launching the Pharo Launcher nor is there one in the vms folders that are downloaded to run the various images started by the launcher. This manifest file is new to me. Where is it to be found and what does it do for

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

I have downloaded the https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/build.win32x86/pharo.cog.spur.lowcode/Pharo.exe.manifest and put it in the folder that contains the PharoLauncher Pharo.exe and then the pointers are correct again (they have their masking done correctly.

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Hi Phil, On Mon, Apr 16, 2018 at 12:54 PM, p...@highoctane.be wrote: > I have downloaded the https://github.com/pharo- > project/pharo-vm/blob/master/opensmalltalk-vm/build. > win32x86/pharo.cog.spur.lowcode/Pharo.exe.manifest and put it in the > folder that contains the

[Pharo-dev] Esteban's ChangeLog week of 9 April 2018

Hello! This is my weekly ChangeLog, from 9 April 2018 to 15 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=9/4/2018=15/4/2018 ChangeLog = 13 April 2018: -- *I just promoted new VMs as stable. This are the

[Pharo-dev] pharo-contribution CI machines out of disk space

https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console

[Pharo-dev] [Pharo 7.0-dev] Build #769: 21709-add-compiler-option-embedded-source

There is a new Pharo build available! The status of the build #769 was: SUCCESS. The Pull Request #1200 was integrated: "21709-add-compiler-option-embedded-source" Pull request url: https://github.com/pharo-project/pharo/pull/1200 Issue Url: https://pharo.fogbugz.com/f/cases/21709

Re: [Pharo-dev] File path encoding

Hi Sven, On 16 April 2018 at 13:57, Sven Van Caekenberghe wrote: > > Technically, at the File (FilePlugin) level we seem to be able to handle > paths with strange characters, even on Windows, but somehow, somewhere a > bogus call is made during image startup. I'm not going to

[Pharo-dev] [Pharo 7.0-dev] Build #766: 21688-OSWindowDriver-is-not-correcly-cleaned-on-shutdown

There is a new Pharo build available! The status of the build #766 was: SUCCESS. The Pull Request #1191 was integrated: "21688-OSWindowDriver-is-not-correcly-cleaned-on-shutdown" Pull request url: https://github.com/pharo-project/pharo/pull/1191 Issue Url:

[Pharo-dev] File path encoding

Hi, Some people raise issues with file path encoding with non-ASCII characters. The following works fine for me (macOS, Pharo 7, using new File class): "works" (FileLocator temp / 'foo' , 'txt') writeStreamDo: [ :out | out << 'Les élèves Français' ; crlf ]. (FileLocator temp / 'foo' , 'txt')

[Pharo-dev] [Pharo 7.0-dev] Build #767: 21707-revert-for-now-the-change-that-made-evaluate-doit-to-loose-variable-names

There is a new Pharo build available! The status of the build #767 was: SUCCESS. The Pull Request #1199 was integrated: "21707-revert-for-now-the-change-that-made-evaluate-doit-to-loose-variable-names" Pull request url: https://github.com/pharo-project/pharo/pull/1199 Issue Url: