July 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Thierry Goubier

2016-07-20 16:47 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: > On Wed, Jul 20, 2016 at 03:00:01PM +0200, Denis Kudriashov wrote: > > It was like that in some Pharo version > > Only shortly, because people preferred consistency over convenience, so it > was changed back. > (Note that there is no correct answer here.) > There is one correct answer according to you then: - A browser able to show a list of implementors / senders. Can be done with RB environments and Nautilus scoping, probably. Thierry > > Peter > > > > > 2016-07-20 2:45 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > > > > > > On Tue, Jul 19, 2016 at 8:26 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> > > > wrote: > > > > > >> Which method should I change if when browsing senders/implementors > there > > >> is only one sender or implementor I'd like the Nautilus browser to > open? > > >> > > >> > > > +999999999 > > > > > > I would also love this!!!! > > > > > > > > > -- > > > Mariano > > > http://marianopeck.wordpress.com > > > > >

July 20, 2016

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Cyril Ferlicot Delbecque

On 20/07/2016 16:47, Peter Uhnak wrote: > Only shortly, because people preferred consistency over convenience, so it was changed back. > (Note that there is no correct answer here.) > The correct answer could be the third: make it into a setting :) > Peter > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

July 20, 2016

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Peter Uhnak

On Wed, Jul 20, 2016 at 03:00:01PM +0200, Denis Kudriashov wrote: > It was like that in some Pharo version Only shortly, because people preferred consistency over convenience, so it was changed back. (Note that there is no correct answer here.) Peter > > 2016-07-20 2:45 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > > On Tue, Jul 19, 2016 at 8:26 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> > > wrote: > > > >> Which method should I change if when browsing senders/implementors there > >> is only one sender or implementor I'd like the Nautilus browser to open? > >> > >> > > +999999999 > > > > I would also love this!!!! > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > >

July 20, 2016

Re: [Pharo-users] SQLite and sure last_insert_rowid

by Pierce Ng

On Sat, Jul 16, 2016 at 02:19:37PM +0800, Hilaire wrote: > In a multi-thread context use of Sqlite, I try to find out how one will > fetch securely the automatically last row index of a Primary key. > > The problem seems to be that between the insert of rows in a table and > the moment you request the last row id, you may have another insert from > another thread in the same database. Hi Hilaire, See http://www.sqlite.org/c3ref/last_insert_rowid.html, especially last paragraph: If a separate thread performs a new INSERT on the same database connection while the sqlite3_last_insert_rowid() function is running and thus changes the last insert rowid, then the value returned by sqlite3_last_insert_rowid() is unpredictable and might not equal either the old or the new last insert rowid. Pierce

July 20, 2016

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Denis Kudriashov

It was like that in some Pharo version 2016-07-20 2:45 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Tue, Jul 19, 2016 at 8:26 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> > wrote: > >> Which method should I change if when browsing senders/implementors there >> is only one sender or implementor I'd like the Nautilus browser to open? >> >> > +999999999 > > I would also love this!!!! > > > -- > Mariano > http://marianopeck.wordpress.com >

July 20, 2016

Re: [Pharo-users] Image not starting

by Valentin Ryckewaert

It's working I integrated it, but I don't understand why it was making my image crash (It wasn't crashing few weeks ago) 2016-07-20 8:35 GMT+02:00 Valentin Ryckewaert <valentin.ryckewaert(a)gmail.com >: > I'll try this as soon as I'm at work thanks you :) > > 2016-07-19 21:59 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> Now it seems to work, >> I followed you instruction from the first mail and just added another >> line to the load.st >> (unset option to inform about read only changes files) >> >> Metacello new >> smalltalkhubUser: 'Uryon' project: 'Coral'; >> configuration: 'Coral'; >> version: #development; >> onConflictUseIncoming; >> load. >> PharoFilesOpener default unsetInformAboutReadOnlyChanges. >> SmalltalkImage configureSystemAsReadonlyAndQuit:true >> >> >> >> 2016-07-19 0:27 GMT+02:00 Valentin Ryckewaert < >> valentin.ryckewaert(a)gmail.com>: >> >>> We tried to put it in a file, print in in stdout, put it as an display >>> in the image.... >>> >>> 2016-07-18 21:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>>> >>>> >>>> 2016-07-18 14:36 GMT+02:00 Valentin Ryckewaert < >>>> valentin.ryckewaert(a)gmail.com>: >>>> >>>>> Hello, >>>>> >>>>> with Pavel we tried to print with a lot of methods but it didn't work, >>>>> i'm searching the source of the problem manually. >>>>> >>>> >>>> What do you mean witth: >>>> "tried to print with a lot of methods" ? >>>> >>>> You can not use stdout to print when doing image shutdown and restart, >>>> because all file streams will be closed during the shutdown (see session >>>> manager). >>>> If you want to use stdout to print log messages (right after image >>>> startup), you need to make sure that the stdout/err stream are already >>>> recreated. >>>> (And for example, reinitialize Coral, if coral has reference to the >>>> (old) closed filestream. >>>> >>>> >>>> >>>> >>>>> >>>>> 2016-07-18 14:32 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>>> >>>>>> Thanks for the suggestion. It is probably the case. >>>>>> >>>>>> Le 17/7/16 Ã 23:27, Nicolai Hess a Ã©crit : >>>>>> >>>>>> Hi Valentin, Ithink you can not print to stdout during shutdown and >>>>>> restart. >>>>>> It will end in a Loop of writing to stdout, throwing an exceptions >>>>>> because it can not write and trying to log the error on stdout, throwing an >>>>>> error... >>>>>> >>>>>> Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" < >>>>>> valentin.ryckewaert(a)gmail.com>: >>>>>> >>>>>>> i will do it tomorrow. >>>>>>> >>>>>>> 2016-07-17 17:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>>>>> >>>>>>>> did you try to solution proposed? >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> Le 17/7/16 Ã 16:22, Valentin Ryckewaert a Ã©crit : >>>>>>>> >>>>>>>> Hello Stef, >>>>>>>> >>>>>>>> no i'm still on it :( >>>>>>>> I'm going to test every code I modified >>>>>>>> >>>>>>>> Valentin >>>>>>>> >>>>>>>> 2016-07-17 15:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>>>>>> >>>>>>>>> HI valentin >>>>>>>>> >>>>>>>>> >>>>>>>>> did you solve your problem? >>>>>>>>> >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> Le 12/7/16 Ã 15:33, Valentin Ryckewaert a Ã©crit : >>>>>>>>> >>>>>>>>> Hello everyone, >>>>>>>>> >>>>>>>>> I'm currently working on the project file policy and I'm having a >>>>>>>>> problem that I don't understand >>>>>>>>> >>>>>>>>> I import my code, configure my image as readOnly (Pharo won't try >>>>>>>>> to write on changesFiles,source,image....), set the folder of the image in >>>>>>>>> readonly and try to open the image again and it's not possible, I don't get >>>>>>>>> any stacktrace so it's hard to understand the problem. >>>>>>>>> >>>>>>>>> PS : If we set back the folder in write mode, it's possible again >>>>>>>>> to open the image again. >>>>>>>>> >>>>>>>>> Here is the code to reproduce the bug, could someone give me a >>>>>>>>> clue please? >>>>>>>>> >>>>>>>>> sudo rm -r testPharo >>>>>>>>> mkdir testPharo >>>>>>>>> cd testPharo >>>>>>>>> >>>>>>>>> echo "Metacello new >>>>>>>>> smalltalkhubUser: 'Uryon' project: 'Coral'; >>>>>>>>> configuration: 'Coral'; >>>>>>>>> version: #development; >>>>>>>>> onConflictUseIncoming; >>>>>>>>> load. >>>>>>>>> SmalltalkImage configureSystemAsReadonlyAndQuit:true >>>>>>>>> " >> load.st >>>>>>>>> >>>>>>>>> mkdir coral >>>>>>>>> cd coral >>>>>>>>> curl get.pharo.org/alpha | bash >>>>>>>>> curl get.pharo.org/vm60 | bash >>>>>>>>> pharo-vm/pharo Pharo.image ../load.st >>>>>>>>> cd .. >>>>>>>>> chmod -R -w coral >>>>>>>>> coral/pharo-vm/pharo coral/Pharo.image >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

July 20, 2016

Re: [Pharo-users] Image not starting

by Valentin Ryckewaert

I'll try this as soon as I'm at work thanks you :) 2016-07-19 21:59 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Now it seems to work, > I followed you instruction from the first mail and just added another line > to the load.st > (unset option to inform about read only changes files) > > Metacello new > smalltalkhubUser: 'Uryon' project: 'Coral'; > configuration: 'Coral'; > version: #development; > onConflictUseIncoming; > load. > PharoFilesOpener default unsetInformAboutReadOnlyChanges. > SmalltalkImage configureSystemAsReadonlyAndQuit:true > > > > 2016-07-19 0:27 GMT+02:00 Valentin Ryckewaert < > valentin.ryckewaert(a)gmail.com>: > >> We tried to put it in a file, print in in stdout, put it as an display in >> the image.... >> >> 2016-07-18 21:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2016-07-18 14:36 GMT+02:00 Valentin Ryckewaert < >>> valentin.ryckewaert(a)gmail.com>: >>> >>>> Hello, >>>> >>>> with Pavel we tried to print with a lot of methods but it didn't work, >>>> i'm searching the source of the problem manually. >>>> >>> >>> What do you mean witth: >>> "tried to print with a lot of methods" ? >>> >>> You can not use stdout to print when doing image shutdown and restart, >>> because all file streams will be closed during the shutdown (see session >>> manager). >>> If you want to use stdout to print log messages (right after image >>> startup), you need to make sure that the stdout/err stream are already >>> recreated. >>> (And for example, reinitialize Coral, if coral has reference to the >>> (old) closed filestream. >>> >>> >>> >>> >>>> >>>> 2016-07-18 14:32 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>> >>>>> Thanks for the suggestion. It is probably the case. >>>>> >>>>> Le 17/7/16 Ã 23:27, Nicolai Hess a Ã©crit : >>>>> >>>>> Hi Valentin, Ithink you can not print to stdout during shutdown and >>>>> restart. >>>>> It will end in a Loop of writing to stdout, throwing an exceptions >>>>> because it can not write and trying to log the error on stdout, throwing an >>>>> error... >>>>> >>>>> Am 17.07.2016 18:36 schrieb "Valentin Ryckewaert" < >>>>> valentin.ryckewaert(a)gmail.com>: >>>>> >>>>>> i will do it tomorrow. >>>>>> >>>>>> 2016-07-17 17:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>>>> >>>>>>> did you try to solution proposed? >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> Le 17/7/16 Ã 16:22, Valentin Ryckewaert a Ã©crit : >>>>>>> >>>>>>> Hello Stef, >>>>>>> >>>>>>> no i'm still on it :( >>>>>>> I'm going to test every code I modified >>>>>>> >>>>>>> Valentin >>>>>>> >>>>>>> 2016-07-17 15:23 GMT+02:00 stepharo <stepharo(a)free.fr>: >>>>>>> >>>>>>>> HI valentin >>>>>>>> >>>>>>>> >>>>>>>> did you solve your problem? >>>>>>>> >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> Le 12/7/16 Ã 15:33, Valentin Ryckewaert a Ã©crit : >>>>>>>> >>>>>>>> Hello everyone, >>>>>>>> >>>>>>>> I'm currently working on the project file policy and I'm having a >>>>>>>> problem that I don't understand >>>>>>>> >>>>>>>> I import my code, configure my image as readOnly (Pharo won't try >>>>>>>> to write on changesFiles,source,image....), set the folder of the image in >>>>>>>> readonly and try to open the image again and it's not possible, I don't get >>>>>>>> any stacktrace so it's hard to understand the problem. >>>>>>>> >>>>>>>> PS : If we set back the folder in write mode, it's possible again >>>>>>>> to open the image again. >>>>>>>> >>>>>>>> Here is the code to reproduce the bug, could someone give me a clue >>>>>>>> please? >>>>>>>> >>>>>>>> sudo rm -r testPharo >>>>>>>> mkdir testPharo >>>>>>>> cd testPharo >>>>>>>> >>>>>>>> echo "Metacello new >>>>>>>> smalltalkhubUser: 'Uryon' project: 'Coral'; >>>>>>>> configuration: 'Coral'; >>>>>>>> version: #development; >>>>>>>> onConflictUseIncoming; >>>>>>>> load. >>>>>>>> SmalltalkImage configureSystemAsReadonlyAndQuit:true >>>>>>>> " >> load.st >>>>>>>> >>>>>>>> mkdir coral >>>>>>>> cd coral >>>>>>>> curl get.pharo.org/alpha | bash >>>>>>>> curl get.pharo.org/vm60 | bash >>>>>>>> pharo-vm/pharo Pharo.image ../load.st >>>>>>>> cd .. >>>>>>>> chmod -R -w coral >>>>>>>> coral/pharo-vm/pharo coral/Pharo.image >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

July 20, 2016

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Mariano Martinez Peck

On Tue, Jul 19, 2016 at 8:26 PM, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > Which method should I change if when browsing senders/implementors there > is only one sender or implementor I'd like the Nautilus browser to open? > > +999999999 I would also love this!!!! -- Mariano http://marianopeck.wordpress.com

July 20, 2016

Re: [Pharo-users] change which browser opens when browsing senders/implementors

by Henrik Nergaard

SystemNavigation>>#browseMessageList:name:autoSelect:refreshingBlock: Adding: "methods size = 1 ifTrue: [ ^ methods anyOne browse ]." At line 10 should do the trick I think. Best regards, Henrik -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of PAUL DEBRUICKER Sent: Wednesday, July 20, 2016 1:26 AM To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] change which browser opens when browsing senders/implementors Which method should I change if when browsing senders/implementors there is only one sender or implementor I'd like the Nautilus browser to open? thanks Paul

July 19, 2016

change which browser opens when browsing senders/implementors

by PAUL DEBRUICKER

Which method should I change if when browsing senders/implementors there is only one sender or implementor I'd like the Nautilus browser to open? thanks Paul

July 19, 2016