Re: More keybindings in compilation-mode-map

[Kim F. Storm]

In my proposals for additions to the compilation-mode-map I am (naturally)
biased towards *my* daily use of M-x compile:

I'm practially always running Make with M-x compile, so maybe my additions
really belongs in something like a 'make-compile-minor-mode-map'.

Anyway, below are my reasons for the proposed commands:

> 
>           t  toggles `truncate-lines'
> 
> Do you really use this often in Compilation mode?  If so, when?

Yes, very often!
The project I'm working on uses a lot of compiler options, so lines are
often +500 characters.

Sometimes, I just want to browse through the compiler output looking for
error messages, and then I want to truncate those long lines.  
But to see the name of the current file or view the compiler options,
I need to look near the whole compilation line - so I toggle
truncate-lines.

I guess the same would be useful when looking at grep output with long
lines (if you are only interesting in getting an overview of where things
occur).

> 
>           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.
> 
Most of the time, I'm compiling a project which consist of a hierarchy
of sub-projects, each with their own makefile.
So when I'm looking at the error messages for a specific file in a 
sub-project, it would be nice to hit `C-c m' and get the makefile for that
project.  Some form of heuristics is probably needed here, but it should
be possible to look for "Entering directory" in the make output and
find make files based on that.


>           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.
>
Well, as explained above, it is the makefile that started the whole
build process.  So I could also have called it "master makefile".
 
>           d  shows dependencies for current file (show .d file if it exists)
> 
> What do you mean by "current file", in compilation mode?
Well, some heuristics is needed here too - probably looking for a .c file
in a gcc command, etc.

>  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.)

At least gcc can make a .d file with dependencies for a .c file.
My proposal was simply to open that file in view mode.

Anyway, - except for the truncate-lines toggle - most of this seems to
be rather specific to my environment, so it probably isn't worth adding
it to compile mode in general.