- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by stephan

On 08-11-17 22:03, Stephane Ducasse wrote: > File @ /Users/ducasse/Documents/Pharo/vms/70-x86/Pharo.app/Contents/MacOS Yes, this is looks like one of the problems I have with PharoLauncher directories. It is unclear to me what is kept with the vm and what with the image. I asked about it in users Stephan

Nov. 8, 2017

Re: [Pharo-dev] LayoutFrame bug

by Stephane Ducasse

Hi nicolas Tx I fixed it before seeing your email. Too bad. I introduced this bug when I did the asLayoutFrame conversion. Note that I split the refactoring in parts to avoid too change commits. Now I was also thinking how I could automate the change and this is not that easy because the expressions can use temps, instance variables... and it would take me age to be able to write a rewrite expression (sadly enough). I found it in 3 min because I know the changes I did but your way is quite nice because it was not easy to find from the stack trace. I fixed it but I cannot commit the fix. Iceberg does not let me. Now I cannot produce a PR. :( https://pharo.fogbugz.com/f/cases/20656/Nautilus-comment-panel-got-broken-b… Guille told me that I could modify the printOn: method to help me. And this is a bit better (I did not bother to be smart with ; or not) I will use this trick to ease the refactoring and minimize errors (probably sleeping more should help too and doing less boring tasks too :). printOn: aStream aStream nextPutAll: ' (LayoutFrame identity '. self leftFraction = 0 ifFalse: [ aStream << ('leftFraction: ', self leftFraction printString, ' ') ]. self topFraction = 0 ifFalse: [ aStream << ('topFraction: ', self topFraction printString, ' ') ]. self rightFraction = 1 ifFalse: [ aStream << ('rightFraction: ', self rightFraction printString, ' ') ]. self bottomFraction = 1 ifFalse: [ aStream << ('bottomFraction: ', self bottomFraction printString,' ') ]. self leftOffset = 0 ifFalse: [ aStream << ('leftOffset: ', self leftOffset printString,' ') ]. self topOffset = 0 ifFalse: [ aStream << ('topOffset: ', self topOffset printString,' ') ]. self rightOffset = 0 ifFalse: [ aStream << ('rightOffset: ', self rightOffset printString,' ') ]. self bottomOffset = 0 ifFalse: [ aStream << ('bottomOffset: ', self bottomOffset printString,' ') ]. aStream nextPutAll: ' ) ' On Wed, Nov 8, 2017 at 1:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yeah, I just got in trouble too by looking at class comments. > > Heroic debugging, Nicolas ! > >> On 8 Nov 2017, at 13:47, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >> Hi, >> don't you get nice red-cross when opening a browser and selecting comment? >> (Pharo7.0-32bit-b5ec533.image) >> >> The problem is LayoutFrame having a Point instead of Number in fraction/offset inst. var. >> >> So I defined two horrible hacks in order to be able to work with Pharo >> >> Point>>@ n ^x @ n >> Point>>asInteger ^x asInteger >> >> then could instrument the LayoutFrame inst. var. setters with horrible checks like: >> aNumber isNumber ifFalse: [ self halt]. >> >> And after a few seconds of IDE usage: >> >> AbstractNautilusUI>>buildCodePanelWithCommentOnRight >> ...snip... >> sourceCodePanel >> addMorph: commentWidget >> fullFrame: (LayoutFrame identity leftFraction: 0.5@0 ; >> leftOffset: delta). >> >> Huh! it's as pleasant as not eating own dog food >> I think this comes from a recent refactoring. I can hardly use in image tools to trace it. >> Iceberg bugs, MC has lost ancestry and is just good at synchronizing disk working copy with image working copy, but there is github & git API: >> >> https://github.com/pharo-project/pharo/commit/042baad47fddb63db2dd0beefeec6… >> >> As it's nearly impossible to make giant refactorings like this without human error, >> and as it's as impossible to review pull request with many lines of code, >> I wonder if it is possible to automate those with rewrite rules... >> >> I let you finish the work (open issue, patch, commit, etc...) >> >> > >

Nov. 8, 2017

Re: [Pharo-dev] Critics; as yet unclassified

by Stephane Ducasse

No overloading :) On Wed, Nov 8, 2017 at 3:40 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > case of blindness > > 2017-11-08 15:37 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >> Hi Nicolas. >> >> It exists for methods. If you select unclassified method in Nautilus you >> will see "unclassified methods" in critiques bottom pane. >> >> 2017-11-08 15:12 GMT+01:00 Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com>: >>> >>> Is there or could we create a code critic for 'as yet unclassified'? >> >> >

Nov. 8, 2017

Re: [Pharo-dev] [IMPORTANT] Is there a bug in Tonel with category:

by Sven Van Caekenberghe

> On 8 Nov 2017, at 21:29, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Sven > > I understand but it is SUPER strange to save the code in a format that > does not respect the syntax of the language. > I think that we should write a parser for the class definition or save > category as strings. > > I do not want to have to explain to people. Yes and no this is not the > pharo syntax. > > Sorry I'm fed up. Tonel is a mix of different formats. Parts are custom to Tonel (the overall structure), parts are Pharo syntax (the method's source code), parts are STON (the contents of the meta data sections). Even if we make a change to how the Symbols are represented, it would still not make the meta sections Pharo syntax. But I do agree it is a bit confusing. Either we make them all Strings, or I could add an option to STON that allows STONWriter to control what constitutes a 'simple' or 'literal' Symbol. And we could err on the safe side (like only allow 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789'), because I dare you to look at String>>#isLiteralSymbol it is way more ugly than STON's simple definition (which allows all characters from 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_./'). What is the opinion of the original Tonel designers ? > Stef > > On Mon, Nov 6, 2017 at 10:25 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 6 Nov 2017, at 20:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> Esteban told me that this is because he uses STON for the class definition. >>> Now a simple question may be we could use a string instead of a symbol >>> because this is strange >>> to have a class definitino that does not respect Pharo syntax. >> >> It might be a bit confusing at first sight, but it is correct, IMHO. >> >> It is STON syntax, not Pharo. >> >> Yes, STON is a bit more liberal with Symbols than normal Smalltalk, but it is totally consistent with itself. >> >> STON fromString: (STON toString: #'My Strange Symbol'). >> STON fromString: (STON toString: #'foo-bar'). >> >> If a Symbol consists only of characters in 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789-_./' then the Symbol does not need to be quoted in STON. >> >> I see no problem there. >> >>> Stef >>> >>> On Mon, Nov 6, 2017 at 8:15 PM, Dale Henrichs >>> <dale.henrichs(a)gemtalksystems.com> wrote: >>>> >>>> >>>> On 11/06/2017 08:23 AM, Sven Van Caekenberghe wrote: >>>>> >>>>> >>>>>> On 6 Nov 2017, at 17:13, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> On 11/6/17 7:07 AM, Sven Van Caekenberghe wrote: >>>>>>>> >>>>>>>> On 6 Nov 2017, at 15:43, Dale Henrichs >>>>>>>> <dale.henrichs(a)gemtalksystems.com> wrote: >>>>>>>> >>>>>>>> of course with Pharo's implementation of Symbol it is not practical to >>>>>>>> use asString nor type checks - things that are not necessary in other >>>>>>>> Smalltalk implementations >>>>>>> >>>>>>> How so ? >>>>>>> >>>>>>> What is the problem with Symbol>>#asString ? >>>>>> >>>>>> I am not going to go to every field in the api that is supposed to be a >>>>>> String and add asString. There are too many places to worry about ... I >>>>>> would prefer that Pharo be ANSI compliant:) >>>>>> >>>>>> It's not just Metacello. >>>>>> >>>>>> It's an annoying issue that has to be dealt with every time a Pharo >>>>>> application is ported to another dialect of Smalltalk and an annoying >>>>>> barrier for folks running on other dialects to move their application to >>>>>> Pharo - in this case the bugs that are introduced by Pharo's behavior with >>>>>> respect to Symbols can be very hard to diagnose -- >>>>>> >>>>>> Making things harder to share code between dialects is a bad thing for >>>>>> Smalltalk overall -- just another reason for non-Smalltalk programmers to >>>>>> question the whether they should use Smalltalk or not... >>>>>> >>>>>> And I don't need to hear about how Pharo is not Smalltalk:) >>>>>> >>>>>> Dale >>>>> >>>>> So there is nothing 'wrong', you just want Pharo to remain the same as >>>>> every other non-changing Smalltalk out there. >>>> >>>> Did I say that? >>>> >>>> I support the direction that Pharo is going, but I reserve the right to >>>> disagree with some of the details. >>>> >>>> This is just one detail ... nothing more nothing less ... For those of us >>>> that work in multiple dialects, it IS annoying and I take an opportunity >>>> every year or so to remind you guys of the things that I find annoying, just >>>> to keep you guys honest:) >>>> >>>>> >>>>> From one perspective you are right, it makes some cross platform porting >>>>> in either direction harder. Seaside has many rules to help portability. Not >>>>> mixing Strings and Symbol is probably one of them. >>>> >>>> ... and as I mentioned, this problem can be one of the more annoying issues >>>> to track down, when a developer is not careful ... Honestly there are two >>>> sides to the issue ... when developers use Symbols in tests to drive an API >>>> that is supposed to use Strings (this happens the most often) things break >>>> pretty quickly and the tests can be fixed pretty easily ... but when the >>>> code itself is written with mixed Symbols and Strings, the tests might >>>> actually pass after the port, and the bugs will only show up in subtle cases >>>> ... I've hit a handful of these over the years and they are hard to track >>>> down... >>>>> >>>>> >>>>> But you know very well that Pharo was started so that we would be able to >>>>> make changes, in any area or aspect of the system, without the burden of >>>>> backwards or cross platform compatibility, even if some of these changes are >>>>> taste based. >>>> >>>> Agree with your statement -- most of the changes that Pharo has made have >>>> not been difficult to accommodate, but Symbol/String is at a fundamental >>>> level and I'm not sure that it would be "illegal" to make this accommodation >>>> --- I AM pretty certain that it would cause some short term pain, but >>>> probably no more pain (and likely less pain) than is caused by trying to >>>> move an application to a new version of Pharo:) >>>>> >>>>> And I happen to like the ability to mix and match Strings and Symbols (we >>>>> discussed about this before). >>>>> >>>> I won't argue with taste, it's is simply the portability for this particular >>>> problem that I am highlighting ... >>>> >>>> Dale >>>> >>> >> >> >

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Stephane Ducasse

I try to understand why I could not find it by myself and when I look at writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag | extension fileName outputStream | self halt. extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. fileName := baseName, extension. fileName := FileSystem disk checkName: fileName fixErrors: true. outputStream := (File named: fileName) writeStream. (ZnCrPortableWriteStream on: (ZnCharacterWriteStream on: outputStream encoding: 'utf8')) nextPutAll: aStream contents. outputStream close. self inform: 'Filed out to: ', String cr, fileName. I do not understand why File does not understand fullName. So going to bed because I got too many bugs this evening. and I'm doing an overflow. Stef On Wed, Nov 8, 2017 at 10:05 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok you are right I could then find them there. > This is quite annoying and this is probably related to the launcher > > > On Wed, Nov 8, 2017 at 10:03 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> File @ /Users/ducasse/Documents/Pharo/vms/70-x86/Pharo.app/Contents/MacOS >> >> Stef >> >> On Wed, Nov 8, 2017 at 10:03 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >>> https://pharo.fogbugz.com/f/cases/20658/Fileouting-code-from-the-changesort… >>> >>> On Wed, Nov 8, 2017 at 9:53 PM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>>> It looks like the problem is here but I cannot find it. >>>> >>>> CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag >>>> >>>> | extension fileName outputStream | >>>> self halt. >>>> extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. >>>> fileName := baseName, extension. >>>> fileName := FileSystem disk checkName: fileName fixErrors: true. >>>> outputStream := (File named: fileName) writeStream. >>>> (ZnCrPortableWriteStream on: (ZnCharacterWriteStream >>>> on: outputStream >>>> encoding: 'utf8')) nextPutAll: aStream contents. >>>> >>>> outputStream close. >>>> >>>> self inform: 'Filed out to: ', String cr, fileName. >>>> >>>> On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse >>>> <stepharo.self(a)gmail.com> wrote: >>>>> Ah thanks we should fix this. >>>>> >>>>> On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann >>>>> <ckeen(a)pestilenz.org> wrote: >>>>>> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: >>>>>>> Hi >>>>>>> >>>>>>> I'm trying to rescue some of my work (that I cannot save in MC nor in >>>>>>> Iceberg because the system >>>>>>> does not see it - super funny). >>>>>>> >>>>>>> I can browse the change using the changesorter when I do fileout >>>>>>> the system tells me that the file it saved but I cannot find it on my disc. >>>>>>> Apparently none of the fileout is working in the changesorter. :( >>>>>> >>>>>> I have successfully filed out code with epicea but not changesorter. >>>>>> >>>>>> HTH, >>>>>> >>>>>> Christian >>>>>> >>>>>> -- >>>>>> May you be peaceful, may you live in safety, may you be free from >>>>>> suffering, and may you live with ease. >>>>>>

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Stephane Ducasse

Ok you are right I could then find them there. This is quite annoying and this is probably related to the launcher On Wed, Nov 8, 2017 at 10:03 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > File @ /Users/ducasse/Documents/Pharo/vms/70-x86/Pharo.app/Contents/MacOS > > Stef > > On Wed, Nov 8, 2017 at 10:03 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> https://pharo.fogbugz.com/f/cases/20658/Fileouting-code-from-the-changesort… >> >> On Wed, Nov 8, 2017 at 9:53 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >>> It looks like the problem is here but I cannot find it. >>> >>> CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag >>> >>> | extension fileName outputStream | >>> self halt. >>> extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. >>> fileName := baseName, extension. >>> fileName := FileSystem disk checkName: fileName fixErrors: true. >>> outputStream := (File named: fileName) writeStream. >>> (ZnCrPortableWriteStream on: (ZnCharacterWriteStream >>> on: outputStream >>> encoding: 'utf8')) nextPutAll: aStream contents. >>> >>> outputStream close. >>> >>> self inform: 'Filed out to: ', String cr, fileName. >>> >>> On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse >>> <stepharo.self(a)gmail.com> wrote: >>>> Ah thanks we should fix this. >>>> >>>> On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann >>>> <ckeen(a)pestilenz.org> wrote: >>>>> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: >>>>>> Hi >>>>>> >>>>>> I'm trying to rescue some of my work (that I cannot save in MC nor in >>>>>> Iceberg because the system >>>>>> does not see it - super funny). >>>>>> >>>>>> I can browse the change using the changesorter when I do fileout >>>>>> the system tells me that the file it saved but I cannot find it on my disc. >>>>>> Apparently none of the fileout is working in the changesorter. :( >>>>> >>>>> I have successfully filed out code with epicea but not changesorter. >>>>> >>>>> HTH, >>>>> >>>>> Christian >>>>> >>>>> -- >>>>> May you be peaceful, may you live in safety, may you be free from >>>>> suffering, and may you live with ease. >>>>>

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Stephane Ducasse

File @ /Users/ducasse/Documents/Pharo/vms/70-x86/Pharo.app/Contents/MacOS Stef On Wed, Nov 8, 2017 at 10:03 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > https://pharo.fogbugz.com/f/cases/20658/Fileouting-code-from-the-changesort… > > On Wed, Nov 8, 2017 at 9:53 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> It looks like the problem is here but I cannot find it. >> >> CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag >> >> | extension fileName outputStream | >> self halt. >> extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. >> fileName := baseName, extension. >> fileName := FileSystem disk checkName: fileName fixErrors: true. >> outputStream := (File named: fileName) writeStream. >> (ZnCrPortableWriteStream on: (ZnCharacterWriteStream >> on: outputStream >> encoding: 'utf8')) nextPutAll: aStream contents. >> >> outputStream close. >> >> self inform: 'Filed out to: ', String cr, fileName. >> >> On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse >> <stepharo.self(a)gmail.com> wrote: >>> Ah thanks we should fix this. >>> >>> On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann >>> <ckeen(a)pestilenz.org> wrote: >>>> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: >>>>> Hi >>>>> >>>>> I'm trying to rescue some of my work (that I cannot save in MC nor in >>>>> Iceberg because the system >>>>> does not see it - super funny). >>>>> >>>>> I can browse the change using the changesorter when I do fileout >>>>> the system tells me that the file it saved but I cannot find it on my disc. >>>>> Apparently none of the fileout is working in the changesorter. :( >>>> >>>> I have successfully filed out code with epicea but not changesorter. >>>> >>>> HTH, >>>> >>>> Christian >>>> >>>> -- >>>> May you be peaceful, may you live in safety, may you be free from >>>> suffering, and may you live with ease. >>>>

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/20658/Fileouting-code-from-the-changesort… On Wed, Nov 8, 2017 at 9:53 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > It looks like the problem is here but I cannot find it. > > CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag > > | extension fileName outputStream | > self halt. > extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. > fileName := baseName, extension. > fileName := FileSystem disk checkName: fileName fixErrors: true. > outputStream := (File named: fileName) writeStream. > (ZnCrPortableWriteStream on: (ZnCharacterWriteStream > on: outputStream > encoding: 'utf8')) nextPutAll: aStream contents. > > outputStream close. > > self inform: 'Filed out to: ', String cr, fileName. > > On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: >> Ah thanks we should fix this. >> >> On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann >> <ckeen(a)pestilenz.org> wrote: >>> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: >>>> Hi >>>> >>>> I'm trying to rescue some of my work (that I cannot save in MC nor in >>>> Iceberg because the system >>>> does not see it - super funny). >>>> >>>> I can browse the change using the changesorter when I do fileout >>>> the system tells me that the file it saved but I cannot find it on my disc. >>>> Apparently none of the fileout is working in the changesorter. :( >>> >>> I have successfully filed out code with epicea but not changesorter. >>> >>> HTH, >>> >>> Christian >>> >>> -- >>> May you be peaceful, may you live in safety, may you be free from >>> suffering, and may you live with ease. >>>

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Pavel Krivanek

I tried it and the file-out looks to work as expected for me. I guess that your troubles can be related to a working directory location. Can you check your working directory path (FileSystem workingDirectory)? -- Pavel 2017-11-08 21:53 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > It looks like the problem is here but I cannot find it. > > CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: > stOrCsFlag > > | extension fileName outputStream | > self halt. > extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. > fileName := baseName, extension. > fileName := FileSystem disk checkName: fileName fixErrors: true. > outputStream := (File named: fileName) writeStream. > (ZnCrPortableWriteStream on: (ZnCharacterWriteStream > on: outputStream > encoding: 'utf8')) nextPutAll: aStream contents. > > outputStream close. > > self inform: 'Filed out to: ', String cr, fileName. > > On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > Ah thanks we should fix this. > > > > On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann > > <ckeen(a)pestilenz.org> wrote: > >> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: > >>> Hi > >>> > >>> I'm trying to rescue some of my work (that I cannot save in MC nor in > >>> Iceberg because the system > >>> does not see it - super funny). > >>> > >>> I can browse the change using the changesorter when I do fileout > >>> the system tells me that the file it saved but I cannot find it on my > disc. > >>> Apparently none of the fileout is working in the changesorter. :( > >> > >> I have successfully filed out code with epicea but not changesorter. > >> > >> HTH, > >> > >> Christian > >> > >> -- > >> May you be peaceful, may you live in safety, may you be free from > >> suffering, and may you live with ease. > >> > >

Nov. 8, 2017

Re: [Pharo-dev] Is fileout on the change sorter working in Pharo 70?

by Stephane Ducasse

It looks like the problem is here but I cannot find it. CodeExporter>> writeSourceCodeFrom: aStream baseName: baseName isSt: stOrCsFlag | extension fileName outputStream | self halt. extension := stOrCsFlag ifTrue: ['.st'] ifFalse: ['.cs']. fileName := baseName, extension. fileName := FileSystem disk checkName: fileName fixErrors: true. outputStream := (File named: fileName) writeStream. (ZnCrPortableWriteStream on: (ZnCharacterWriteStream on: outputStream encoding: 'utf8')) nextPutAll: aStream contents. outputStream close. self inform: 'Filed out to: ', String cr, fileName. On Wed, Nov 8, 2017 at 9:38 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ah thanks we should fix this. > > On Wed, Nov 8, 2017 at 9:31 PM, Christian Kellermann > <ckeen(a)pestilenz.org> wrote: >> * Stephane Ducasse <stepharo.self(a)gmail.com> [171108 21:29]: >>> Hi >>> >>> I'm trying to rescue some of my work (that I cannot save in MC nor in >>> Iceberg because the system >>> does not see it - super funny). >>> >>> I can browse the change using the changesorter when I do fileout >>> the system tells me that the file it saved but I cannot find it on my disc. >>> Apparently none of the fileout is working in the changesorter. :( >> >> I have successfully filed out code with epicea but not changesorter. >> >> HTH, >> >> Christian >> >> -- >> May you be peaceful, may you live in safety, may you be free from >> suffering, and may you live with ease. >>

Nov. 8, 2017