Re: [Pharo-dev] Character encoding and line ending in OSSubprocess

Hi Nico, I am on holidays now, so my answer will be short. I would like to provide some encoding facility if you think if may make sense to provide that at that level. This issue is the second time it appeared, that's why I am asking. Whenever you make the PR, can I see the changes and see if I

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

Branch: refs/tags/60191 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] 46ae65: 60191

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 46ae6557594467c838b7b75baa52bbe399eb2072 https://github.com/pharo-project/pharo-core/commit/46ae6557594467c838b7b75baa52bbe399eb2072 Author: Jenkins Build Server Date:

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

Hi nicolai I remember that I read everything and fix typos. Did you got my review or did I suuceed to lose it ;). Stef Le 6/8/16 à 15:24, Nicolai Hess a écrit : 2016-07-28 16:18 GMT+02:00 stepharo >: I will! I love to read nice

[Pharo-dev] About better communication in the community

Hi guys the board got a good discussion at ESUG about how to improve and a lot of the discussion turned around improving communication. We got some ideas that we will propose soon but I would like to get *your* ideas. If you have idea about improving communication around pharo please tell

[Pharo-dev] About Pharo 60

Hi We have some ideas (because people are working on items) for the Pharo 6 roadmap and we will consolidate them soon and propose them to you. but I would like to know two kinds of points - what are the points you are working on and that would deserve more focus and help from the

Re: [Pharo-dev] About PythonDocTest for Pharo

Ok this is your taste. My reality is different. Tests are far far away. I do not see them. They live in a different time zone. They are smart have a boring setup. I want documentation in front on my nose. No extra thinking no extra click Just right there. Stef Le 18/8/16 à 23:14, Denis

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

2016-08-06 15:24 GMT+02:00 Nicolai Hess : > > > 2016-07-28 16:18 GMT+02:00 stepharo : > >> I will! >> >> I love to read nice comments >> >> Stef >> >> > I updated the slice and added some more example (much more is needed but I > think it is better than

Re: [Pharo-dev] About PythonDocTest for Pharo

I am sorry, but I want to said it: we have tests. Why tests are not for same purpose? (I would say they include it). As Tudor said: "they are way too disconnected from the code" And this needs to be solved. We already have nice feature in Nautilus: it shows "test icon" on covered

Re: [Pharo-dev] About better communication in the community

Hi Stef, Good communication implies being clear when writing about sensitive topics, especially when communicating through virtual channels. I am not in Europe, so I cannot discuss these things with you face to face. Therefore is not clear to me (and others) what are your policies in many

Re: [Pharo-dev] About PythonDocTest for Pharo

On Thu, Aug 18, 2016 at 11:28 PM, Denis Kudriashov wrote: > > 2016-08-18 13:32 GMT+02:00 stepharo : > >> withExtension: aString >> >> "Returns a new file reference with a different file extension" > > > Does this comment is really needed? > I only see

Re: [Pharo-dev] Character encoding and line ending in OSSubprocess

On Mon, Aug 22, 2016 at 4:29 PM, Thierry Goubier wrote: > > > 2016-08-22 16:08 GMT+02:00 Nicolas Passerini : > >> >> On Mon, Aug 22, 2016 at 3:31 PM, Thierry Goubier < >> thierry.goub...@gmail.com> wrote: >> >>> does this happens when you are

Re: [Pharo-dev] /

I will probably sound stupid but here I go. I am no fan of Pragmas. I feel that their syntax is weird and unnecessary and what they do can be easily achieved with a secondary class that provides this meta data. In case of examples it would have been possible to have examples in a separate