Helge Hafting wrote:
Abdelrazak Younes wrote:
This patch (for trunk) mostly fixes the problem. The downside is that
the inset is not automatically "uncollapsed" when you leave the inset
after an automatic opening. The inset might also refuse to collapse if
the cursor is within it in another view.
The user probably have a reason for uncollapsing, and will not object to
the inset getting collapsed in the other view as well.
As a user I am objecting. I uncollapse an inset when I want to view
what's inside or when I want to edit it. If this same buffer is opened
in another window it's because I generally want to edit another part of
the same buffer and I don't want that view to change just because I am
editing some other inset in the other view.
Why not do that?
That's what we are doing actually.
If another view has a cursor inside - do the same thing as we do when
the user close an inset where the first view has the cursor. That is,
move the cursor outside, then close. Or is this hard to program?
It is not very hard but it is bad behavior IMO: I don't want to lose my
cursor position just because I closed the inset in the other view.
Abdel.
