> Hi Nicolai, > > On 30 Dec 2013, at 13:26, Nicolai Hess <[email protected]> wrote: > >> for issue 12223 >> >> please revert the changes done for editing history in Nautilus. >> It makes more trouble than it helps. >> It is a nice feature, but it is implementation has too many side effects >> (discard changes on close, lose changes when jump through the >> history, history has a limit) >> If no one has the time to revert this, just give me a GO, and I'll do it :-) >> >> >> Nicolai > > Yes, I think that features has given us a lot of trouble already, I concur > with your conclusion: revert.
Please :) > > Another thing I have been wanting to say to you: I am very impressed and very > happy to see you tackle so many diverse issues with so much energy. You > really embody the ‘just doIt’ tagline. + 1 :) > Thank you very much, I for one, appreciate it a lot ! Yes me too. > > Regards, > > Sven > > BTW, from my perspective you seem to have come from nowhere, which makes your > contributions even more magical. > >> >> 2013/12/30 Marcus Denker <[email protected]> >> >> On 30 Dec 2013, at 12:38, jannik.laval <[email protected]> wrote: >> >>> Hi all, >>> >>> I am porting Phratch in Pharo 3.0 and I have some problems with the >>> interface. >>> I uses a one-click Pharo3.0 #30664 >>> >>> Here is a list of what I have: >>> >>> - in a debugger, it is not possible to do a Cmd-p to evaluate an >>> expression. This appears only if I select with the mouse. If I make the >>> selection with shift-arrow it works. >>> It means that the selection with mouse or with shift-arrow are not the >>> same. >>> >> yes, known bug. Introduced by 12144 TextModel>>getSelection. The only >> solution seems to be to revert tag for now: >> >> https://pharo.fogbugz.com/f/cases/12521/Undo-12144-TextModel-getSelection >> >> This will be in the next update. (I was offline more or less since thursday >> due to helping my brother moving, so this is not integrated yet) >> >>> - In monticello browser: when I select my project, all the repositories >>> available in Pharo are shown. As in Pharo 2.0, it should show only the >>> concerned repositories (2 or 3 max). >>> >> Yes, this was made on purpose and there is an issue that questions if that >> idea was good: >> >> https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies >> (this issue is from July) >> >> >>> - In a browser, when I did a change in the source code of a method, then I >>> select another method, the changes are lost, without asking if I want to >>> save changes. >>> >> >> https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes >> (issue date: 22/11) >> >> In short: if there would be more people *actively* helping on the issue >> tracker front, you would not even have seen those problems. >> >> >> Marcus >> > > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org
