May 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] SmalltalkHub username/password in environment variable?

by Yuriy Tymchuk

Hi http://stackoverflow.com/questions/23673986/how-to-publish-to-smalltalkhub-… Uko On 14 May 2014, at 11:56, Mircea Filip Lungu <lungu(a)iam.unibe.ch> wrote: > Hi folks, > > Is there a way of setting the SmalltalkHub username and password in an environment variable or an external configuration file as opposed to setting them in every repository in every image? > > It gets old introducing them always :) > > Cheers, > M. > > > -- > Mircea Lungu, PhD. > Researcher > Software Composition Group > University of Bern >

May 15, 2014

Re: [Pharo-dev] Alt-Space is Non-breaking S

by Henrik Johansen

On 13 May 2014, at 8:05 , Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Tue, May 13, 2014 at 4:08 AM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > â¦ Which is extremely annoying when writing blocks with arguments on a norwegian OSX keyboard. > | is Alt - 7, when I donât release the Alt key before the following space, and a NBSP is inserted instead of a space character, which breaks both the parser and syntax highlighting. > > When doitâing, you get the syntax error: > [ :a | Unknown character ->a ] (notice also the off-by-one indicator, itâs not the a, but the preceding space which is unknown). > > Would it be better if NBSP were treated equally to a normal space by the parser, or is there some keyboard binding I can revert? > > I think getting the parser to accept NBSP is a really bad idea. If you want to export code to other dialects you can't rely on that happening. WTF is an accellerator key doing introducing an illegal sequence in the first place? Surely the key could insert a legal sequence? Hmm, it seems Alt-Space is mapped to NBSP by OSX itself, and has been for a long time, I guess I just havenât noticed before for some reasonâ¦ I agree accepting source with NBSP would be bad, I was thinking maybe have the parser substitute them with normal spaces instead of raising errors. Seems to me (at least in the RBParser of 3.0,) that might be viable, thereâs an error handling block (in RBParser >> #parserError:) which could possibly do it. As for the PS, it seems to me the off-by-one is caused by: scanError: theCause currentCharacter ifNotNil: [ :char | buffer nextPut: char ]. ^ RBErrorToken value: buffer contents asString start: tokenStart cause: theCause location: stream position + 1 Now, I donât mind the change that introduced a separate ErrorToken, Iâm more ambiguous about switching from using tokenStart to the streamâs position as the errorâs location though. In 99% of cases, the token of a syntax error will be a single character (if you write #wasÂ£ for example, #was will parse as a valid token before Â£ gives an unknown character error), the one exception I can think of is missing string literal/comment quotes, where location will be the end of the method, and token start will be at the unmatched quote. Though, in that case, isnât it better to display the Unmatched message *at* the unmatched quote itself, rather than at the end of method? Is there cases Iâve overlooked where the current location is better, or should RBErrorToken be changed back to just use tokenStart as the errorLocation? (Which would also simplify RBParser >> #parserError:) Cheers, Henry PS. Also, with an error token that includes a cause, does it ever make sense to use the string parameter to parserError:?

May 15, 2014

Re: [Pharo-dev] SmalltalkHub username/password in environment variable?

by phil＠highoctane.be

On Thu, May 15, 2014 at 11:23 AM, Mircea Filip Lungu <lungu(a)iam.unibe.ch>wrote: > Hi Phil! > > Thanks for the prompt answer. I can't get it to work though... > That's why I need Sean to tell us where the changes to get that working are... I want this too, so, ... bump :-) Phil > > Thanks, > M. > > > 2014-05-14 12:10 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> A while ago, Sean did this: >> >> Sean P. DeNigris <sean(a)clipperadams.com> >> 10/23/13 >> to pharo-dev >> philippeback wrote >> > Would be great to have a logout, in order to give images to other people >> > without leaving credentials around. >> >> Done, added to world menu under the individual repo login options >> >> The way the logins work is that a file named .mcconfig is expected in the >> general preferences folder with the format: >> >> [squeaksource] >> user := 'me'. >> password := 'pwd'. >> [squeaksource3] >> user := 'me'. >> password = 'pwd'. >> [smalltalkhub] >> user := 'me'. >> password := 'pwd'. >> >> >> But I do not see where is is used... >> >> Sean? >> >> Phil >> >> >> >> On Wed, May 14, 2014 at 11:56 AM, Mircea Filip Lungu <lungu(a)iam.unibe.ch>wrote: >> >>> Hi folks, >>> >>> Is there a way of setting the SmalltalkHub username and password in an >>> environment variable or an external configuration file as opposed to >>> setting them in every repository in every image? >>> >>> It gets old introducing them always :) >>> >>> Cheers, >>> M. >>> >>> >>> -- >>> Mircea Lungu, PhD. >>> Researcher >>> Software Composition Group >>> University of Bern >>> >>> >> > > > -- > Mircea Lungu, PhD. > Researcher > Software Composition Group > University of Bern > >

May 15, 2014

Re: [Pharo-dev] SmalltalkHub username/password in environment variable?

by Mircea Filip Lungu

Hi Phil! Thanks for the prompt answer. I can't get it to work though... Thanks, M. 2014-05-14 12:10 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > A while ago, Sean did this: > > Sean P. DeNigris <sean(a)clipperadams.com> > 10/23/13 > to pharo-dev > philippeback wrote > > Would be great to have a logout, in order to give images to other people > > without leaving credentials around. > > Done, added to world menu under the individual repo login options > > The way the logins work is that a file named .mcconfig is expected in the > general preferences folder with the format: > > [squeaksource] > user := 'me'. > password := 'pwd'. > [squeaksource3] > user := 'me'. > password = 'pwd'. > [smalltalkhub] > user := 'me'. > password := 'pwd'. > > > But I do not see where is is used... > > Sean? > > Phil > > > > On Wed, May 14, 2014 at 11:56 AM, Mircea Filip Lungu <lungu(a)iam.unibe.ch>wrote: > >> Hi folks, >> >> Is there a way of setting the SmalltalkHub username and password in an >> environment variable or an external configuration file as opposed to >> setting them in every repository in every image? >> >> It gets old introducing them always :) >> >> Cheers, >> M. >> >> >> -- >> Mircea Lungu, PhD. >> Researcher >> Software Composition Group >> University of Bern >> >> > -- Mircea Lungu, PhD. Researcher Software Composition Group University of Bern

May 15, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by phil＠highoctane.be

On Thu, May 15, 2014 at 10:44 AM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > damnâ¦ I was sure. I need to check now :) > Hey, when will we get a CentOS 6.x slave running? ;-) [sorry, couldn't resist. But, truth be told, having a CentOS version helps with credibility when it comes to the enterprise - My clients aren't using Ubuntu for sure, it is CentOS/RHEL with a LooooooongTS) One tiny glitch I noticed is that my PharoVM running on CentOS6 doesn't catches all keys under VMWare Workstation when I run it in a window. When VMWare is fullscreen, there is no issue at all. The keys do work fine in a linux terminal, so this is linked to the PharoVM as well. Phil > > Esteban > > On 15 May 2014, at 09:21, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > wrote: > > > Are you sure? > > Because VM fetched with "curl get.pharo.org/vmLatest | bash" has no > > working keypad. > > > > Hilaire > > > > Le 15/05/2014 00:46, Esteban Lorenzano a Ã©crit : > >> and is integrated but still not promoted to stable (I think it will be > >> next week). In the mean time, vmLatest will work. > >> > > > > -- > > Dr. Geo http://drgeo.eu > > > > > > >

May 15, 2014

Re: [Pharo-dev] Reef status

by Esteban Lorenzano

On 15 May 2014, at 10:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Reef works out of the box in Pharo3. > What does not work is the configuration (I need to update it) :P > > Real thing is that I was migrating (and simplifying) everything to work with bootstrap "out of the boxâ and I made (as always) just what I needed. But Iâm willing to help and to spend some time on it. > So, firstâ¦ I updated the configuration. This should work now: > > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Reef'; > configuration; > loadDevelopment. > ah, but you need to have seaside loaded first. Reef just loads âseaside coreâ, which means not all packages you might need (like the zinc adaptor) will be present. Esteban > And any question you haveâ¦ Iâm happy to help. > > cheers, > Esteban > > > On 15 May 2014, at 08:46, stepharo <stepharo(a)free.fr> wrote: > >> It would so great! >> Esteban is too busy but yes yes yes. >> We have a draft of a chapter but I do not enough knowledge to be efficient >> >> On 15/5/14 01:25, Facundo Vozzi wrote: >>> Hi, >>> someone is working with Reef and is someone planning to migrate to Pharo 3? >>> >>> Is it working on Pharo 2 ? >>> >>> Thanks, >>> >>> p.s.: if nobody is migrating it maybe I can try it with Esteban instructions. >> >> >

May 15, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by Esteban Lorenzano

damnâ¦ I was sure. I need to check now :) Esteban On 15 May 2014, at 09:21, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > Are you sure? > Because VM fetched with "curl get.pharo.org/vmLatest | bash" has no > working keypad. > > Hilaire > > Le 15/05/2014 00:46, Esteban Lorenzano a Ã©crit : >> and is integrated but still not promoted to stable (I think it will be >> next week). In the mean time, vmLatest will work. >> > > -- > Dr. Geo http://drgeo.eu > >

May 15, 2014

Re: [Pharo-dev] Reef status

by Esteban Lorenzano

Hi, Reef works out of the box in Pharo3. What does not work is the configuration (I need to update it) :P Real thing is that I was migrating (and simplifying) everything to work with bootstrap "out of the boxâ and I made (as always) just what I needed. But Iâm willing to help and to spend some time on it. So, firstâ¦ I updated the configuration. This should work now: Gofer it smalltalkhubUser: 'estebanlm' project: 'Reef'; configuration; loadDevelopment. And any question you haveâ¦ Iâm happy to help. cheers, Esteban On 15 May 2014, at 08:46, stepharo <stepharo(a)free.fr> wrote: > It would so great! > Esteban is too busy but yes yes yes. > We have a draft of a chapter but I do not enough knowledge to be efficient > > On 15/5/14 01:25, Facundo Vozzi wrote: >> Hi, >> someone is working with Reef and is someone planning to migrate to Pharo 3? >> >> Is it working on Pharo 2 ? >> >> Thanks, >> >> p.s.: if nobody is migrating it maybe I can try it with Esteban instructions. > >

May 15, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by phil＠highoctane.be

On Thu, May 15, 2014 at 9:08 AM, Hilaire Fernandes < hilaire.fernandes(a)gmail.com> wrote: > Is your build done against not too recent libc et al. ? > If so I will be interested to have an archive of it. > I've sent you a dropbox link. The thing is uploading now. Tell me how it works. Phil > > Thanks > > Le 14/05/2014 22:28, phil(a)highoctane.be a Ã©crit : > > > > Keypad works on my linux build. There was a lost commit somewhere and I > > fwded the file to Esteban for integration. > > -- > Dr. Geo http://drgeo.eu > > >

May 15, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by Hilaire Fernandes

Are you sure? Because VM fetched with "curl get.pharo.org/vmLatest | bash" has no working keypad. Hilaire Le 15/05/2014 00:46, Esteban Lorenzano a Ã©crit : > and is integrated but still not promoted to stable (I think it will be > next week). In the mean time, vmLatest will work. > -- Dr. Geo http://drgeo.eu

May 15, 2014