Good day!
Now i download fresh latest pharo archive and unzipped it to C:\Pharo 6.1.
The error still exists.
Debugging shows that error comes with reading from environment varaible:
...
ByteString(String)
convertFromWithConverter:
FilePathEncoder class
Thank you Stef!
I wrote documentation for my packages in Markdown + pandoc + LaTeX.
The TeX macros contains syntax colorization for Smalltalk code which
can be easily added to Pillar (I suppose)
Would you consider adding the syntax coloring from the TeX macros I sent to you?
I have some silly qu
Hi Steph,
The diagram looks cool.
But may I give some positive suggestions?
The goal of each diagram is not clear for me, is to understand the
connection of tools? or a how to configure github in Pharo?
Maybe it could be added into the diagram as a Title.
So, what's the purpose of the diagram/wo
On Wed, Nov 1, 2017 at 6:08 AM, teso...@gmail.com wrote:
> Hi Ben,
> first sorry for answering late, I have seen your mail before, but the
> tons of mails of Pharo got over it.
>
> I will tell you the state of what I have and what maybe you will need.
> But, before my plan is to improve this,
Thanks Stef. They will be very useful.
I presume the simpler one is for projects you own, and the other is
contributing to third-party projects. It would be good to be explicit by
adding such a title to distinguish them.
If your software allows, it might be enhanced by:
* adding sequence numbers
Hi Ben,
first sorry for answering late, I have seen your mail before, but the
tons of mails of Pharo got over it.
I will tell you the state of what I have and what maybe you will need. But,
before my plan is to improve this, but as with everything it is easier to
push it if I have some users.
Hi Holger,
thanks for mentioning the Software Exploration Tool Sourcetrail. I use it when
I develop in C, it is now free for non commercial using.
I already contacted Eberhard Gräther to discuss using Sourcetrail for other
languages than C, C++ and Java. But this will probably at best ta
On Sat, Oct 28, 2017 at 01:39:56PM +0200, Herby Vojk wrote:
> Hi,
>
> I had to find out how to automatically deploy the backend written in
> Pharo, and so far it uses docker-compose stop to stop the instance (and
> later docker-compose up -d to get everything up again).
>
> I noticed the st
We tried to get signing for the Pharo association but it did not work.
So ZweiDenker proposed that we can use their key. Now esteban was busy
with consulting for Pharo
+ iceberg + tonel.
Stef
On Tue, Oct 31, 2017 at 3:38 PM, Andrew Glynn wrote:
> If it would be a help, I can sign the apps.
>
>
>
Bruce O'Neel wrote:
Hi,
Well, not so scary. That's the mac list. From a not so recent mac with
Xcode 7 installed it looks like the below.
The good news here is that the common signals have the same numbers.
And how often do you get an SIGXCPU?
I was think of SIGUSR1, can be used to useful
Hi Pharo 32 bit/Win users,
I'm on the latest stock Pharo 32 bit/Win downloaded from
http://files.pharo.org/platform/Pharo6.1-win.zip
which contains the latest 60518 image.
When evaluating
Metacello new
smalltalkhubUser: 'Moose' project: 'GToolkit';
configuration: 'GToolki
What actually happens is that moving (with the finder) a file to /Applications
removes
the com.apple.quarantine flag.
you could try:
xattr -d com.apple.quarantine
(this is related to signing, too, but not the signing of the app, but the
container the files are downloaded.
We need to use .dmg
If it would be a help, I can sign the apps.
Cheers
Andrew
From: Todd Blanchard
Sent: Tuesday, October 31, 2017 10:36 AM
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] Pharo 6.1
Actually, it is in Applications
Sent from the road
> On Oct 31, 2017, at 02:34, Esteban Lorenzan
Hi,
Well, not so scary. That's the mac list. From a not so recent mac with Xcode
7 installed it looks like the below.
The good news here is that the common signals have the same numbers. And how
often do you get an SIGXCPU?
cheers
bruce
#define SIGHUP 1 /* hangup
Actually, it is in Applications
Sent from the road
> On Oct 31, 2017, at 02:34, Esteban Lorenzano wrote:
>
>
>
>> On 30 Oct 2017, at 20:30, Todd Blanchard wrote:
>>
>> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64
>> for Mac
>>
>> I was greeted with a walkback
Bruce O'Neel wrote:
Hi,
Posix requires that if the process is killed the return status is
greater than 128.
What is convention on linux systems is that if the process is sent a
signal then the signal number is added to 128. Therefore 137 is SIGKILL
(kill -9). SIGTERM is 143, SIGABRT is 134, S
Hi,
Posix requires that if the process is killed the return status is greater than
128.
What is convention on linux systems is that if the process is sent a signal
then the signal number is added to 128. Therefore 137 is SIGKILL (kill -9).
SIGTERM is 143, SIGABRT is 134, SIGSEGV is
Hi all,
an argument for Smalltalk, an discussion coming up many times in my history.
It is also something I'm asking myself from time to time. It is very actual
in the moment.
Many good arguments were mentioned this discussion. I want to provide you my
2 cents on this.
First, I'm taking the vi
Hi all,
an argument for Smalltalk, an discussion coming up many times in my history.
It is also something I'm asking myself from time to time. It is very actual
in the moment.
Many good arguments were mentioned this discussion. I want to provide you my
2 cents on this.
First, I'm taking the vi
> On 30 Oct 2017, at 20:30, Todd Blanchard wrote:
>
> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64
> for Mac
>
> I was greeted with a walkback when it failed to create directory
> /private/var/folders/ks/wg6l98bj64q6hgvs23wwqyprgn/T/AppTranslocation/DAA5EA3A
Hi Diego,
we used this process to migrate:
https://github.com/peteruhnak/git-migration. So we have all history of
QCMagritte (including ConfigurationOf). We created the BaselineOf but
it only loads latest packages (see
https://github.com/Afibre/QCMagritte/blob/master/src/BaselineOfQCMagritte.
21 matches
Mail list logo
