I'm working on modernizing Rosetta Code's infrastructure. Starting with communications. Please accept this time-limited open invite to RC's Slack.. --Michael Mol (talk) 20:59, 30 May 2020 (UTC)

# User talk:Blek

## PowerShell entry

Good day!
Thanks in advance! --Simple9371 (talk) 08:37, 30 June 2015 (UTC)

(Jumping in...) I would say go ahead and make the change - as long as your change is clearly an improvement. That said, if you and Blek need to coordinate, waiting for a conversation also can work quite well. (The reason I say this is that if your change is not clearly an improvement and you are asking permission for that, then that can lead into all sorts of problems. So it's often best to just jump in and try and help and then in the unusual failure mode case where things go sour to back off and let cooler heads prevail.) --Rdm (talk) 13:48, 1 July 2015 (UTC)
Ok. I made the change already. --Simple9371 (talk) 09:05, 2 July 2015 (UTC)
I've seen your changes. Your solution is better than mine. There are many ways to solve each task. Feel free to share your solutions.
Thanks! --Simple9371 (talk) 07:52, 3 July 2015 (UTC)

## Pisano period

In the second equation for the Rosetta Code task   Pisano period:

```  pisano(pK) == p(k-1)pisano(p)
```

You have the 1st   letter   K   spelled in uppercase,   and
you have the 2nd   letter   k   spelled in lowercase.

I would've changed it myself   (for consistency),   but I don't know which (lower/upper) case you preferred in the equation.

I could barely make out the superscripts   (old eyes, I guess).

For equations that use superscripts and/or subscripts, radicals (and other special characters), and also Greek letters,   I normally use:

```  pisano(pk) == p(k-1)pisano(p)
```

-- Gerard Schildberger (talk) 00:55, 5 March 2020 (UTC)

Hi Blek, Gérard, that mistake was mine. Feel free to correct as I am on my mobile at the moment. Thanks.
P.S I too have old eyes. Glasses help me, as does a lovely 7.2" Huawei Mate 20 X phone 😊
--Paddy3118 (talk) 07:20, 5 March 2020 (UTC)