- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Iceberg ?

by Stephane Ducasse

I retried rename all the keys I put in my git account. But > ssh-add -K ~/.ssh/github_rsa Error connecting to agent: No such file or directory > ssh-add -K ~/.ssh/2016RSA Error connecting to agent: No such file or directory Apparently I should run eval `ssh-agent -s` Now I will try to republish on github. anyway I'm not using git in pharo for now. Stef On Thu, May 25, 2017 at 8:20 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > I do not get why I can use github all the time and not with pharo. > > That is an excellent question > > Alexandre > >

May 25, 2017

Re: [Pharo-dev] Iceberg ?

by Alexandre Bergel

> I do not get why I can use github all the time and not with pharo. That is an excellent question Alexandre

May 25, 2017

Re: [Pharo-dev] Iceberg ?

by Stephane Ducasse

In fact I checked before and to me it looks ok. Now should I have the same name for the key? trying now. I do not get why I can use github all the time and not with pharo. total 216 drwx------ 21 ducasse admin 714 May 25 18:13 ./ drwxr-xr-x@ 118 ducasse staff 4012 Apr 28 16:25 ../ -rw-r--r-- 1 ducasse admin 12288 Mar 20 2015 .config.swp -rw------- 1 ducasse admin 1766 Jan 10 2016 2016RSA -rw-r--r--@ 1 ducasse admin 401 Jan 10 2016 2016RSA.pub -rw-r--r-- 1 ducasse staff 10054 Sep 30 2009 KnowHOST -rw-r--r--@ 1 ducasse staff 238 Mar 7 2011 authorized_keys -rw-r--r--@ 1 ducasse staff 1765 Jun 29 2016 config -rw-------@ 1 ducasse staff 1697 Jun 1 2010 esug.pem -rw------- 1 ducasse staff 1743 Aug 26 2011 github_rsa -rw-r--r-- 1 ducasse staff 389 Aug 26 2011 github_rsa.pub -rw------- 1 ducasse staff 668 Sep 30 2009 id_dsa -rw-r--r-- 1 ducasse staff 609 Sep 30 2009 id_dsa.pub -rw------- 1 ducasse staff 951 Sep 30 2009 id_rsa -rw-r--r-- 1 ducasse staff 238 Sep 30 2009 id_rsa.pub -rw-r--r--@ 1 ducasse staff 17378 Jul 19 2016 known2 -rw-r--r-- 1 ducasse admin 413 May 25 18:24 known_hosts -rw-r--r-- 1 ducasse staff 609 Sep 30 2009 mail -rw------- 1 ducasse staff 1675 Jun 1 2010 newRSAA -rw-r--r-- 1 ducasse staff 406 Jun 1 2010 newRSAA.pub On Mon, May 22, 2017 at 10:14 PM, Max Leske <maxleske(a)gmail.com> wrote: > ls -la ~/.ssh wil probably show you that you donât have a key named > âid_rsaâ. You have to specify the correct file (e.g. my github key is named > âgithubâ). > > HTH, > Max > > On 22 May 2017, at 21:47, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > I get > > ssh-add -K ~/.ssh/id_rsa > > Error connecting to agent: No such file or directory > > > > On Mon, May 22, 2017 at 9:46 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Yes please do because I had no idea and I was trying to look at the >> setting but without results. >> >> On Mon, May 22, 2017 at 8:53 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> is not weird because git uses other authentication services and for now >>> we just implemented ssh/ssh-agent :) >>> solution is to execute this in command line: >>> >>> ssh-add -K ~/.ssh/id_rsa >>> >>> then it will be ok. >>> >>> (I will add an entry for this in the FAQ) >>> >>> >>> On 22 May 2017, at 20:48, Alexandre Bergel <alexandre.bergel(a)me.com> >>> wrote: >>> >>> I got the very same error. And this is weird because I can commit from >>> the command line or using any Git client. >>> >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> On May 21, 2017, at 5:31 AM, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> >>> On mac with latest pharo vm and latest pharo 60 >>> Metacello new >>> baseline: 'Bloc'; >>> repository: 'github://pharo-graphics/Bloc/src'; >>> load:#core >>> >>> Then I got LGit_GIT_ERROR no ssh-agent suitable credentials found >>> >>> >>> >>> >>> >> > >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by phil＠highoctane.be

WebDoc used to work in 3.0 Didn't loaded it since. This is doing things like this: http://files.pharo.org/doc/1.2/#packageList=webdoc/doc/package.html&classLi… Phil On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > Nice idea. I've seen vague discussion about getting Pillar into the > standard image for documentation. > Perhaps it should be raised for consideration for Pharo 7? > > Actually you stimulate my thoughts that the Help file might be a > better place for such snippets, > so they are always with the image, and don't need to be retyped. Any > objections? > > cheers -ben > > On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > > Ben, > > > > I think there is a deeper need here. Writing good document is hard and > > keeping it in sync with code is harder still. > > > > A book/booklet separates content from the code and being frozen in time > > faces obsolescence. I would prefer to see a guidebook framework in Pharo > > that every package author can use to create a simple narrative on its > > features. Package authors and consumers have an incentive to keep the > code > > and content in sync. If an Object is a recursion on the notion of a > > computer, why not provide, say a Note, as a recursive simplification of a > > book? > > > > The framework could be on the lines of Plugins, Tests. E.g. > > > > Package-Core > > Package-Plugins > > Package-Tests > > *Package-Guide* > > > > The guide framework should support active code (say to pop the source > code > > for a method), active links to guides on which this package depends, > > automatic generation of table of contents, index of class references. > Most > > of features already exists in Pharo but spread all over. They need a > home. > > > > A package could also extend this basic framework with features (e.g. PDF > > package could export articles to PDF, Zinc could generate HTML). > > > > Regards .. Subbu > > > > > > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: > >> > >> I've seen a few requests for short bits of code to use in playground for > >> a demo presentation. I wonder if it would be good to have a booklet to > >> gather these - seeded with Sven's excellent article... > >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 > >> > >> It could include the recent meta-programming scripts like searching for > >> all class instance variables starting with a capital letter. > >> > >> The book might be named "Snippets", in a format presentable to laser > >> print on-site - something physical for attendees to take away with them > >> to quick demo to others back in their office. > >> > >> I can take the lead in setting it up. Anyone remember any relevant > >> posts in our archives? > >> > >> cheers -ben > > > > > > > >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Ben Coman

On Thu, May 25, 2017 at 9:59 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > What I would like is to extend pillar with a special environment > > I had the same thought for a long time, but its sunk lower on my list. > [[[testable=5 > 3+ 2 > ]]] > > and also > [[[screenshot: 10@200 named: 'browserOpen' > Browser open > ]]] > Maybe something like... [[[ window := Browser openSized: 10@200. window saveSnapshotAs: 'browserOpen' ]]] cheers -ben > > Now I need help on pillar. > > Stef > > > > On Thu, May 25, 2017 at 3:57 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> What I'm doing is >> - extracting a subset of pillar >> - doc + renderer >> - so that we can use it in the image. >> Now kasper did a first version (in the repository and if people want to >> have a look it will help) >> - now I'm remaving the dependency on magritte. >> >> Stef >> >> On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> Nice idea. I've seen vague discussion about getting Pillar into the >>> standard image for documentation. >>> Perhaps it should be raised for consideration for Pharo 7? >>> >>> Actually you stimulate my thoughts that the Help file might be a >>> better place for such snippets, >>> so they are always with the image, and don't need to be retyped. Any >>> objections? >>> >>> cheers -ben >>> >>> On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >>> > Ben, >>> > >>> > I think there is a deeper need here. Writing good document is hard and >>> > keeping it in sync with code is harder still. >>> > >>> > A book/booklet separates content from the code and being frozen in time >>> > faces obsolescence. I would prefer to see a guidebook framework in >>> Pharo >>> > that every package author can use to create a simple narrative on its >>> > features. Package authors and consumers have an incentive to keep the >>> code >>> > and content in sync. If an Object is a recursion on the notion of a >>> > computer, why not provide, say a Note, as a recursive simplification >>> of a >>> > book? >>> > >>> > The framework could be on the lines of Plugins, Tests. E.g. >>> > >>> > Package-Core >>> > Package-Plugins >>> > Package-Tests >>> > *Package-Guide* >>> > >>> > The guide framework should support active code (say to pop the source >>> code >>> > for a method), active links to guides on which this package depends, >>> > automatic generation of table of contents, index of class references. >>> Most >>> > of features already exists in Pharo but spread all over. They need a >>> home. >>> > >>> > A package could also extend this basic framework with features (e.g. >>> PDF >>> > package could export articles to PDF, Zinc could generate HTML). >>> > >>> > Regards .. Subbu >>> > >>> > >>> > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: >>> >> >>> >> I've seen a few requests for short bits of code to use in playground >>> for >>> >> a demo presentation. I wonder if it would be good to have a booklet >>> to >>> >> gather these - seeded with Sven's excellent article... >>> >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 >>> >> >>> >> It could include the recent meta-programming scripts like searching >>> for >>> >> all class instance variables starting with a capital letter. >>> >> >>> >> The book might be named "Snippets", in a format presentable to laser >>> >> print on-site - something physical for attendees to take away with >>> them >>> >> to quick demo to others back in their office. >>> >> >>> >> I can take the lead in setting it up. Anyone remember any relevant >>> >> posts in our archives? >>> >> >>> >> cheers -ben >>> > >>> > >>> > >>> >>> >> >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Ben Coman

On Thu, May 25, 2017 at 9:32 PM, askoh <askoh(a)askoh.com> wrote: > You gave me an idea. > > Since Test Driven Design insists all tests passes before release, we can > piggy back on that by insisting Tutorials, Demos, Examples be tests that > must pass before release. Can we design Tutorials, Demos, Examples like > tests? I think so. > So TDDoc? cheers -ben

May 25, 2017

Re: [Pharo-dev] multiple crashes on macOS Sierra

by Stephane Ducasse

It happened to me too. On Thu, May 25, 2017 at 12:17 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > For me the Bloc image on Ubuntu Linux 14.04 LTS never reopened back. > > All I get is a black screen. > > Damn. > > > Phil > > On Thu, May 25, 2017 at 9:34 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> Hi doru >> >> Yes I get the same. Now I was also in the bloc image, I got crash when >> resizing the host window. >> >> Stef >> >> On Wed, May 24, 2017 at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Hi, >>> >>> Today I experienced multiple crashes on macOS Sierra. >>> >>> These happened during regular programming, mostly while typing code. I >>> attached here the crash dump(s). I believe I heard Phil having the same >>> issue with the stable Pharo VM. >>> >>> Does anyone else has the same issue? >>> >>> The VM is: >>> CoInterpreter VMMaker.oscog-eem.2203 uuid: 12d4afae-8498-4e76-8efe-60eba6ef4db2 >>> May 2 2017 >>> StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid: >>> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May 2 2017 >>> VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git >>> $ Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552 >>> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ >>> >>> The Pharo update number is: 60482 >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "From an abstract enough point of view, any two things are similar." >>> >>> >>> >>> >> >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Stephane Ducasse

What I would like is to extend pillar with a special environment [[[testable=5 3+ 2 ]]] and also [[[screenshot: 10@200 named: 'browserOpen' Browser open ]]] Now I need help on pillar. Stef On Thu, May 25, 2017 at 3:57 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > What I'm doing is > - extracting a subset of pillar > - doc + renderer > - so that we can use it in the image. > Now kasper did a first version (in the repository and if people want to > have a look it will help) > - now I'm remaving the dependency on magritte. > > Stef > > On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> Nice idea. I've seen vague discussion about getting Pillar into the >> standard image for documentation. >> Perhaps it should be raised for consideration for Pharo 7? >> >> Actually you stimulate my thoughts that the Help file might be a >> better place for such snippets, >> so they are always with the image, and don't need to be retyped. Any >> objections? >> >> cheers -ben >> >> On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> > Ben, >> > >> > I think there is a deeper need here. Writing good document is hard and >> > keeping it in sync with code is harder still. >> > >> > A book/booklet separates content from the code and being frozen in time >> > faces obsolescence. I would prefer to see a guidebook framework in Pharo >> > that every package author can use to create a simple narrative on its >> > features. Package authors and consumers have an incentive to keep the >> code >> > and content in sync. If an Object is a recursion on the notion of a >> > computer, why not provide, say a Note, as a recursive simplification of >> a >> > book? >> > >> > The framework could be on the lines of Plugins, Tests. E.g. >> > >> > Package-Core >> > Package-Plugins >> > Package-Tests >> > *Package-Guide* >> > >> > The guide framework should support active code (say to pop the source >> code >> > for a method), active links to guides on which this package depends, >> > automatic generation of table of contents, index of class references. >> Most >> > of features already exists in Pharo but spread all over. They need a >> home. >> > >> > A package could also extend this basic framework with features (e.g. PDF >> > package could export articles to PDF, Zinc could generate HTML). >> > >> > Regards .. Subbu >> > >> > >> > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: >> >> >> >> I've seen a few requests for short bits of code to use in playground >> for >> >> a demo presentation. I wonder if it would be good to have a booklet to >> >> gather these - seeded with Sven's excellent article... >> >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 >> >> >> >> It could include the recent meta-programming scripts like searching for >> >> all class instance variables starting with a capital letter. >> >> >> >> The book might be named "Snippets", in a format presentable to laser >> >> print on-site - something physical for attendees to take away with them >> >> to quick demo to others back in their office. >> >> >> >> I can take the lead in setting it up. Anyone remember any relevant >> >> posts in our archives? >> >> >> >> cheers -ben >> > >> > >> > >> >> >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by Stephane Ducasse

What I'm doing is - extracting a subset of pillar - doc + renderer - so that we can use it in the image. Now kasper did a first version (in the repository and if people want to have a look it will help) - now I'm remaving the dependency on magritte. Stef On Thu, May 25, 2017 at 2:03 PM, Ben Coman <btc(a)openinworld.com> wrote: > Nice idea. I've seen vague discussion about getting Pillar into the > standard image for documentation. > Perhaps it should be raised for consideration for Pharo 7? > > Actually you stimulate my thoughts that the Help file might be a > better place for such snippets, > so they are always with the image, and don't need to be retyped. Any > objections? > > cheers -ben > > On Thu, May 25, 2017 at 4:00 PM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > > Ben, > > > > I think there is a deeper need here. Writing good document is hard and > > keeping it in sync with code is harder still. > > > > A book/booklet separates content from the code and being frozen in time > > faces obsolescence. I would prefer to see a guidebook framework in Pharo > > that every package author can use to create a simple narrative on its > > features. Package authors and consumers have an incentive to keep the > code > > and content in sync. If an Object is a recursion on the notion of a > > computer, why not provide, say a Note, as a recursive simplification of a > > book? > > > > The framework could be on the lines of Plugins, Tests. E.g. > > > > Package-Core > > Package-Plugins > > Package-Tests > > *Package-Guide* > > > > The guide framework should support active code (say to pop the source > code > > for a method), active links to guides on which this package depends, > > automatic generation of table of contents, index of class references. > Most > > of features already exists in Pharo but spread all over. They need a > home. > > > > A package could also extend this basic framework with features (e.g. PDF > > package could export articles to PDF, Zinc could generate HTML). > > > > Regards .. Subbu > > > > > > On Thursday 25 May 2017 07:03 AM, Ben Coman wrote: > >> > >> I've seen a few requests for short bits of code to use in playground for > >> a demo presentation. I wonder if it would be good to have a booklet to > >> gather these - seeded with Sven's excellent article... > >> https://medium.com/concerning-pharo/elegant-pharo-code-bb590f0856d0 > >> > >> It could include the recent meta-programming scripts like searching for > >> all class instance variables starting with a capital letter. > >> > >> The book might be named "Snippets", in a format presentable to laser > >> print on-site - something physical for attendees to take away with them > >> to quick demo to others back in their office. > >> > >> I can take the lead in setting it up. Anyone remember any relevant > >> posts in our archives? > >> > >> cheers -ben > > > > > > > >

May 25, 2017

Re: [Pharo-dev] Booklet suggestion

by askoh

You gave me an idea. Since Test Driven Design insists all tests passes before release, we can piggy back on that by insisting Tutorials, Demos, Examples be tests that must pass before release. Can we design Tutorials, Demos, Examples like tests? I think so. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Booklet-suggestion-tp4948195p4948263.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 25, 2017