Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

+1 > On 08 Aug 2016, at 11:31, Nicolas Passerini wrote: > > Hi, > > I think that whatever default behavior and shortcuts you decide, it would be > nice to be able to configure it. So, if someone does not feel comfortable > with the default, he has a simple way to

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

+1 On 8/8/16 2:31 AM, Nicolas Passerini wrote: Hi, I think that whatever default behavior and shortcuts you decide, it would be nice to be able to configure it. So, if someone does not feel comfortable with the default, he has a simple way to change it and configure in a way that gets

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Hi, I think that whatever default behavior and shortcuts you decide, it would be nice to be able to configure it. So, if someone does not feel comfortable with the default, he has a simple way to change it and configure in a way that gets better along with his way of using Pharo. Don't you think?

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Nicolai, It is good to encourage this, but it is a reality that it is a lot of work to do a good job of complaining and criticizing and personally I have a talk at ESUG that needs work, so I won't have the luxury of detailed criticisms much longer :) and I'm sure that this is an issue for

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Hi, > On Aug 7, 2016, at 5:48 PM, Ben Coman wrote: > > On Sun, Aug 7, 2016 at 9:16 PM, Tudor Girba wrote: >> Hi Stef, >> >> We had a thread on that two months ago, and it is still waiting for your >> answer. I made concrete proposals on which

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

On Sun, Aug 7, 2016 at 9:16 PM, Tudor Girba wrote: > Hi Stef, > > We had a thread on that two months ago, and it is still waiting for your > answer. I made concrete proposals on which bindings can work. It would be > more constructive to focus on those details (see more

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Often the reason of annoyance is either time consuming or simply complicated to detail. Anyway, personally, I am not really perturbed by the button location. The print-it in the debugger is no more an annoyance when the Cmd-c bidding can simply copy the print-it. It is exactly what I wish to do

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

2016-08-07 16:10 GMT+02:00 Tudor Girba : > Hi Dale, > > Thanks for your thoughts. And thanks for giving these new quirks time to > settle :). > > Actually, I am looking for what is annoying and I specifically interested > in the reasons why it is annoying. Please feel free

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Hi Dale, Thanks for your thoughts. And thanks for giving these new quirks time to settle :). Actually, I am looking for what is annoying and I specifically interested in the reasons why it is annoying. Please feel free to report the bits that annoy you. Cheers, Doru > On Aug 7, 2016, at

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

On 8/7/16 6:16 AM, Tudor Girba wrote: Hi Stef, That is why we made the default printing not affect the text editor, and this feature is around since almost 2 years and, except of you, there was no other complain. I believe that this is a logical fallacy ... many developers are too busy

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

Hi Stef, We had a thread on that two months ago, and it is still waiting for your answer. I made concrete proposals on which bindings can work. It would be more constructive to focus on those details (see more below). First, one thing should get clarified. The case in which someone wants to

Re: [Pharo-dev] when Cmd-P can just display a string in the debugger

On Sun, Aug 7, 2016 at 3:39 PM, stepharo wrote: > Hi > > Seriously I do not get why printing in the debugger cannot just print the > text without putting these ^%&*^*&()**(&%^*( double quote around. I believe the behaviour was introduced for the Workspace/Playground so that

[Pharo-dev] when Cmd-P can just display a string in the debugger

Hi Seriously I do not get why printing in the debugger cannot just print the text without putting these ^%&*^*&()**(&%^*( double quote around. Why do we change such basic functionality and in particular we do not propose ANY alternative. If you need a pop up and do not care of manipulating