- Pharo-users - lists.pharo.org

Fwd: Possible Problem in Spawning Warning Messages

by Joseph Kulisics

---------- Forwarded message ---------- From: Joseph Kulisics <kulisics.joseph(a)gmail.com> Date: Mon, Jun 6, 2016 at 6:48 PM Subject: Fwd: Possible Problem in Spawning Warning Messages To: pharo-users(a)lists.pharo.org I have additional information on the #general slack channel on June 3. In short, the problem appears to be that the test runner keeps executing instructions after the initial error and opens a window for each subsequent error, which could be a lot of windows if the error is in the middle of a parse. Here are the screen shots and interaction demonstrating the phenomenon. The screen shots corresponding to the discussion are 2, 3, and 4 at the end of the e-mail. Joseph Kulisics [9:53 PM] Star this message @emaringolo: Actually, now that I look at it, it looks like the program kept executing after the first error. Is that possible? Esteban Maringolo [9:54 PM] Star this message Unless you're forking processes it shouldn't [9:54] Star this message Zinc HTTP client runs on the thread you execute it, so it won't fork anything. Joseph Kulisics [9:55 PM] Star this message I'm not forking anything, but let me show you the windows: Joseph Kulisics [9:55 PM] Star this file uploaded an image: PharoScreenshot.2.png Add Comment Joseph Kulisics [9:56 PM] Star this message This is the code that was executing. The window is the middle one in the stack. dionisiydk [9:56 PM] Star this message It could happen if error is signaled inside announcement processing Joseph Kulisics [9:56 PM] Star this message The first line produces the `ZnHttpUnsuccessful` error Joseph Kulisics [9:57 PM] Star this file uploaded an image: PharoScreenshot.3.png Add Comment Joseph Kulisics [9:57 PM] Star this message The error is what opens the bottom window. [9:58] Star this message The code in the middle window resumes and produces an error at the second line, which raises the middle window, which is pictured first Esteban Maringolo [9:58 PM] Star this message Nothing looks "strange" there Joseph Kulisics [9:58 PM] Star this message Finally, the top window is spawned by the last line of code, which attempts to read a result key from a dictionary parsed from JSON Esteban Maringolo [9:58 PM] Star this message other than the dashes in the method comment Joseph Kulisics [9:59 PM] Star this file uploaded an image: PharoScreenshot.4.png Add Comment Joseph Kulisics [9:59 PM] Star this message So the single test appears to have raised all three of these windows by continuing to run after the first error [10:00] Star this message I couldn't really inspect the stack of windows on the JSON parsing errors because it was just too deep ---------- Forwarded message ---------- From: Joseph Kulisics <kulisics.joseph(a)gmail.com> Date: Fri, Jun 3, 2016 at 9:38 PM Subject: Possible Problem in Spawning Warning Messages To: pharo-users(a)lists.pharo.org I post my question/report to the Slack pharo #general channel, and someone advised me to e-mail the list. I've attached the referenced screenshots. âHere is the interaction: Joseph Kulisics [9:10 PM] Hi. I started using Pharo 5 about a week ago, and I've noticed some peculiar behavior with debugging. When I get an error in a message send, the system now seems to open a warning window for every message in the stack, which can amount to hundreds of messages. In Pharo 4, only one warning opened. In addition, when I select a warning message, I get the debugger with no stack; the stack no longer seems to be aggregated and available to the debugger instance. Is there a system setting that controls the behavior? I looked around---I tried turning off the Glamorous tools---but nothing seemed to have any effect. The behavior is very difficult to work with. Is there an way to use the interface to at least close all of the warning windows when an error occurs? Thanks. Esteban Maringolo [9:12 PM] @offray: Yeap, and I'd also like something like jOOQ for Pharo, it could be done using Glorp internals Offray Vladimir Luna CÃ¡rdenas [9:13 PM] @emaringolo: what is jOOQ ? [9:14] this: https://en.wikipedia.org/wiki/Java_Object_Oriented_Querying ? Esteban Maringolo [9:14 PM] Let's continue in #databases Offray Vladimir Luna CÃ¡rdenas [9:14 PM] Ohh ok Esteban Maringolo [9:18 PM] Joseph, it seem like every action in the debugger is triggering a new debugger, is that what you mean? Joseph Kulisics [9:18 PM] I'm not really about the description at that low a level. I have a testing suite, and when I click on the icon next to a single test to run it, a failing test will open warning windows. [9:19] In Pharo 4, I got one warning for the failing message send [9:19] Now I seem to get one for each message in the stack [9:19] If I click on the message in the warning window, a debugger opens Esteban Maringolo [9:19 PM] Are you running the tests using the Test Runner? Joseph Kulisics [9:19 PM] But the debugger only has one message in the top pane [9:20] Both with the test runner and clicking the icon next to the test in a browser [9:20] In the test runner, I I click a test in error, I get a slew of warning windows Joseph Kulisics [9:24 PM] uploaded an image: PharoScreenshot.png Add Comment Joseph Kulisics [9:24 PM] uploaded an image: PharoScreenshot.1.png Add Comment Joseph Kulisics [9:25 PM] The top image shows the stack of windows that opened in response to selecting the test highlighted in the second image [9:25] (I changed a system setting to open a full debugger instead of a warning window in response to an error, but the behavior is identical when warning windows appear first.) [9:26] As I mentioned, the behavior from the TestRunner is the same. The only difference is that the warnings are suppressed until you select a test in error. [9:26] In Pharo 4, I'd have had one window for the error. [9:27] This example isn't too bad---there are only three windows on the stack---but I've had cases where a test triggered a stack of a couple of hundred warning windows dionisiydk [9:27 PM] Could it be that you test fork multiple processes? Joseph Kulisics [9:27 PM] I either have to exit each one, or I have to kill the image [9:28] @dionisiydk: I don't think so. I don't create a new process in the code, but I can't speak for the underlying libraries like Zinc. In any case, as you can see above, the titles of the three windows are different. [9:29] @dionisiydk: In addition, each window in the stack contains exactly one message, but in exploring the data, the messages all appear to deal with the same set of objects used by the tests [9:31] As I mentioned before, I made the switch to Pharo 5 last week. Before last week, the same tests produced a single error message. [9:31] I did reload the underlying libraries as part of moving my software into the new image, so maybe the underlying libraries changed. Esteban Maringolo [9:33 PM] Could you write a mail to the mailing list? `pharo-users(a)lists.pharo.org`

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Sven Van Caekenberghe

> On 06 Jun 2016, at 17:22, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > why ByteArray? http://www.unicode.org/faq/utf_bom.html A Unicode transformation format (UTF) is an algorithmic mapping from every Unicode code point (except surrogate code points) to a unique byte sequence. https://en.wikipedia.org/wiki/UTF-8 UTF-8 encodes each of the 1,112,064 valid code points in the Unicode code space (1,114,112 code points minus 2,048 surrogate code points) using one to four 8-bit bytes (a group of 8 bits is known as an octet in the Unicode Standard). In Pharo https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… Of course, given a ByteArray, whose values are all between 0 and 255 by definition, you can convert it to a ByteString. That String is not a correct (Pharo) String anymore, it is like converting a PNG or JPEG to String, you can do it, it is just wrong. When talking to the outside world, be it over a network connection, or via primitive calls, anything but pure ASCII strings need an encoding. This has to be agreed upon by both parties. If the receiving party wants UTF-8 forced into a (kind of) String, that is (still) possible. Your initial solution seems to indicate that this is expected. This (ugly) conversion should be done at an as low level as possible, IMHO. Sven

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Sabine Manaa

Hi Sven, thank you very much for your explanation. I will read the pharo book chapter again tomorrow morning. Each time I have to do with encoding, I have to start again with reading....;-( I was not asking for the reason of encoding but because OSProcess command: needs a String and not a Byte Array. But yes, sure, first encode it and then convert it back to a string. Regards and a nice evening Sabine 2016-06-06 19:57 GMT+02:00 Sven Van Caekenberghe-2 [via Smalltalk] < ml-node+s1294792n4899446h21(a)n4.nabble.com>: > > > On 06 Jun 2016, at 17:22, Sabine Manaa <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4899446&i=0>> wrote: > > > > why ByteArray? > > http://www.unicode.org/faq/utf_bom.html > > A Unicode transformation format (UTF) is an algorithmic mapping from every > Unicode code point (except surrogate code points) to a unique byte > sequence. > > https://en.wikipedia.org/wiki/UTF-8 > > UTF-8 encodes each of the 1,112,064 valid code points in the Unicode code > space (1,114,112 code points minus 2,048 surrogate code points) using one > to four 8-bit bytes (a group of 8 bits is known as an octet in the Unicode > Standard). > > In Pharo > > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > Of course, given a ByteArray, whose values are all between 0 and 255 by > definition, you can convert it to a ByteString. That String is not a > correct (Pharo) String anymore, it is like converting a PNG or JPEG to > String, you can do it, it is just wrong. > > When talking to the outside world, be it over a network connection, or via > primitive calls, anything but pure ASCII strings need an encoding. This has > to be agreed upon by both parties. If the receiving party wants UTF-8 > forced into a (kind of) String, that is (still) possible. > > Your initial solution seems to indicate that this is expected. This (ugly) > conversion should be done at an as low level as possible, IMHO. > > Sven > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Sabine Manaa

Sorry, I did a mistake. I reversed it by mistake. asString is needed. does work : OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). does not work (Improper store into indexable object): OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) I can try on windows tomorrow if you want. 2016-06-06 17:22 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > Hi Sven, > > why ByteArray? > > does not work (Improper store into indexable object): > OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf > /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). > > works: > OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf > /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) > > Perhaps David can add this here: > > command: aCommandString > "Run a command in a shell process. Similar to the system(3) call in the > standard C library, > except that aCommandString runs asynchronously in a child process. The > command is > run by a ConnectedUnixProcess in order to facilitate command pipelines > within Squeak." > > "UnixProcess thisOSProcess command: 'ls -l /etc'" > > | proc | > pid isNil > ifTrue: > [self class noAccessorAvailable. ^nil] > ifFalse: > [proc := self > forkJob: ExternalUnixOSProcess defaultShellPath > arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) > <<<=== > environment: nil > descriptors: nil. > proc ifNil: [self class noAccessorAvailable]. > ^ proc] > > > regards > Sabine > > >> >> > > 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > >> Hi Dave, >> >> I get the german Ã¤ with: >> >> (Character value: 228) asString >> >> Do you want me to go in it and suggest a solution or do you want to try >> to fix it and I test it? >> >> Thanks for helping! >> >> Regards Sabine >> >> 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: >> >>> >>> >>> ------------------------------ >>> If you reply to this email, your message will be added to the discussion >>> below: >>> >>> http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… >>> To start a new topic under Pharo Smalltalk Users, email [hidden email] >>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> >>> To unsubscribe from Pharo Smalltalk Users, click here. >>> NAML >>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>> >> >> >> ------------------------------ >> View this message in context: Re: OSProcess command with german umlaut >> does not work >> <http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp…> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >> Nabble.com. >> > >

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Mariano Martinez Peck

Hi Dave, Sabine, Norbert et all, Few weeks (months?) ago I was also reviewing this topic of encoding a OS(Sub)Process. After surfing a bit the web, I found out the most simple and accurate answer/solution was indeed to set the correct locale and/or text encoding in the computer in question. Anyway...more answers below. Now... what I don't understand from Sabine is.. she said this one works: OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) *But then my question is...does that work only because she's computer locale is UTF8? Or Unix* automatically decodes it and knows it is utf8?* *If not...should I adapt the #utf8Encoded to the encoding defined by the terminal? mmm* In my OSX box I do have UTF8 set: â¯ locale [13:56:49] LANG="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_CTYPE="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_ALL= On Mon, Jun 6, 2016 at 1:42 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > Norbert, > > You are probably right. I'm not sure the best way to handle it. > > Dave > > > Dave, > > > >> Am 06.06.2016 um 18:13 schrieb David T. Lewis <lewis(a)mail.msen.com>: > >> > >> Hi Sabine, > >> > >> That's great that #utf8Encoded is working, thanks for confirming. > >> > >> I'll look and see if I can add that to OSProcess (I'm traveling and > >> cannot > >> look at it right now). > >> > >> Mariano - this thread probably applies to OSSubProcess also. > >> > > that would just work if the system locale is utf8, right? Wouldn't it be > > better to making that a setting? > > > > Norbert > > > >> Dave > >> > >>> Hi Sven, > >>> > >>> why ByteArray? > >>> > >>> does not work (Improper store into indexable object): > >>> OSProcess command: ('cp > >>> /Library/WebServer/Documents/reports/bÃ¤r.pdf > >>> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). > >>> > >>> works: > >>> OSProcess command: ('cp > >>> /Library/WebServer/Documents/reports/bÃ¤r.pdf > >>> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) > >>> > >>> Perhaps David can add this here: > >>> > >>> command: aCommandString > >>> "Run a command in a shell process. Similar to the system(3) call in the > >>> standard C library, > >>> except that aCommandString runs asynchronously in a child process. The > >>> command is > >>> run by a ConnectedUnixProcess in order to facilitate command pipelines > >>> within Squeak." > >>> > >>> "UnixProcess thisOSProcess command: 'ls -l /etc'" > >>> > >>> | proc | > >>> pid isNil > >>> ifTrue: > >>> [self class noAccessorAvailable. ^nil] > >>> ifFalse: > >>> [proc := self > >>> forkJob: ExternalUnixOSProcess defaultShellPath > >>> arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) > >>> <<<=== > >>> environment: nil > >>> descriptors: nil. > >>> proc ifNil: [self class noAccessorAvailable]. > >>> ^ proc] > >>> > >>> > >>> regards > >>> Sabine > >>> > >>> > >>>> > >>>> > >>> > >>> 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > >>> > >>>> Hi Dave, > >>>> > >>>> I get the german Ã¤ with: > >>>> > >>>> (Character value: 228) asString > >>>> > >>>> Do you want me to go in it and suggest a solution or do you want to > >>>> try > >>>> to > >>>> fix it and I test it? > >>>> > >>>> Thanks for helping! > >>>> > >>>> Regards Sabine > >>>> > >>>> 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden > >>>> email] > >>>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: > >>>> > >>>>> > >>>>> > >>>>> ------------------------------ > >>>>> If you reply to this email, your message will be added to the > >>>>> discussion > >>>>> below: > >>>>> > >>>>> > http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… > >>>>> To start a new topic under Pharo Smalltalk Users, email [hidden > >>>>> email] > >>>>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> > >>>>> To unsubscribe from Pharo Smalltalk Users, click here. > >>>>> NAML > >>>>> < > http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan… > > > >>>>> > >>>> > >>>> > >>>> ------------------------------ > >>>> View this message in context: Re: OSProcess command with german umlaut > >>>> does not work > >>>> < > http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… > > > >>>> Sent from the Pharo Smalltalk Users mailing list archive > >>>> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at > >>>> Nabble.com. > >>>> > >>> > >> > >> > >> > > > > > > > > -- Mariano http://marianopeck.wordpress.com

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by David T. Lewis

Norbert, You are probably right. I'm not sure the best way to handle it. Dave > Dave, > >> Am 06.06.2016 um 18:13 schrieb David T. Lewis <lewis(a)mail.msen.com>: >> >> Hi Sabine, >> >> That's great that #utf8Encoded is working, thanks for confirming. >> >> I'll look and see if I can add that to OSProcess (I'm traveling and >> cannot >> look at it right now). >> >> Mariano - this thread probably applies to OSSubProcess also. >> > that would just work if the system locale is utf8, right? Wouldn't it be > better to making that a setting? > > Norbert > >> Dave >> >>> Hi Sven, >>> >>> why ByteArray? >>> >>> does not work (Improper store into indexable object): >>> OSProcess command: ('cp >>> /Library/WebServer/Documents/reports/bÃÂ¤r.pdf >>> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). >>> >>> works: >>> OSProcess command: ('cp >>> /Library/WebServer/Documents/reports/bÃÂ¤r.pdf >>> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) >>> >>> Perhaps David can add this here: >>> >>> command: aCommandString >>> "Run a command in a shell process. Similar to the system(3) call in the >>> standard C library, >>> except that aCommandString runs asynchronously in a child process. The >>> command is >>> run by a ConnectedUnixProcess in order to facilitate command pipelines >>> within Squeak." >>> >>> "UnixProcess thisOSProcess command: 'ls -l /etc'" >>> >>> | proc | >>> pid isNil >>> ifTrue: >>> [self class noAccessorAvailable. ^nil] >>> ifFalse: >>> [proc := self >>> forkJob: ExternalUnixOSProcess defaultShellPath >>> arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) >>> <<<=== >>> environment: nil >>> descriptors: nil. >>> proc ifNil: [self class noAccessorAvailable]. >>> ^ proc] >>> >>> >>> regards >>> Sabine >>> >>> >>>> >>>> >>> >>> 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: >>> >>>> Hi Dave, >>>> >>>> I get the german ÃÂ¤ with: >>>> >>>> (Character value: 228) asString >>>> >>>> Do you want me to go in it and suggest a solution or do you want to >>>> try >>>> to >>>> fix it and I test it? >>>> >>>> Thanks for helping! >>>> >>>> Regards Sabine >>>> >>>> 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden >>>> email] >>>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: >>>> >>>>> >>>>> >>>>> ------------------------------ >>>>> If you reply to this email, your message will be added to the >>>>> discussion >>>>> below: >>>>> >>>>> http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… >>>>> To start a new topic under Pharo Smalltalk Users, email [hidden >>>>> email] >>>>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> >>>>> To unsubscribe from Pharo Smalltalk Users, click here. >>>>> NAML >>>>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>>>> >>>> >>>> >>>> ------------------------------ >>>> View this message in context: Re: OSProcess command with german umlaut >>>> does not work >>>> <http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp…> >>>> Sent from the Pharo Smalltalk Users mailing list archive >>>> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >>>> Nabble.com. >>>> >>> >> >> >> > >

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Norbert Hartl

Dave, > Am 06.06.2016 um 18:13 schrieb David T. Lewis <lewis(a)mail.msen.com>: > > Hi Sabine, > > That's great that #utf8Encoded is working, thanks for confirming. > > I'll look and see if I can add that to OSProcess (I'm traveling and cannot > look at it right now). > > Mariano - this thread probably applies to OSSubProcess also. > that would just work if the system locale is utf8, right? Wouldn't it be better to making that a setting? Norbert > Dave > >> Hi Sven, >> >> why ByteArray? >> >> does not work (Improper store into indexable object): >> OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃÂ¤r.pdf >> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). >> >> works: >> OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃÂ¤r.pdf >> /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) >> >> Perhaps David can add this here: >> >> command: aCommandString >> "Run a command in a shell process. Similar to the system(3) call in the >> standard C library, >> except that aCommandString runs asynchronously in a child process. The >> command is >> run by a ConnectedUnixProcess in order to facilitate command pipelines >> within Squeak." >> >> "UnixProcess thisOSProcess command: 'ls -l /etc'" >> >> | proc | >> pid isNil >> ifTrue: >> [self class noAccessorAvailable. ^nil] >> ifFalse: >> [proc := self >> forkJob: ExternalUnixOSProcess defaultShellPath >> arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) >> <<<=== >> environment: nil >> descriptors: nil. >> proc ifNil: [self class noAccessorAvailable]. >> ^ proc] >> >> >> regards >> Sabine >> >> >>> >>> >> >> 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: >> >>> Hi Dave, >>> >>> I get the german ÃÂ¤ with: >>> >>> (Character value: 228) asString >>> >>> Do you want me to go in it and suggest a solution or do you want to try >>> to >>> fix it and I test it? >>> >>> Thanks for helping! >>> >>> Regards Sabine >>> >>> 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden >>> email] >>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: >>> >>>> >>>> >>>> ------------------------------ >>>> If you reply to this email, your message will be added to the >>>> discussion >>>> below: >>>> >>>> http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… >>>> To start a new topic under Pharo Smalltalk Users, email [hidden email] >>>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> >>>> To unsubscribe from Pharo Smalltalk Users, click here. >>>> NAML >>>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>>> >>> >>> >>> ------------------------------ >>> View this message in context: Re: OSProcess command with german umlaut >>> does not work >>> <http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp…> >>> Sent from the Pharo Smalltalk Users mailing list archive >>> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >>> Nabble.com. >>> >> > > >

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by David T. Lewis

Hi Sabine, That's great that #utf8Encoded is working, thanks for confirming. I'll look and see if I can add that to OSProcess (I'm traveling and cannot look at it right now). Mariano - this thread probably applies to OSSubProcess also. Dave > Hi Sven, > > why ByteArray? > > does not work (Improper store into indexable object): > OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃÂ¤r.pdf > /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). > > works: > OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃÂ¤r.pdf > /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) > > Perhaps David can add this here: > > command: aCommandString > "Run a command in a shell process. Similar to the system(3) call in the > standard C library, > except that aCommandString runs asynchronously in a child process. The > command is > run by a ConnectedUnixProcess in order to facilitate command pipelines > within Squeak." > > "UnixProcess thisOSProcess command: 'ls -l /etc'" > > | proc | > pid isNil > ifTrue: > [self class noAccessorAvailable. ^nil] > ifFalse: > [proc := self > forkJob: ExternalUnixOSProcess defaultShellPath > arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) > <<<=== > environment: nil > descriptors: nil. > proc ifNil: [self class noAccessorAvailable]. > ^ proc] > > > regards > Sabine > > >> >> > > 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > >> Hi Dave, >> >> I get the german ÃÂ¤ with: >> >> (Character value: 228) asString >> >> Do you want me to go in it and suggest a solution or do you want to try >> to >> fix it and I test it? >> >> Thanks for helping! >> >> Regards Sabine >> >> 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden >> email] >> <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: >> >>> >>> >>> ------------------------------ >>> If you reply to this email, your message will be added to the >>> discussion >>> below: >>> >>> http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… >>> To start a new topic under Pharo Smalltalk Users, email [hidden email] >>> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> >>> To unsubscribe from Pharo Smalltalk Users, click here. >>> NAML >>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>> >> >> >> ------------------------------ >> View this message in context: Re: OSProcess command with german umlaut >> does not work >> <http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp…> >> Sent from the Pharo Smalltalk Users mailing list archive >> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >> Nabble.com. >> >

June 6, 2016

magma for pharo 5.

by francescoagati

Hi, someone know the state of Magma for pharo5? there is a port of magma for pharo 5? -- View this message in context: http://forum.world.st/magma-for-pharo-5-tp4899426.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 6, 2016

Re: [Pharo-users] OSProcess command with german umlaut does not work

by Sabine Manaa

Hi Sven, why ByteArray? does not work (Improper store into indexable object): OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded asString). works: OSProcess command: ('cp /Library/WebServer/Documents/reports/bÃ¤r.pdf /Library/WebServer/Documents/reports/test-a.pdf' utf8Encoded) Perhaps David can add this here: command: aCommandString "Run a command in a shell process. Similar to the system(3) call in the standard C library, except that aCommandString runs asynchronously in a child process. The command is run by a ConnectedUnixProcess in order to facilitate command pipelines within Squeak." "UnixProcess thisOSProcess command: 'ls -l /etc'" | proc | pid isNil ifTrue: [self class noAccessorAvailable. ^nil] ifFalse: [proc := self forkJob: ExternalUnixOSProcess defaultShellPath arguments: (Array with: '-c' with: aCommandString utf8Encoded asString) <<<=== environment: nil descriptors: nil. proc ifNil: [self class noAccessorAvailable]. ^ proc] regards Sabine > > 2016-06-06 8:41 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > Hi Dave, > > I get the german Ã¤ with: > > (Character value: 228) asString > > Do you want me to go in it and suggest a solution or do you want to try to > fix it and I test it? > > Thanks for helping! > > Regards Sabine > > 2016-06-05 23:08 GMT+02:00 David T. Lewis [via Smalltalk] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4899318&i=0>>: > >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp… >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4899318&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: OSProcess command with german umlaut > does not work > <http://forum.world.st/OSProcess-command-with-german-umlaut-does-not-work-tp…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

June 6, 2016