[Pharo-dev] [pharo-project/pharo-core] 4fb354: 60095

2016-06-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4fb354e0d46b1acfc61183dccc94eb3bfeeb4348 https://github.com/pharo-project/pharo-core/commit/4fb354e0d46b1acfc61183dccc94eb3bfeeb4348 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

2016-06-17 Thread GitHub
Branch: refs/tags/60095 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 80fbbc: 60094

2016-06-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 80fbbc02844a45677c751eb14226e99321363381 https://github.com/pharo-project/pharo-core/commit/80fbbc02844a45677c751eb14226e99321363381 Author: Jenkins Build Server Date:

[Pharo-dev] PluggableTextFieldMorph Entry Completion Enhancement

2016-06-17 Thread Sean P. DeNigris
I've run into a limitation a few times where PluggableTextFieldMorph accepts the text regardless of the outcome of the entryCompletion's chooseBlock. I've found that this is not always appropriate. As such, I propose that PluggableTextFieldMorph skip accepting if the chooseBlock returns false. Any

Re: [Pharo-dev] Automatic deprecation refactoring

2016-06-17 Thread stepharo
it is using #Refactoring asClassIfPresent: I would prefer self class environment atIfPresent: Because asClass is evil since it does not consider that we can have different namespaces. Stef Le 17/6/16 à 12:22, Guille Polito a écrit : Hi! How is this packaged? I don't want to

[Pharo-dev] Re : Re: [Pharo-users] Pharo Launcher

2016-06-17 Thread Christophe Demarey
Yes. It was that. Thanks - Sean P. DeNigris a écrit : > demarey wrote > > Now fixed > > Was that due to the #vm40Path being incorrectly set? I was going to report > that... > > > > - > Cheers, > Sean > -- > View this message in context: >

Re: [Pharo-dev] pharo 5 segfault (stack size?) [FreeBSD]

2016-06-17 Thread Petr Fischer
VM version (from https://swing.fit.cvut.cz/jenkins/job/pharo-vm-spur-swing/): 5.0 #1 Sun Jan 17 14:19:14 CET 2016 gcc 4.7.2 [Production Spur ITHB VM] CoInterpreter VMMaker.oscog-eem.1630 uuid: 2ed025ea-f400-4440-8e8b-5aa46d06c9ab Jan 17 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1630

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-17 Thread Tudor Girba
Hi Nicolai, > On Jun 17, 2016, at 2:59 PM, Nicolai Hess wrote: > > > > 2016-06-17 14:35 GMT+02:00 Tudor Girba : > Hi Nicolai, > > I am a bit removed from the code details at the moment, and I think I need to > step back a bit :). > > If I

Re: [Pharo-dev] Official packages on pharo.com - broken

2016-06-17 Thread Jan Vrany
On Fri, Jun 17, 2016 at 2:56 PM, Peter Uhnak wrote: On Fri, Jun 17, 2016 at 03:24:37PM +0200, Sven Van Caekenberghe wrote: > On 17 Jun 2016, at 15:15, Petr Fischer wrote: > > It's due to my obscure OS (‎FreeBSD, latest). They have Linux

Re: [Pharo-dev] Official packages on pharo.com - broken

2016-06-17 Thread Peter Uhnak
On Fri, Jun 17, 2016 at 03:24:37PM +0200, Sven Van Caekenberghe wrote: > > > On 17 Jun 2016, at 15:15, Petr Fischer wrote: > > > > It's due to my obscure OS (‎FreeBSD, latest). They have Linux compatibility > > (even 64bits soon), so it's nice, but libs are from CentOS6

[Pharo-dev] [pharo-project/pharo-core] d6d2a4: 60092

2016-06-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: d6d2a49d685a98a1bdebbd9c76b046c06acfc2bd https://github.com/pharo-project/pharo-core/commit/d6d2a49d685a98a1bdebbd9c76b046c06acfc2bd Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

2016-06-17 Thread GitHub
Branch: refs/tags/60092 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] GT-Spotter dive in shortcut

2016-06-17 Thread Nicolai Hess
2016-06-17 14:35 GMT+02:00 Tudor Girba : > Hi Nicolai, > > I am a bit removed from the code details at the moment, and I think I need > to step back a bit :). > > If I understand correctly, you are saying that: > 1. defining bindings with #alt does not work on Windows. This

Re: [Pharo-dev] pharo 5 segfault (stack size?) [FreeBSD]

2016-06-17 Thread Max Leske
Hi Petr, That looks like a bug with FreeType with our FFI. It should actually have been fixed but I don’t know if the VM for FreeBSD is up to date. Can you post the output of “Smalltalk vm version”? Cheers, Max > On 17 Jun 2016, at 13:26, Petr Fischer wrote: > > Hello,

[Pharo-dev] [pharo-project/pharo-core]

2016-06-17 Thread GitHub
Branch: refs/tags/60091 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 4dd981: 60091

2016-06-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4dd98181596226cf85131d4b1d2d4b2269b6191f https://github.com/pharo-project/pharo-core/commit/4dd98181596226cf85131d4b1d2d4b2269b6191f Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

2016-06-17 Thread GitHub
Branch: refs/tags/60090 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] pharo 5 segfault (stack size?) [FreeBSD]

2016-06-17 Thread Petr Fischer
Hello, I got some random segfaults (while loading Seaside) with 32 bit spur vm on FreeBSD - can someone (with low level knowledge) decode attached log? Is this some problem with stack size? Can I fix this? Log: http://pastebin.com/raw/NpFUnjh0 There is "**StackOverflow**" lines n the log...

[Pharo-dev] Official packages on pharo.com - broken

2016-06-17 Thread Petr Fischer
Hello, look at this page: http://pharo.org/gnu-linux-installation and try to download "libc < 2.15" or "centos" versions. Both are broken - error message immediately after start: "This interpreter (vers. 6505) cannot read image file (vers. 6521)." So, the first impression is really terrible

[Pharo-dev] [pharo-project/pharo-core] bebc80: 60089

2016-06-17 Thread GitHub
Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: bebc80cd71de4131430ab5ddf9fb1367be92721f https://github.com/pharo-project/pharo-core/commit/bebc80cd71de4131430ab5ddf9fb1367be92721f Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

2016-06-17 Thread GitHub
Branch: refs/tags/60089 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Better #haltOnce: per haltOnce state, auto-enable

2016-06-17 Thread Marcus Denker
> On 14 Jun 2016, at 09:47, marcus.den...@inria.fr wrote: > > Hi, > > Yesterday we improved #haltOnce to be more like a “once” BreakPoint: > > -> state per *each* haltOnce send > (this means you can put two in one method and they are > independent) > -> when putting

Re: [Pharo-dev] Automatic deprecation refactoring

2016-06-17 Thread Marcus Denker
> On 17 Jun 2016, at 12:22, Guille Polito wrote: > > Hi! > > How is this packaged? I don't want to introduce a dependency to the > refactoring browser into the kernel… > There is *NO* dependency. > Guille > > Original Message >> Hi, >> >> >>

Re: [Pharo-dev] [Pharo-users] Pharo Launcher

2016-06-17 Thread Serge Stinckwich
On Fri, Jun 17, 2016 at 10:22 AM, Christophe Demarey wrote: > Hi, > > I just updated Pharo Launcher. A new version 0.2.11 is available. > Here are the change log: Great ! Thank you for the update. > move Pharo Launcher to the latest stable pharo image: pharo 5.0. It

Re: [Pharo-dev] Unambiguously differentiating official and local builds [Was [Vm-dev] Moving the Cog subversion repository to githup at 2016-6-16 7am UTC]

2016-06-17 Thread Alistair Grant
On Thu, Jun 16, 2016 at 08:51:16PM -0700, Eliot Miranda wrote: > > > > On Jun 16, 2016, at 3:32 PM, Serge Stinckwich > > wrote: > > > >> On Thu, Jun 16, 2016 at 11:08 PM, Eliot Miranda > >> wrote: > >> Hi Alistair, > >> > >> On Thu, Jun

Re: [Pharo-dev] changes in latest Athens configuration

2016-06-17 Thread Nicolai Hess
2016-06-17 9:04 GMT+02:00 Marcus Denker : > > On 10 Jun 2016, at 21:45, Nicolai Hess wrote: > > > > 2016-06-10 19:13 GMT+02:00 Aliaksei Syrel : > >> Sorry, I don't get what you mean with this: "Why do we merge compositing >>

Re: [Pharo-dev] changes in latest Athens configuration

2016-06-17 Thread Marcus Denker
> On 10 Jun 2016, at 21:45, Nicolai Hess wrote: > > > > 2016-06-10 19:13 GMT+02:00 Aliaksei Syrel >: > Sorry, I don't get what you mean with this: "Why do we merge compositing > modes with "paint options"?" > > I