June 2022 - Pharo-users - lists.pharo.org

Re: Pharo 10 & Windows 10 - Frozen

by Christopher Fuhrman

I also had a frozen image problem on my Surface Pro after it sleeps. In my case the frozen Pharo window appears to have an image that was put back into the wrong resolution (I see colored pixels like a P10 window, but they're misaligned). As far as I can tell, the image doesn't respond to keyboard shortcuts, etc. I have to kill the image in Explorer. My setup involves multiple monitors, with different pixel sizes (windows allows to scale them according to the monitor). Perhaps that is part of the problem? It affects Pharo Launcher itself, too, which is running Pharo 10 according to a playground window (SystemVersion current version) Next time I will make an issue on pharo-project/pharo with a screenshot. On Sun, 12 Jun 2022 at 10:26, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > Hi, > I have installed Pharo 10 in windows 10 using Pharo Launcher. > > Whenever Windows goes to sleep or hibernate.... after coming back Pharo > is completely frozen. > The process is consuming almost NO CPU, and I cannot find a workaround to > get it back to normal. > > Any suggestions? > > Thanks > Arturo > > -- > Arturo Zambrano > LinkedIn: https://www.linkedin.com/in/arturozambrano/ >

June 12, 2022

Pharo 10 & Windows 10 - Frozen

by Arturo Zambrano

Hi, I have installed Pharo 10 in windows 10 using Pharo Launcher. Whenever Windows goes to sleep or hibernate.... after coming back Pharo is completely frozen. The process is consuming almost NO CPU, and I cannot find a workaround to get it back to normal. Any suggestions? Thanks Arturo -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

June 12, 2022

[ANN] Launchpad v4.5.0 [v4.5.0] released!

by Buenos Aires Smalltalk

June 9, 2022

Re: OSSUnixSubprocess - not getting output from a command that pipes to grep

by Stewart MacLean

Hi Yanni, Thanks for this. Actually I discovered the equivalent by using shellCommand: instead of command:. What an excellent utility! Cheers, Stewart On Tue, Jun 7, 2022 at 3:12 AM Yanni Chiu <yannix7db(a)gmail.com> wrote: > The equivalent of running in a Terminal is to run it in a shell. Try the > following code: > > OSSUnixSubprocess new > command: '/bin/bash'; > arguments: #('-c' 'ls /'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString inspect > ]. > > OSSUnixSubprocess new > command: '/bin/bash'; > arguments: #('-c' 'ls / | grep bin'); > redirectStdout; > runAndWaitOnExitDo: [ :process :outString | > outString inspect > ]. > > Youâll need to be careful to properly shell escape the shell command > arguments if they are not hard coded (especially things like file names > from users). HTH. âYanni > > On Mon, Jun 6, 2022 at 7:51 AM <vinref(a)gmail.com> wrote: > >> Hi >> >> I tried something similar on (X)ubuntu using this: >> >> OSSUnixSubprocess new >> >> command: '/bin/ls'; >> >> arguments: #('-la' '/tmp/' '|' '/usr/bin/grep unix'); >> >> redirectStdout; >> >> runAndWaitOnExitDo: [ :process :outString | >> >> outString inspect >> >> ] >> >> >> and looking at the output in xtrerm I got a message like this: >> >> /bin/ls: cannot access '|': No such file or directory >> >> /bin/ls: cannot access '/usr/bin/grep unix': No such file or directory. >> >> >> So I think it regards anything after the first item in the arguments as a >> file or directory. >> >> This means you will have to write a bash script instead. So I wrote a >> script called my_grep: >> >> #!/bin/bash >> >> cd $1 >> >> ls -la | grep unix >> >> and called it with: >> >> OSSUnixSubprocess new >> >> command: '/tmp/my_grep'; >> >> arguments: #('/tmp'); >> >> redirectStdout; >> >> runAndWaitOnExitDo: [ :process :outString | >> >> outString inspect >> >> ] >> >> and it worked. >> >> >> Vince >> >> >>

June 6, 2022

Re: OSSUnixSubprocess - not getting output from a command that pipes to grep

by Yanni Chiu

The equivalent of running in a Terminal is to run it in a shell. Try the following code: OSSUnixSubprocess new command: '/bin/bash'; arguments: #('-c' 'ls /'); redirectStdout; runAndWaitOnExitDo: [ :process :outString | outString inspect ]. OSSUnixSubprocess new command: '/bin/bash'; arguments: #('-c' 'ls / | grep bin'); redirectStdout; runAndWaitOnExitDo: [ :process :outString | outString inspect ]. Youâll need to be careful to properly shell escape the shell command arguments if they are not hard coded (especially things like file names from users). HTH. âYanni On Mon, Jun 6, 2022 at 7:51 AM <vinref(a)gmail.com> wrote: > Hi > > I tried something similar on (X)ubuntu using this: > > OSSUnixSubprocess new > > command: '/bin/ls'; > > arguments: #('-la' '/tmp/' '|' '/usr/bin/grep unix'); > > redirectStdout; > > runAndWaitOnExitDo: [ :process :outString | > > outString inspect > > ] > > > and looking at the output in xtrerm I got a message like this: > > /bin/ls: cannot access '|': No such file or directory > > /bin/ls: cannot access '/usr/bin/grep unix': No such file or directory. > > > So I think it regards anything after the first item in the arguments as a > file or directory. > > This means you will have to write a bash script instead. So I wrote a > script called my_grep: > > #!/bin/bash > > cd $1 > > ls -la | grep unix > > and called it with: > > OSSUnixSubprocess new > > command: '/tmp/my_grep'; > > arguments: #('/tmp'); > > redirectStdout; > > runAndWaitOnExitDo: [ :process :outString | > > outString inspect > > ] > > and it worked. > > > Vince > > >

June 6, 2022

Re: OSSUnixSubprocess - not getting output from a command that pipes to grep

by vinref＠gmail.com

Hi I tried something similar on (X)ubuntu using this: ``` OSSUnixSubprocess new ``` ``` command: '/bin/ls'; ``` ``` arguments: #('-la' '/tmp/' '|' '/usr/bin/grep unix'); ``` ``` redirectStdout; ``` ``` runAndWaitOnExitDo: [ :process :outString | ``` ``` outString inspect ``` ``` ] ``` and looking at the output in xtrerm I got a message like this: ``` /bin/ls: cannot access '|': No such file or directory ``` ``` /bin/ls: cannot access '/usr/bin/grep unix': No such file or directory. ``` So I think it regards anything after the first item in the arguments as a file or directory. This means you will have to write a bash script instead. So I wrote a script called my_grep: ``` #!/bin/bash ``` ``` cd $1 ``` ``` ls -la | grep unix ``` and called it with: ``` OSSUnixSubprocess new ``` ``` command: '/tmp/my_grep'; ``` ``` arguments: #('/tmp'); ``` ``` redirectStdout; ``` ``` runAndWaitOnExitDo: [ :process :outString | ``` ``` outString inspect ``` ``` ] ``` and it worked. Vince

June 6, 2022

OSSUnixSubprocess - not getting output from a command that pipes to grep

by Stewart MacLean

Hi, I have a command that works fine in terminal, and I'm able to retrieve the output using OSUnixSubprocess. However, when I grep the output in the command, I don't receive any output from OSUnixSubprocess. So I get output from: "/Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X" 2>&1 but not from: "/Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X" 2>&1 | grep '==>' However both work fine when the enclosing .command script is run directly in the terminal. I'm a bit out of my depth here, but I would have thought OSUnixSubprocess would just retrieve the output from grep? Is this a problem with my .command or is this a problem with how I'm using OSUnixSubprocess. Code below: Cheers, Stewart >>startUpLogic Transcript cr; show: 'Starting up Logic...'. logicOSProcess := OSSUnixSubprocess new. logicReadProcess := [logicOSProcess command: '/Users/stewart/Desktop/LogicFiltered.command'; redirectStdout; redirectStderr; runAndWaitPollingEvery: (Delay forMilliseconds: 50) doing: [: process : outStream : errorStream | errorStream upToEnd ifNotEmpty: [: value | Transcript cr; show: value]. outStream upToEnd ifNotEmpty: [: value | Transcript cr; show: value]] onExitDo: [: process : outStream : errStream | process closeAndCleanStreams. self log: 'Logic exited with: ', process exitStatusInterpreter printString]] newProcess. logicReadProcess name: 'Logic Read Process'; priority: 50; "Processor userInterruptPriority" resume ================================================ I get output using OSSUnixSubprocess from this .command #!/bin/sh # xattr -r -d com.apple.quarantine /Users/stewart/Desktop/Logic.command cd "/Applications/Logic Pro X.app/Contents/MacOS/" "/Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X" 2>&1 ======================================================== but not this .command #!/bin/sh # xattr -r -d com.apple.quarantine /Users/stewart/Desktop/LogicFiltered.command cd "/Applications/Logic Pro X.app/Contents/MacOS/" "/Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X" 2>&1 | grep '==>'

June 6, 2022

ESUG deadline for Presentation

by stephane ducasse

Hi Happy Smalltalkers Two important points - We are starting to work on the program of ESUG 2022 and we will accept some more talks but do not wait too long. https://esug.github.io/2022-Conference/call2022.html <https://esug.github.io/2022-Conference/call2022.html> - The registration is open and the early rate is nicer than the late one :) https://registration.esug.org <https://registration.esug.org/> But you can sponsor ESUG by registering with late fees from 6th of July. But this is more expensive. S

June 3, 2022