- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Extra shortcut modifier opposite to #meta

by Tim Mackinnon

I really would like the ability to ctrl-tab (or whatever meta-tab or even meta-some other key) reliably between windows - its frustrating that it only works sometimes via alt-tab. There has been a lot of great work on keyboard shortcuts, which I really appreciate - it would be awesome to finish the job and even add a few more. Does this thread help with this if it was implemented? Tim > On 16 Jun 2017, at 14:22, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-06-14 17:09 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>>: > But meta does also present problems in linux, doesn't it? I mean, meta in linux and windows means Ctrl. That means that overriding meta+arrows will break the Ctrl+arrows text navigation. What am I missing? > > I don't think that alternativeMeta means something useful. And I believe in this topic that there are no magic solutions. Spotter should define for each platform shortcuts that do not override text navigation, > > alternativeMeta will provide reusable solution for such cases.

June 18, 2017

Re: [Pharo-dev] Esteban clone, Pavel clone, Clement clone, Guillermo clone....

by Alistair Grant

Hi Stef, On Sat, Jun 17, 2017 at 08:48:36AM +0200, Stephane Ducasse wrote: > Dear Pharoers > > there are many things that we would like to achieve to offer you a much better > system but we cannot clone ourselves. > > Please let us know if you want to participate building better tools > around for example Iceberg. > > Stef As there haven't been any other replies yet... I've been using Iceberg for a few months without any problems. I've just started trying out Esteban's suggested PR process for Pharo 7 and am starting to see issues. I've got some FileSystem patches which I would like to get in, but once they're done I will hopefully have a chance to look at Iceberg. Just FYI, the FileSystem patches are: - FileRefence>>moveTo: works across disks - FileReference>>/ is more intuitive, i.e. accept directory deliminators in the paramter, and make path canonicalisation consistent (also below). - FileReference>>= considers files equal if they point to the same file / directory. - Path canonicalisation has been tightened up (there's still some room for improvement). - isSymlink works, and all attributes from the libc stat() / lstat() calls are accessible (about 11 new attributes). And file attribute operations and directory enumarating are slightly faster than before. This is a fairly major patch, introducing a new VM plugin (which is why I waited for Pharo 7). And of course, thanks to everyone who has helped make Pharo what it is today. Cheers, Alistair

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Esteban Lorenzano

yes please :) > On 18 Jun 2017, at 15:40, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > HI juraj > > yes it would really cool. > > Stef > > On Sun, Jun 18, 2017 at 1:11 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> >>> El 16-06-2017, a las 19:27, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: >>> >>> >>>> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >>>> >>>> On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >>>>> 2. work on fix/change >>>>> 3. commit/push to your repo >>>>> 4. do a Pull Request once finished. >>>> >>>> Esteban, >>>> >>>> Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. >>> >>> it would be, yes. >>> I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ >> >> Hi, I am currently playing with something like this :-) Well, I am reporting it to a Discord channel because someone may want to report and share troubles that are not related only with Pharo core, e.g., Roassal or other external projects. But we can have two buttons for sure. >> >> I will share it once it is ready for public review. >> >> Juraj >> >>> >>> but then, someone has to program it :) >>> >>> Esteban >>> >>>> >>>> When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. >>>> >>>> Regards .. Subbu >>>> >>>> >>> >>> >> >> >

June 18, 2017

Why allChildrenMatching: does not match extension?

by Stephane Ducasse

Why allChildrenMatching: does not match extension? allChildrenMatching: aPattern "Return all the files and folders recursively nested in the receiver and matching the pattern, aPattern" ^ self allChildren select: [ :each | aPattern match: each basename ] I would rename allChildrenMatching: aPattern into allChildrenNameMatching: aPattern

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

HI juraj yes it would really cool. Stef On Sun, Jun 18, 2017 at 1:11 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> El 16-06-2017, a las 19:27, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: >> >> >>> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >>> >>> On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >>>> 2. work on fix/change >>>> 3. commit/push to your repo >>>> 4. do a Pull Request once finished. >>> >>> Esteban, >>> >>> Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. >> >> it would be, yes. >> I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ > > Hi, I am currently playing with something like this :-) Well, I am reporting it to a Discord channel because someone may want to report and share troubles that are not related only with Pharo core, e.g., Roassal or other external projects. But we can have two buttons for sure. > > I will share it once it is ready for public review. > > Juraj > >> >> but then, someone has to program it :) >> >> Esteban >> >>> >>> When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. >>> >>> Regards .. Subbu >>> >>> >> >> > >

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Juraj Kubelka

> El 16-06-2017, a las 19:27, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: > > >> On 16 Jun 2017, at 16:50, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> >> On Thursday 15 June 2017 08:14 PM, Esteban Lorenzano wrote: >>> 2. work on fix/change >>> 3. commit/push to your repo >>> 4. do a Pull Request once finished. >> >> Esteban, >> >> Step 2 requires an issue to be created in Fogbugz. It would be nice to do this within Pharo itself. > > it would be, yes. > I have even played with the idea of having a âreport bugâ button on debugger for years nowâ¦ Hi, I am currently playing with something like this :-) Well, I am reporting it to a Discord channel because someone may want to report and share troubles that are not related only with Pharo core, e.g., Roassal or other external projects. But we can have two buttons for sure. I will share it once it is ready for public review. Juraj > > but then, someone has to program it :) > > Esteban > >> >> When creating an issue FB requires every detail to be filled in. Most issues arise while testing or debugging, so it would be easy to get most of the details from a debug session or test failure and then file an issue. >> >> Regards .. Subbu >> >> > >

June 18, 2017

Re: [Pharo-dev] Doing a pull request

by Pavel Krivanek

You can just simply do them from Pharo 6 and place them into Pharo 6 inbox. We will then convert them to pull requests as we already did for most of prepared slices. Cheers, -- Pavel 2017-06-17 9:03 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Esteban > > what is the process for people to publish in the inbox of Pharo 70? > This is what we should add in the readme even if it changes. > I have enhancements waiting for a couple of months and I would like to > start pushing them. > > Stef > > > > On Sat, Jun 17, 2017 at 8:41 AM, Stephane Ducasse > <stepharo.self(a)gmail.com> wrote: > > What is the base branch? > > The master? > > > > On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > >> On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: > >>> > >>> Hi, > >>> > >>> I am a GSoC student working on enhancing pharo command line interface. > I > >>> was > >>> wondering if there is a procedure to make a pull request to the Github > >>> repo. > >>> It would be really helpful if someone can explain the right way of > doing a > >>> Pull Request. Thanks in advance. > >> > >> > >> Have you already forked the upstream project in github (aka base) and > >> created a topic branch in your fork (aka head) to hold your changes? > Please > >> post them here or in Discord chat if you need detailed help. Follow the > >> steps in : > >> > >> https://help.github.com/articles/creating-a-pull-request-from-a-fork/ > >> > >> Git jargon may be quite intimidating ;-) for first timers, but the > procedure > >> is really simple. Just remember to start with the "Pull Request" on the > >> *base branch* and not your fork. > >> > >> Regards .. Subbu > >> > >

June 17, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

Esteban what is the process for people to publish in the inbox of Pharo 70? This is what we should add in the readme even if it changes. I have enhancements waiting for a couple of months and I would like to start pushing them. Stef On Sat, Jun 17, 2017 at 8:41 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > What is the base branch? > The master? > > On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: >> On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: >>> >>> Hi, >>> >>> I am a GSoC student working on enhancing pharo command line interface. I >>> was >>> wondering if there is a procedure to make a pull request to the Github >>> repo. >>> It would be really helpful if someone can explain the right way of doing a >>> Pull Request. Thanks in advance. >> >> >> Have you already forked the upstream project in github (aka base) and >> created a topic branch in your fork (aka head) to hold your changes? Please >> post them here or in Discord chat if you need detailed help. Follow the >> steps in : >> >> https://help.github.com/articles/creating-a-pull-request-from-a-fork/ >> >> Git jargon may be quite intimidating ;-) for first timers, but the procedure >> is really simple. Just remember to start with the "Pull Request" on the >> *base branch* and not your fork. >> >> Regards .. Subbu >>

June 17, 2017

Esteban clone, Pavel clone, Clement clone, Guillermo clone....

by Stephane Ducasse

Dear Pharoers there are many things that we would like to achieve to offer you a much better system but we cannot clone ourselves. Please let us know if you want to participate building better tools around for example Iceberg. Stef

June 17, 2017

Re: [Pharo-dev] Doing a pull request

by Stephane Ducasse

What is the base branch? The master? On Thu, Jun 15, 2017 at 8:17 AM, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > On Wednesday 14 June 2017 08:25 PM, Rajula Vineet wrote: >> >> Hi, >> >> I am a GSoC student working on enhancing pharo command line interface. I >> was >> wondering if there is a procedure to make a pull request to the Github >> repo. >> It would be really helpful if someone can explain the right way of doing a >> Pull Request. Thanks in advance. > > > Have you already forked the upstream project in github (aka base) and > created a topic branch in your fork (aka head) to hold your changes? Please > post them here or in Discord chat if you need detailed help. Follow the > steps in : > > https://help.github.com/articles/creating-a-pull-request-from-a-fork/ > > Git jargon may be quite intimidating ;-) for first timers, but the procedure > is really simple. Just remember to start with the "Pull Request" on the > *base branch* and not your fork. > > Regards .. Subbu >

June 17, 2017