Re: [PATCH] window.el: Improve mark management

[Stefan Monnier]

>> `push-mark' is wrong if nothing happened between window-state-get and
>> window-state-put.
>> And the mark & mark-active are buffer-local but not window-local.
>> If we window-state-get in a frame which shows the same buffer several
>> times, window-state-put would end up pushing the same mark several times.

> We could refuse pushing the mark when current and old position are the
> same.  But obviously pushing the mark from a non-current buffer is not
> very reasonable either.

> IIRC all I tried was to emulate the behavior for window configurations.
> What would you suggest instead?  Not save the mark in the first place?

I'm not completely sure.  The current code doesn't seem that bad since,
as you say, it basically reproduces the behavior of
window-configurations.

So I'd like to first hear of what are concrete cases where the current
behavior is a problem.


        Stefan