Shortcuts have long been a thorn for Pharo, the lack of global state and
the fact that are hard coded. Colors and Themes had the same issue and it
was the effort Esteban who wanted to bring the dark theme that really
changed this. I suspect like Theme these are legacy Squeak stuff that are
not
Le 07/07/2018 à 16:17, Ben Coman a écrit :
> Any seeming agreement may just have been the nay-sayers falling silent since
> there seemed little chance of having it changed when it came as a
> done-deal with Nautilus.
> Personally I tried to conform to using the double-sequence-shortcuts
> but
> Am 07.07.2018 um 16:17 schrieb Ben Coman :
>
>> On 7 July 2018 at 20:35, Norbert Hartl wrote:
>> Maybe I missed an important discussion but as I’m trying pharo7 now and I
>> wonder about the keyboard shortcuts.
>>
>> Wasn’t the old agreement moving to the multiple keys? So browsing
Maybe I missed an important discussion but as I’m trying pharo7 now and I
wonder about the keyboard shortcuts.
Wasn’t the old agreement moving to the multiple keys? So browsing senders with
CMD-bn instead of the old CMD-n?
What I find really confusing is that the shortcut keys in the menu are
I have used Pharo with Git, for versioning source code and variable assets
, images and audio files using filetree and the git client of my choosing.
Git is super flexible , especially if you combine it with make files that I
also use to build my own custom pharo images together with pharo startup
Ciao,
thanks.
> Hi Dario,
>> i'm interested to port all my code to new Pharo version that manage
>> git support.
>>
>> I found information in pharo.org news, it talk of Pharo 6.1.
>>
>> But it run only on macOS 64bits o i can run it on Linux Ubuntu
