Re: More keybindings in compilation-mode-map

[Richard Stallman]

    * view-mode like bindings (SPC, DEL for scrolling, possibly keys for
      scrolling by lines)

I can see why you would want this, but it won't work.
SPC and DEL need to have their ordinary editing meanings
for editing input to send to the compiler.  For the same reason,
letters like t and m cannot be given other definitions.

However, some other special bindings can be added if they
are on C-c or other places that don't get in the way of
normal editing.

    * command to advance point to next error message,
      ditto for previous error message

These are a reasonable addition.  Maybe put them on M-{ and M-},
since paragraphs in the usual sense are useless, and this makes
a reasonable definition of paragraph in Compilation mode. 

    * next-error, previous-error, compile-goto-error

compile-goto-error is bound to RET.  next-error is C-x `.  It might be
good to add nicer and symmetrical bindings for next-error and
previous-error.

    * M-x revert-buffer RET (this starts the compilation again)

That is a bad idea--it will do drastic things that the user does not
expect.  Anyway, M-x recompile is an easy way to start the compilation
again.

    * a command that selects the buffer from which the user hit M-x
      compile RET

I am not sure this is very useful, but if people find it useful,
I have nothing against it.

            t  toggles `truncate-lines'

Do you really use this often in Compilation mode?  If so, when?

            m  opens the makefile used to compile the current file

M-x compile is not always used to run Make.  Anyway, I think that is
of limited usefulness--or perhaps I just don't understand it.

            M  opens the base makefile

What is a "base makefile"?  I don't know that terminology.  Perhaps
this command would fit more logically in Makefile mode.

            d  shows dependencies for current file (show .d file if it exists)

What do you mean by "current file", in compilation mode?  Anyway, I
think this command would fit more logically in Makefile mode.  And
how would it figure out the dependencies?

(I am not sure what you mean by a .d file.)