Re: [Pharo-dev] Why RBComment is not RBCommentNode?

[ducasse]

> On 31 Jan 2019, at 20:59, Manuel Leuenberger  wrote:
> 
> +1
> 
> This would also help with the auto-formatter. This guy seems to put comments 
> wherever it likes to put it.

I’m slowly working on tests and a new formatter but I got distracted. 
If someone wants to help let me know. The code is in mybecher/BlueInk on my 
github account. 
https://github.com/Ducasse/mybecher

I would like to be able to really use it to reformat all Pharo 
But it will take time because I’m eaten by admin.

Stef

>> On 31 Jan 2019, at 20:57, ducasse  wrote:
>> 
>> 
>> Hi
>> 
>> In my journey in Pharo AST node I found RBComment and it is not a Node and I 
>> wonder why. 
>> To me RBComment should be a subclass of RBProgramNode and renamed 
>> RBCommentNode.
>> 
>> Stef
>> 
> 
> 

Re: [Pharo-dev] Why RBComment is not RBCommentNode?

[Manuel Leuenberger]

+1

This would also help with the auto-formatter. This guy seems to put comments 
wherever it likes to put it.

> On 31 Jan 2019, at 20:57, ducasse  wrote:
> 
> 
> Hi
> 
> In my journey in Pharo AST node I found RBComment and it is not a Node and I 
> wonder why. 
> To me RBComment should be a subclass of RBProgramNode and renamed 
> RBCommentNode.
> 
> Stef
> 

[Pharo-dev] Why RBComment is not RBCommentNode?

[ducasse]

Hi

In my journey in Pharo AST node I found RBComment and it is not a Node and I 
wonder why. 
To me RBComment should be a subclass of RBProgramNode and renamed RBCommentNode.

Stef

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

[Torsten Bergmann]

 
[ Pharo current ] fork

[Pharo-dev] DuplicatedSlotName empty pre-debugger

[Hernán Morales Durand]

Hi,

When loading OpenPonk in Pharo 7, I have a duplicated slot name entry
pre-debugger window but is empty (see attachment). Is this behavior
well-known or on purpose?
Cheers,

Hernán

Re: [Pharo-dev] Debugger opening on user halt and not Object>>halt

[Ben Coman]

On Thu, 31 Jan 2019 at 17:15, Guillermo Polito 
wrote:

> Hi Thomas,
>
> Check the pragma debuggerCompleteToSender and its users. I think it's
> related to that.
> BenComan probably can give a better insight since (if I recall correctly)
> he introduced it?
>

Thats right.  Use "Tools > Finder > Source" to search for...
debuggerCompleteToSender
ignoring where its a pragma.

That leaves...
  Process>>complete:
  Process>>stepToHome:
  GTGenericStackDebugger>>filteredStack
  GTGenericStackDebugger>>setDebuggerToFirstNonFilteredContext

The first was me. Not sure about the second. The latter two were someone
else.



> Guille
>
> On Wed, Jan 30, 2019 at 5:44 PM Thomas Dupriez <
> tdupr...@ens-paris-saclay.fr> wrote:
>
>> Hello,
>>
>> Does someone know which is the code responsible for the debugger opening
>> on the halt of the user instead of Object>>halt (see picture)? It's neat
>> but it's not the regular behaviour so I'm guessing it is handled somewhere
>> specifically for halt messages?
>>
>
Its not just for halt, but for any method that you don't want the debugger
opening in the method sending #signal.
Is your snapshot based on modified code? In
Pharo-7.0.1+build.146.sha.c48755acc5f489337be0e7abc882c15b1707b254 (32 Bit)
in Playground I evaluate...
1 + 1.
self halt.
2 + 2.
and my top line is the same as your second line.

cheers -ben

[Pharo-dev] [Pharo 8.0] Build #47: 2381 Add class comment to ManifestCodeImportCommandLineHandlers

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #47 was: SUCCESS.

The Pull Request #2382 was integrated: "2381 Add class comment to 
ManifestCodeImportCommandLineHandlers"
Pull request url: https://github.com/pharo-project/pharo/pull/2382

Issue Url: https://pharo.fogbugz.com/f/cases/2381
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/47/

[Pharo-dev] [Pharo 8.0] Build #46: 2423-Rename-selection-methods-of-FastTable-to-remove-the-row-in-names

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!
  
The status of the build #46 was: SUCCESS.

The Pull Request #2424 was integrated: 
"2423-Rename-selection-methods-of-FastTable-to-remove-the-row-in-names"
Pull request url: https://github.com/pharo-project/pharo/pull/2424

Issue Url: https://pharo.fogbugz.com/f/cases/2423
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/46/

Re: [Pharo-dev] Debugger opening on user halt and not Object>>halt

[Guillermo Polito]

Hi Thomas,

Check the pragma debuggerCompleteToSender and its users. I think it's
related to that.
BenComan probably can give a better insight since (if I recall correctly)
he introduced it?

Guille

On Wed, Jan 30, 2019 at 5:44 PM Thomas Dupriez 
wrote:

> Hello,
>
> Does someone know which is the code responsible for the debugger opening
> on the halt of the user instead of Object>>halt (see picture)? It's neat
> but it's not the regular behaviour so I'm guessing it is handled somewhere
> specifically for halt messages?
>
>
> Thomas
>


-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
*


*Web:* *http://guillep.github.io* 

*Phone: *+33 06 52 70 66 13

Re: [Pharo-dev] [ANN] Pharo open documentation

[Hernán Morales Durand]

Hi Norbert,

If you like to get a list of projects in the catalog (through CLI) have a
look at https://github.com/hernanmd/pi/tree/dev
Cheers,

Hernán


El jue., 31 ene. 2019 a las 5:13, Norbert Hartl ()
escribió:

> Very good initiative! Did you talk about the catalog, too? This list
> somehow mirrors the catalog. And as it is done in markdown it does not
> easily work as a parsable document, does it?
>
> Norbert
>
>
> > Am 30.01.2019 um 15:00 schrieb Cyril Ferlicot  >:
> >
> > Hi everyone!
> >
> > With some other members of the community we are proud to announce a
> > new effort on Pharo documentation.
> >
> > We launched an organization pharo-open-documentation which is a
> > user-maintained documentation related to Pharo environment, language,
> > and libraries.
> >
> > Currently it has three main projects:
> > - pharo-wiki : Wiki related to the Pharo programming language and
> environment.
> > - awesome-pharo : A collection of awesome Pharo libraries, tools,
> > frameworks and software. We want to make this project a reference in
> > https://github.com/sindresorhus/awesome
> > - awesome-pharo-ml : List of projects, books, booklets, papers, and
> > applications related to machine learning, AI, data science in Pharo.
> >
> > Contributions are welcomed!
> >
> > If you own a cool project in Pharo others could use in their own
> > projects, send us a PR to awesome-pharo!
> > If you have knowledge on Pharo or projects of Pharo, we would be glad
> > if you could contribute to the pharo-wiki! Don't forget to read the
> > contribution guidelines. ;)
> >
> > We opened a Twitter to announce new entries on the pharo-wiki.
> >
> > https://twitter.com/PharoOpen
> >
> > Have a nice day!
> >
> > --
> > Cyril Ferlicot
> > https://ferlicot.fr
> >
>
>
>

Re: [Pharo-dev] [ANN] Pharo open documentation

[Norbert Hartl]

Very good initiative! Did you talk about the catalog, too? This list somehow 
mirrors the catalog. And as it is done in markdown it does not easily work as a 
parsable document, does it?

Norbert


> Am 30.01.2019 um 15:00 schrieb Cyril Ferlicot :
> 
> Hi everyone!
> 
> With some other members of the community we are proud to announce a
> new effort on Pharo documentation.
> 
> We launched an organization pharo-open-documentation which is a
> user-maintained documentation related to Pharo environment, language,
> and libraries.
> 
> Currently it has three main projects:
> - pharo-wiki : Wiki related to the Pharo programming language and environment.
> - awesome-pharo : A collection of awesome Pharo libraries, tools,
> frameworks and software. We want to make this project a reference in
> https://github.com/sindresorhus/awesome
> - awesome-pharo-ml : List of projects, books, booklets, papers, and
> applications related to machine learning, AI, data science in Pharo.
> 
> Contributions are welcomed!
> 
> If you own a cool project in Pharo others could use in their own
> projects, send us a PR to awesome-pharo!
> If you have knowledge on Pharo or projects of Pharo, we would be glad
> if you could contribute to the pharo-wiki! Don't forget to read the
> contribution guidelines. ;)
> 
> We opened a Twitter to announce new entries on the pharo-wiki.
> 
> https://twitter.com/PharoOpen
> 
> Have a nice day!
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
>