Smalltalk › Pharo › Pharo Smalltalk Developers

How to report website text bugs?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

15 messages Options

Tim Mackinnon

How to report website text bugs?

Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?

Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.

We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"

-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Sven Van Caekenberghe-2

Re: How to report website text bugs?

Hi Tim,

> On 29 Nov 2016, at 00:57, Tim Mackinnon <[hidden email]> wrote:
>
> Hi Guys - how is the best way to report website and text bugs?
>
> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.
>
> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)
>
> Are you using macOS Sierra?
> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
> We are working to fix this temporary inconvenience.
>
>
> Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:
>
> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
> -bash: !'": event not found
>
> The culprit is of course the “!” Character so a better example might be:
>
> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
> Hello WorldStdioStream: 'stdout'
>
> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?
>
>
> Tim

Right, that is not a good example, at all. I don't like it. Good of you to give feedback.

I would rather says something like

./pharo Pharo.image eval '42 factorial'

The stdio example leads way too far (difference between return value and output, newlines, weirder syntax, for Pharo at least, different kinds of quotes, the handling of !).

Sven

philippeback

Re: How to report website text bugs?

In reply to this post by Tim Mackinnon

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:

Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

EstebanLM

Re: How to report website text bugs?

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Tim Mackinnon

Re: How to report website text bugs?

Ok - great. But I will remember that for future reference.

I noticed a number of small textual/grammatical things in the Pharo 5 UI as well, so I will dust of the cobwebs on how to create some some slices and see if I can help in a small way.

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

stepharo

Re: How to report website text bugs?

In reply to this post by Tim Mackinnon

On Tue, 29 Nov 2016 00:57:36 +0100, Tim Mackinnon <[hidden email]> wrote:

Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

Thank you for this take :)

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Using Opera's mail client: http://www.opera.com/mail/

Tim Mackinnon

Re: How to report website text bugs?

In reply to this post by EstebanLM

I just tried the new example on the website (factorial is a great example from the command line - I like it).

The output is:

$ ./pharo Pharo.image eval "42 factorial"

'No change'

1405006117752879898543142606244511569936384000000000

$

Out of curiosity, What is the ‘No Change’ message above the answer?

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

EstebanLM

Re: How to report website text bugs?

On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:

I just tried the new example on the website (factorial is a great example from the command line - I like it).

The output is:

$ ./pharo Pharo.image eval "42 factorial"
'No change'
1405006117752879898543142606244511569936384000000000
$

Out of curiosity, What is the ‘No Change’ message above the answer?

no idea :)

obviously… a remaining error :P

Esteban

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

EstebanLM

Re: How to report website text bugs?

On 30 Nov 2016, at 12:09, Esteban Lorenzano <[hidden email]> wrote:

On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:

I just tried the new example on the website (factorial is a great example from the command line - I like it).

The output is:

$ ./pharo Pharo.image eval "42 factorial"
'No change'
1405006117752879898543142606244511569936384000000000
$

Out of curiosity, What is the ‘No Change’ message above the answer?

no idea :)
obviously… a remaining error :P

and btw… that’s obviously a transcript message.

Esteban

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Henrik Nergaard-2

Re: How to report website text bugs?

SystemNavigation new allLocalCallsOn: 'No change' ofClass: ProtoObject .

"a Set(Delay class>>#delaySchedulerClass:)"

From: Pharo-dev [mailto:[hidden email]] On Behalf Of Esteban Lorenzano
Sent: Wednesday, November 30, 2016 12:14 PM
To: Pharo Development List <[hidden email]>
Subject: Re: [Pharo-dev] How to report website text bugs?

On 30 Nov 2016, at 12:09, Esteban Lorenzano <[hidden email]> wrote:

On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:

I just tried the new example on the website (factorial is a great example from the command line - I like it).

The output is:

$ ./pharo Pharo.image eval "42 factorial"

'No change'

1405006117752879898543142606244511569936384000000000

$

Out of curiosity, What is the ‘No Change’ message above the answer?

no idea :)

obviously… a remaining error :P

and btw… that’s obviously a transcript message.

Esteban

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:

Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?

Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.

We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"

-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"

Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Sven Van Caekenberghe-2

Re: How to report website text bugs?

In reply to this post by Tim Mackinnon

Tim,

> On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
>
> I just tried the new example on the website (factorial is a great example from the command line - I like it).
>
> The output is:
>
> $ ./pharo Pharo.image eval "42 factorial"
> 'No change'
> 1405006117752879898543142606244511569936384000000000
> $
>
> Out of curiosity, What is the ‘No Change’ message above the answer?

What version are you using, I just tried (on macOS 10.12.1), in a terminal:

prometheus:pharo6 sven$ curl get.pharo.org/60+vm | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2901 100 2901 0 0 2565 0 0:00:01 0:00:01 --:--:-- 2571
Downloading the latest 60 Image:
http://files.pharo.org/get-files/60/pharo.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/get-files/60/pharo-mac-stable.zip
pharo-vm/Pharo.app/Contents/MacOS/Pharo
Downloading PharoV60.sources:
http://files.pharo.org/get-files/60/sources.zip
Creating starter scripts pharo and pharo-ui

prometheus:pharo6 sven$ ./pharo Pharo.image printVersion
[version] 6.0 #60311

prometheus:pharo6 sven$ ./pharo Pharo.image eval '42 factorial'
1405006117752879898543142606244511569936384000000000

Works like a charm. I assume it works on Linux too.

HTH,

Sven

> Tim
>
>> On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:
>>
>> yes, but no need… I already fixed it :)
>>
>>> On 29 Nov 2016, at 09:29, [hidden email] wrote:
>>>
>>> Report them on pharo.fogbugz.com
>>>
>>> http://pharo.org/contribute-report-bug
>>>
>>> Use Project: Websites as the reference.
>>>
>>> Phil
>>>
>>> On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
>>> Hi Guys - how is the best way to report website and text bugs?
>>>
>>> As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.
>>>
>>> I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)
>>>
>>> Are you using macOS Sierra?
>>> Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
>>> We are working to fix this temporary inconvenience.
>>>
>>>
>>> Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:
>>>
>>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
>>> -bash: !'": event not found
>>>
>>> The culprit is of course the “!” Character so a better example might be:
>>>
>>> $ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
>>> Hello WorldStdioStream: 'stdout'
>>>
>>> Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?
>>>
>>>
>>> Tim
>>>
>>
>

Ben Coman

Re: How to report website text bugs?

In reply to this post by Henrik Nergaard-2

On Wed, Nov 30, 2016 at 7:37 PM, Henrik Nergaard <[hidden email]> wrote:
> SystemNavigation new allLocalCallsOn: 'No change' ofClass: ProtoObject .
>
> "a Set(Delay class>>#delaySchedulerClass:)"

That is only called from two places:
* DelayBenchmark>>bench:
* Delay class >> systemSettingOn:
so it is curious that #delaySchedulerClass: is being invoked.

> From: Pharo-dev [mailto:[hidden email]] On Behalf Of
> Esteban Lorenzano
> Sent: Wednesday, November 30, 2016 12:14 PM
> To: Pharo Development List <[hidden email]>
> Subject: Re: [Pharo-dev] How to report website text bugs?
>
>
> On 30 Nov 2016, at 12:09, Esteban Lorenzano <[hidden email]> wrote:
> On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
>
> I just tried the new example on the website (factorial is a great example
> from the command line - I like it).
>
> The output is:
>
> $ ./pharo Pharo.image eval "42 factorial"
> 'No change'
> 1405006117752879898543142606244511569936384000000000
>
> Out of curiosity, What is the ‘No Change’ message above the answer?
> no idea :)
> obviously… a remaining error :P
> and btw… that’s obviously a transcript message.

actually an #inform:

On Thu, Dec 1, 2016 at 12:14 AM, Sven Van Caekenberghe <[hidden email]> wrote:

> Tim,
>
>> On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
>>
>> I just tried the new example on the website (factorial is a great example from the command line - I like it).
>>
>> The output is:
>>
>> $ ./pharo Pharo.image eval "42 factorial"
>> 'No change'
>> 1405006117752879898543142606244511569936384000000000
>> $
>>
>> Out of curiosity, What is the ‘No Change’ message above the answer?
>
> What version are you using, I just tried (on macOS 10.12.1), in a terminal:
>
> prometheus:pharo6 sven$ curl get.pharo.org/60+vm | bash
> % Total % Received % Xferd Average Speed Time Time Time Current
> Dload Upload Total Spent Left Speed
> 100 2901 100 2901 0 0 2565 0 0:00:01 0:00:01 --:--:-- 2571
> Downloading the latest 60 Image:
> http://files.pharo.org/get-files/60/pharo.zip
> Pharo.image
> Downloading the latest pharoVM:
> http://files.pharo.org/get-files/60/pharo-mac-stable.zip
> pharo-vm/Pharo.app/Contents/MacOS/Pharo
> Downloading PharoV60.sources:
> http://files.pharo.org/get-files/60/sources.zip
> Creating starter scripts pharo and pharo-ui
>
> prometheus:pharo6 sven$ ./pharo Pharo.image printVersion
> [version] 6.0 #60311
>
> prometheus:pharo6 sven$ ./pharo Pharo.image eval '42 factorial'
> 1405006117752879898543142606244511569936384000000000
>
> Works like a charm. I assume it works on Linux too.

I just tried the same with new download of Pharo 5 and it worked
without outputting 'No change'
cheers -ben

Nicolai Hess-3-2

Re: How to report website text bugs?

Am 01.12.2016 12:30 vorm. schrieb "Ben Coman" <[hidden email]>:
>
> On Wed, Nov 30, 2016 at 7:37 PM, Henrik Nergaard <[hidden email]> wrote:
> > SystemNavigation new allLocalCallsOn: 'No change' ofClass: ProtoObject .
> >
> > "a Set(Delay class>>#delaySchedulerClass:)"
>
> That is only called from two places:
> * DelayBenchmark>>bench:
> * Delay class >> systemSettingOn:
> so it is curious that #delaySchedulerClass: is being invoked.
>
> > From: Pharo-dev [mailto:[hidden email]] On Behalf Of
> > Esteban Lorenzano
> > Sent: Wednesday, November 30, 2016 12:14 PM
> > To: Pharo Development List <[hidden email]>
> > Subject: Re: [Pharo-dev] How to report website text bugs?
> >
> >
> > On 30 Nov 2016, at 12:09, Esteban Lorenzano <[hidden email]> wrote:
> > On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
> >
> > I just tried the new example on the website (factorial is a great example
> > from the command line - I like it).
> >
> > The output is:
> >
> > $ ./pharo Pharo.image eval "42 factorial"
> > 'No change'
> > 1405006117752879898543142606244511569936384000000000
> >
> > Out of curiosity, What is the ‘No Change’ message above the answer?
> > no idea :)
> > obviously… a remaining error :P
> > and btw… that’s obviously a transcript message.
>
> actually an #inform:
>
>
>
>
> On Thu, Dec 1, 2016 at 12:14 AM, Sven Van Caekenberghe <[hidden email]> wrote:
> > Tim,
> >
> >> On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
> >>
> >> I just tried the new example on the website (factorial is a great example from the command line - I like it).
> >>
> >> The output is:
> >>
> >> $ ./pharo Pharo.image eval "42 factorial"
> >> 'No change'
> >> 1405006117752879898543142606244511569936384000000000
> >> $
> >>
> >> Out of curiosity, What is the ‘No Change’ message above the answer?
> >
> > What version are you using, I just tried (on macOS 10.12.1), in a terminal:
> >
> > prometheus:pharo6 sven$ curl get.pharo.org/60+vm | bash
> > % Total % Received % Xferd Average Speed Time Time Time Current
> > Dload Upload Total Spent Left Speed
> > 100 2901 100 2901 0 0 2565 0 0:00:01 0:00:01 --:--:-- 2571
> > Downloading the latest 60 Image:
> > http://files.pharo.org/get-files/60/pharo.zip
> > Pharo.image
> > Downloading the latest pharoVM:
> > http://files.pharo.org/get-files/60/pharo-mac-stable.zip
> > pharo-vm/Pharo.app/Contents/MacOS/Pharo
> > Downloading PharoV60.sources:
> > http://files.pharo.org/get-files/60/sources.zip
> > Creating starter scripts pharo and pharo-ui
> >
> > prometheus:pharo6 sven$ ./pharo Pharo.image printVersion
> > [version] 6.0 #60311
> >
> > prometheus:pharo6 sven$ ./pharo Pharo.image eval '42 factorial'
> > 1405006117752879898543142606244511569936384000000000
> >
> > Works like a charm. I assume it works on Linux too.
>
> I just tried the same with new download of Pharo 5 and it worked
> without outputting 'No change'
> cheers -ben
>

It depends on your user settings. If and what set of user settings were exported. And maybe, if there is a set if user settings in the old format.

Tim Mackinnon

Re: How to report website text bugs?

In reply to this post by Sven Van Caekenberghe-2

I found the transcript output from a few days ago when I did it - it was the following (which shows that initial error on the eval example)

macta$ curl get.pharo.org | bash 

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100 12445  100 12445    0     0   235k      0 --:--:-- --:--:-- --:--:--  238k

Downloading the latest 50 Image:

    http://files.pharo.org/get-files/50/pharo.zip

Pharo.image

Downloading the latest pharoVM:

	http://files.pharo.org/get-files/50/pharo-mac-stable.zip

pharo-vm/Pharo.app/Contents/MacOS/Pharo

Downloading PharoV50.sources:

	http://files.pharo.org/get-files/50/sources.zip

Creating starter scripts pharo and pharo-ui

macta$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"

-bash: !'": event not found

When I then try the print version I also get the same message with that same initial setup that I downloaded?

macta$ ./pharo Pharo.image printVersion

'No change'

[version] 5.0 #50764

Tim

On 30 Nov 2016, at 16:14, Sven Van Caekenberghe <[hidden email]> wrote:

Tim,

On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:

I just tried the new example on the website (factorial is a great example from the command line - I like it).

The output is:

$ ./pharo Pharo.image eval "42 factorial"
'No change'
1405006117752879898543142606244511569936384000000000
$

Out of curiosity, What is the ‘No Change’ message above the answer?

What version are you using, I just tried (on macOS 10.12.1), in a terminal:

prometheus:pharo6 sven$ curl get.pharo.org/60+vm | bash
% Total    % Received % Xferd Average Speed   Time    Time     Time Current
                                Dload Upload   Total   Spent    Left Speed
100 2901 100 2901    0     0   2565      0 0:00:01 0:00:01 --:--:-- 2571
Downloading the latest 60 Image:
   http://files.pharo.org/get-files/60/pharo.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/get-files/60/pharo-mac-stable.zip
pharo-vm/Pharo.app/Contents/MacOS/Pharo
Downloading PharoV60.sources:
http://files.pharo.org/get-files/60/sources.zip
Creating starter scripts pharo and pharo-ui

prometheus:pharo6 sven$ ./pharo Pharo.image printVersion
[version] 6.0 #60311

prometheus:pharo6 sven$ ./pharo Pharo.image eval '42 factorial'
1405006117752879898543142606244511569936384000000000

Works like a charm. I assume it works on Linux too.

HTH,

Sven

Tim

On 29 Nov 2016, at 08:41, Esteban Lorenzano <[hidden email]> wrote:

yes, but no need… I already fixed it :)

On 29 Nov 2016, at 09:29, [hidden email] wrote:

Report them on pharo.fogbugz.com

http://pharo.org/contribute-report-bug

Use Project: Websites as the reference.

Phil

On Tue, Nov 29, 2016 at 12:57 AM, Tim Mackinnon <[hidden email]> wrote:
Hi Guys - how is the best way to report website and text bugs?

As I know the English is not always a first language (and you guys are busy writing code anyway) - its up to us native English speakers to chip in where we can.

I was pleased to get the notice that on OSX Sierra I need to do something extra to get Pharo to work, however the text could be slightly corrected eg. (Bolded words changed)

Are you using macOS Sierra?
Due to changes in security policies of macOS, you will need to put the VM in the /Applications folder.
We are working to fix this temporary inconvenience.

Also - the Hello world command line example on the front page doesn’t work on a standard Terminal on a Mac (you get an error:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello,World!'"
-bash: !'": event not found

The culprit is of course the “!” Character so a better example might be:

$ ./pharo Pharo.image eval "Stdio stdout << 'Hello World'"
Hello WorldStdioStream: 'stdout'

Although, in this case, is it expected that the return string is merged with some other output text (e.g. the StdioStream:….?). I think its an impressive example, but it just doesn’t quite look right?

Tim

Ben Coman

Re: How to report website text bugs?

In reply to this post by Nicolai Hess-3-2

On Thu, Dec 1, 2016 at 2:21 PM, Nicolai Hess <[hidden email]> wrote:

> Am 01.12.2016 12:30 vorm. schrieb "Ben Coman" <[hidden email]>:
>>
>> On Wed, Nov 30, 2016 at 7:37 PM, Henrik Nergaard <[hidden email]>
>> wrote:
>> > SystemNavigation new allLocalCallsOn: 'No change' ofClass: ProtoObject .
>> >
>> > "a Set(Delay class>>#delaySchedulerClass:)"
>>
>> That is only called from two places:
>> * DelayBenchmark>>bench:
>> * Delay class >> systemSettingOn:
>> so it is curious that #delaySchedulerClass: is being invoked.
>>
>> > From: Pharo-dev [mailto:[hidden email]] On Behalf Of
>> > Esteban Lorenzano
>> > Sent: Wednesday, November 30, 2016 12:14 PM
>> > To: Pharo Development List <[hidden email]>
>> > Subject: Re: [Pharo-dev] How to report website text bugs?
>> >
>> >
>> > On 30 Nov 2016, at 12:09, Esteban Lorenzano <[hidden email]> wrote:
>> > On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
>> >
>> > I just tried the new example on the website (factorial is a great
>> > example
>> > from the command line - I like it).
>> >
>> > The output is:
>> >
>> > $ ./pharo Pharo.image eval "42 factorial"
>> > 'No change'
>> > 1405006117752879898543142606244511569936384000000000
>> >
>> > Out of curiosity, What is the ‘No Change’ message above the answer?
>> > no idea :)
>> > obviously… a remaining error :P
>> > and btw… that’s obviously a transcript message.
>>
>> actually an #inform:
>>
>>
>>
>>
>> On Thu, Dec 1, 2016 at 12:14 AM, Sven Van Caekenberghe <[hidden email]>
>> wrote:
>> > Tim,
>> >
>> >> On 30 Nov 2016, at 11:26, Tim Mackinnon <[hidden email]> wrote:
>> >>
>> >> I just tried the new example on the website (factorial is a great
>> >> example from the command line - I like it).
>> >>
>> >> The output is:
>> >>
>> >> $ ./pharo Pharo.image eval "42 factorial"
>> >> 'No change'
>> >> 1405006117752879898543142606244511569936384000000000
>> >> $
>> >>
>> >> Out of curiosity, What is the ‘No Change’ message above the answer?
>> >
>> > What version are you using, I just tried (on macOS 10.12.1), in a
>> > terminal:
>> >
>> > prometheus:pharo6 sven$ curl get.pharo.org/60+vm | bash
>> > % Total % Received % Xferd Average Speed Time Time Time
>> > Current
>> > Dload Upload Total Spent Left
>> > Speed
>> > 100 2901 100 2901 0 0 2565 0 0:00:01 0:00:01 --:--:--
>> > 2571
>> > Downloading the latest 60 Image:
>> > http://files.pharo.org/get-files/60/pharo.zip
>> > Pharo.image
>> > Downloading the latest pharoVM:
>> > http://files.pharo.org/get-files/60/pharo-mac-stable.zip
>> > pharo-vm/Pharo.app/Contents/MacOS/Pharo
>> > Downloading PharoV60.sources:
>> > http://files.pharo.org/get-files/60/sources.zip
>> > Creating starter scripts pharo and pharo-ui
>> >
>> > prometheus:pharo6 sven$ ./pharo Pharo.image printVersion
>> > [version] 6.0 #60311
>> >
>> > prometheus:pharo6 sven$ ./pharo Pharo.image eval '42 factorial'
>> > 1405006117752879898543142606244511569936384000000000
>> >
>> > Works like a charm. I assume it works on Linux too.
>>
>> I just tried the same with new download of Pharo 5 and it worked
>> without outputting 'No change'
>> cheers -ben
>>
>
> It depends on your user settings. If and what set of user settings were
> exported. And maybe, if there is a set if user settings in the old format.

Nice pick up. Better to be less verbose...
https://pharo.fogbugz.com/default.asp?19428

cheers -ben