bug#13055: 24.3.50; `scroll-margin' not always honored in Info buffers

[Juanma Barranquero]

On Mon, Dec 3, 2012 at 8:34 AM, Dani Moncayo <dmoncayo@gmail.com> wrote:

> IMO, `scroll-margin' clearly makes sense whenever the displayed text
> changes, regardless of the relation between the old displayed text and
> the new one.

I agree with Eli that this is a documentation bug. The very name
"scroll-margin" clearly says that its effect is related to scrolling,
and it's in fact so though the docstring might suggest otherwise. It's
true that <backspace> in an Info buffer would be, from a user's POV, a
"motion command", but not scrolling IMO. Do you also expect M-> M-< to
move the point to the second line of the buffer, or to display a
ghostly empty line above 1st line?

> It should.

That's clearly a matter of opinion.

> Does that behavior (changing the location of the the current line
> after minimizing + restoring the Emacs frame) makes sense to anyone?
> Come on ...

On this one I agree with you. After minimize / restore, Emacs
shouldn't recenter the point. But that's unrelated to scrolling; it's
just that Emacs has a definite affinity for recentering whether the
user wants or not.

> Please Eli, reconsider this.  The meaning of `scroll-margin' makes
> perfectly sense here.

No, you want some new variable (and behavior) `point-margin' or somesuch.

    Juanma