RE: S-SPC for non-editing modes

[Drew Adams]

> > But the argument that S-SPC is currently useless because it is
> > unbound is not a reason to bind it for this purpose.
>
> It is not unbound, it duplicates SPC.

S-SPC is not specifically bound. It is mapped to SPC by default. But this
quibble is unimportant.

> > Are new users really finding their habits so terribly violated
> > by Emacs that we need to make changes such as this? PageUp and
> > PageDown are also used in most browsers, and Emacs supports
> > them. How much is enough?
>
> Emacs supports PageUp and PageDown, but in very inconvenient way:
> typing PageUp on the first screen doesn't move point to the beginning of
> the buffer.

OK. Should that be changed? Why have two different behaviors for such
scrolling? Better to duplicate whichever behavior is best. Unless there is a
need for each.

> > Go ahead, if you really think it's helpful. If a better use for
> > S-SPC comes up, I'll argue to change it then. ;-)
>
> I know a better use, but only for editing modes where S-SPC could insert a
> non-breaking space.

I was thinking of that also.