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

[pharo-project/pharo-core] e4e322: 60044

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: e4e322ff92cc57f6c8ecad4b911e18246e9447bf https://github.com/pharo-project/pharo-core/commit/e4e322ff92cc57f6c8ecad4b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-30 (Mon, 30 May 2016) Changed paths: A AST-Core.package/RBKeywordToken.class/instance/testing/isPrimitiveKeyword.st M AST-Core.package/RBParser.class/instance/private-parsing/parsePragmaLiteral.st A AST-Core.package/RBParser.class/instance/private-parsing/parsePrimitiveKeywordPragma.st A AST-Core.package/RBToken.class/instance/testing/isPrimitiveKeyword.st A AST-FFI-Pharo50Compatibility.package/extension/RBKeywordToken/instance/isExternalFunctionKeyword.st M AST-FFI-Pharo50Compatibility.package/extension/RBParser/instance/basicParsePragma.st A AST-FFI-Pharo50Compatibility.package/extension/RBToken/instance/isExternalFunctionKeyword.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testPragmaConstantLiteralArgument.st M AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testPragmas.st M AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testPrimitives.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60043.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60044.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60043.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60044.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60044 17696 RBParser should not allow variable names for pragma arguments https://pharo.fogbugz.com/f/cases/17696 http://files.pharo.org/image/60/60044.zip

May 30, 2016

[pharo-project/pharo-core]

by GitHub

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

May 30, 2016

[pharo-project/pharo-core] 3cd1b4: 60043

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 3cd1b427b40b18ba17bf26644d1e045f1ab27ae6 https://github.com/pharo-project/pharo-core/commit/3cd1b427b40b18ba17bf2664… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-05-30 (Mon, 30 May 2016) Changed paths: M Multilingual-TextConversion.package/ByteTextConverter.class/definition.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60042.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60043.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60042.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60043.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/MessageBrowser.class/instance/text selection/autoSelect_.st Log Message: ----------- 60043 18329 Make MessageBrowser work for CompiledMethods and RGMethodDefinitions https://pharo.fogbugz.com/f/cases/18329 18300 Nautilus does not warn about unaccepted changes in comment pane https://pharo.fogbugz.com/f/cases/18300 18196 ByteTextConverter uses EventSensorConstants https://pharo.fogbugz.com/f/cases/18196 http://files.pharo.org/image/60/60043.zip

May 30, 2016

Re: [Pharo-dev] Komitter SubscriptOutOfBounds: 1

by stepharo

Hi hernan do you have a reproducible scenario because I cannot reproduce it? The problem we got before was that Komitter was publishing the previous version :( Stef Le 30/5/16 Ã 00:13, HernÃ¡n Morales Durand a Ã©crit : > In Pharo 5.0 #50759 on Windows, whenever I try to commit any change > through Versionner, an exception SubscriptOutOfBounds raise and then > the package modification mark is lost. > > Is this bug reported? > Screenshot attached. > > HernÃ¡n >

May 30, 2016

Re: [Pharo-dev] Komitter SubscriptOutOfBounds: 1

by Cyril Ferlicot D.

Le 30/05/2016 00:13, HernÃ¡n Morales Durand a Ã©crit : > In Pharo 5.0 #50759 on Windows, whenever I try to commit any change > through Versionner, an exception SubscriptOutOfBounds raise and then the > package modification mark is lost. > > Is this bug reported? > Screenshot attached. > > HernÃ¡n > Hi, I tried and before I could commit I got a MNU receiver of #selectMorphList is nil. I got it in Windows 7 in Pharo6.0 Latest update: #60042 when I unselected a change. http://puu.sh/p9C9b/3e8fe7787c.png -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

May 29, 2016

Komitter SubscriptOutOfBounds: 1

by HernÃ¡n Morales Durand

In Pharo 5.0 #50759 on Windows, whenever I try to commit any change through Versionner, an exception SubscriptOutOfBounds raise and then the package modification mark is lost. Is this bug reported? Screenshot attached. HernÃ¡n

May 29, 2016

Re: [Pharo-dev] File List -- MNU: RubTextEditor>>doIt

by HernÃ¡n Morales Durand

In Windows if you select a file with Smalltalk code and right click you get MessageNotUnderstood: FileList class>>allRegisteredServices without menu at all. I think you have to open a Workspace with contents and then you can evaluate. I don't see any "do-it" right clicking on the file from the FileList. Cheers, HernÃ¡n 2016-05-18 2:42 GMT-03:00 Martin McClure <martin(a)hand2mouse.com>: > So I open Pharo 5, and the *very* *first* thing I do is to open a file > list, select a file that contains the Metacello expression to load my > project, and select "Do it" from the menu. > > And get MNU: RubTextEditor>>doIt > > :-( > > This was on Linux, in case that makes a difference. > > I couldn't quickly track down how this is *supposed* to work. > > Regards, > > -Martin > >

May 29, 2016

Re: [Pharo-dev] lineConversion for WriteStream

by stepharo

Yes we should probably migrate to LF and I would also go a for newer stream library. Stef >> Well, STONWriter, NeoJSONWriter and NeoCSVWriter allow you to set the line end convention, you are not alone in wanting the standard unix line end. > So why don't we do it? > > CR does seem a major legacy [1] ... Early Mac OS up to version 9; > Commodore 8-bit machines, Acorn BBC, ZX Spectrum, TRS-80, Apple II > family, Oberon, MIT Lisp Machine and OS-9 > > I read [2] its a "non-issue with windows 7. Just use unix-newlines. > The only application (of the few tested) I have found which does not > understand unix-newlines as newlines is the useless notepad. For > instance it seems the following applications understand unix-newlines > just fine in windows 7: cmd scripts; powershell scripts; word 2013 (I > can open a txt file with unix-newlines, though I never use that, I can > also paste text with unix-newlines and get correct/desired line > breaking) ; OneNote 2013 (pasting text) ; wordpad (not that I use it) > ; Sublime Text 3 (naturally, just on the list because it the best; > Eclipse." > > And now Microsoft is taking small steps towards a Linux desktop ;) [3] [4] > > So it looks to me like LF wins! > It may take a while and some effort, but can we agree on a three point strategy? > 1. Default CR line ending must change! > 2. Change it to LF. > 3. Default auto-conversion of "text" input to LF? > > [1] https://en.wikipedia.org/wiki/Newline#History > [2] https://blog.codinghorror.com/the-great-newline-schism/ > [3] http://www.zdnet.com/article/microsoft-and-canonical-partner-to-bring-ubunt… > [4] https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspa… > > cheers -ben > >>> Anyway; this is not system-breaking problem, just annoying. >>> >>> Peter >>> >>> On Thu, May 26, 2016 at 2:50 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> On 26 May 2016, at 14:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> >>>> >>>> >>>> On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> On 26 May 2016, at 13:29, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>> >>>>>> In general I would say that you should write either something platform specific or you write something specific >>>>> Except that I cannot do that because the system doesn't support neither. >>>>> And the fact that the default line ending is CR is just bullshitâ¦ it's 2016, not 1986. >>>> Yes, that CR is from days long gone ;-) >>>> >>>>> or #cr #lf or #crlf as needed, and/or make that last one a parameter (OSPlatform current lineEnding). >>>> I am piping unknown content into the file, thus the need for `lineEndConvention:` and the reason of this entire thread. So as I said, the system doesn't support it. >>>> I know I can use #lf or whatnot, but I am not creating the content, I am saving it. >>>> >>>> Peter >>> Well, maybe I don't understand your use case, but if you do not know what is inside, why not save it as is, binary even, not doing any conversions ? >>> >>> >>> >> >

May 29, 2016

Re: [Pharo-dev] lineConversion for WriteStream

by Sven Van Caekenberghe

> On 27 May 2016, at 05:07, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, May 27, 2016 at 2:30 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> On 26 May 2016, at 20:20, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> Well I was saving e.g. STON or XML fileâ¦ but some apps outside didn't particularly like itâ¦ even `cat` doesn't like CR. >> >> Well, STONWriter, NeoJSONWriter and NeoCSVWriter allow you to set the line end convention, you are not alone in wanting the standard unix line end. > > So why don't we do it? > > CR does seem a major legacy [1] ... Early Mac OS up to version 9; > Commodore 8-bit machines, Acorn BBC, ZX Spectrum, TRS-80, Apple II > family, Oberon, MIT Lisp Machine and OS-9 > > I read [2] its a "non-issue with windows 7. Just use unix-newlines. > The only application (of the few tested) I have found which does not > understand unix-newlines as newlines is the useless notepad. For > instance it seems the following applications understand unix-newlines > just fine in windows 7: cmd scripts; powershell scripts; word 2013 (I > can open a txt file with unix-newlines, though I never use that, I can > also paste text with unix-newlines and get correct/desired line > breaking) ; OneNote 2013 (pasting text) ; wordpad (not that I use it) > ; Sublime Text 3 (naturally, just on the list because it the best; > Eclipse." > > And now Microsoft is taking small steps towards a Linux desktop ;) [3] [4] > > So it looks to me like LF wins! > It may take a while and some effort, but can we agree on a three point strategy? > 1. Default CR line ending must change! > 2. Change it to LF. > 3. Default auto-conversion of "text" input to LF? Yes, why not. I believe they did the same in Cuis years ago, switched the whole image, all defaults and source code from #cr to #lf and never looked back. You made a good argument, #cr on itself is obsolete, and if Windows users can live with it, there is no longer any reason not to choose for #lf. > [1] https://en.wikipedia.org/wiki/Newline#History > [2] https://blog.codinghorror.com/the-great-newline-schism/ > [3] http://www.zdnet.com/article/microsoft-and-canonical-partner-to-bring-ubunt… > [4] https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspa… > > cheers -ben > >> >>> Anyway; this is not system-breaking problem, just annoying. >>> >>> Peter >>> >>> On Thu, May 26, 2016 at 2:50 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>>> On 26 May 2016, at 14:06, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> >>>> >>>> >>>> On Thu, May 26, 2016 at 1:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>>> On 26 May 2016, at 13:29, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>> >>>>>> In general I would say that you should write either something platform specific or you write something specific >>>>> >>>>> Except that I cannot do that because the system doesn't support neither. >>>>> And the fact that the default line ending is CR is just bullshitâ¦ it's 2016, not 1986. >>>> >>>> Yes, that CR is from days long gone ;-) >>>> >>>>> or #cr #lf or #crlf as needed, and/or make that last one a parameter (OSPlatform current lineEnding). >>>> >>>> I am piping unknown content into the file, thus the need for `lineEndConvention:` and the reason of this entire thread. So as I said, the system doesn't support it. >>>> I know I can use #lf or whatnot, but I am not creating the content, I am saving it. >>>> >>>> Peter >>> >>> Well, maybe I don't understand your use case, but if you do not know what is inside, why not save it as is, binary even, not doing any conversions ? >>> >>> >>> >> >> >

May 28, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] d2bfc7: 60040

by Ben Coman

Epic! I look forward to trying it out. cheers -ben On Fri, May 27, 2016 at 8:17 PM, Max Leske <maxleske(a)gmail.com> wrote: > This is the Video from ESUG 2014 where Martin Dias presented Epicea first: > https://youtu.be/Wr1IenGfT0I?t=9m20s > > Cheers, > Max > > On 27 May 2016, at 14:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Friday, 27 May 2016, GitHub <noreply(a)github.com> wrote: >> >> Branch: refs/heads/6.0 >> Home: https://github.com/pharo-project/pharo-core > > > Could we have a mail explaining what it is, what it does, how to use it ? :) > Because everyone don't follow all mails and even following mails might not > know how to use it. > Thank you :) > > From my phone, Cyril > > > -- > Cheers > Cyril Ferlicot > >

May 27, 2016