If no one has the time to revert this, just give me a GO, and I'll do it :-)history, history has a limit)It is a nice feature, but it is implementation has too many side effects (discard changes on close, lose changes when jump through theplease revert the changes done for editing history in Nautilus.It makes more trouble than it helps.
Nicolai2013/12/30 Marcus Denker <marcus.denker@inria.fr>
yes, known bug. Introduced by 12144 TextModel>>getSelection. The only solution seems to be to revert tag for now:
On 30 Dec 2013, at 12:38, jannik.laval <jannik.laval@gmail.com> 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.
>
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)
Yes, this was made on purpose and there is an issue that questions if that idea was good:
> - 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).
>
https://pharo.fogbugz.com/f/cases/10551/All-Monticello-Repositories-are-added-to-all-Working-Copies
(this issue is from July)
https://pharo.fogbugz.com/f/cases/12223/Nautilus-loses-changes
> - 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.
>
(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