Re: current position of the compilation buffer should be the end, not the start

[Eli Zaretskii]

> From: woods@weird.com (Greg A. Woods)
> Date: Fri, 29 Dec 2000 14:51:24 -0500 (EST)
> 
> The only problem is finding out about this stuff without pouring through
> the manual with a fine-tooth'ed comb!

The way to find specific info in the manual is by using the
index-search command, bound to `i'.

> Texinfo documentation is great if you're in the mood for reading a book,
> but it's not very good as a reference, even with advanced searching
> functions in your viewer, etc.

If you cannot find something using `i', it means that the manual's
indexing needs work; please report that as a documentation bug.  `i'
is _the_ method for using a manual as a reference material.

In the particular case of compilation-scroll-output, please suggest
index entries suitable for finding it.

> Half the problem is that there's no permuted index

Why do you need the index to be permuted?  The `i' command doesn't
require you to type the entry from its beginning, it looks for the
string you type in all the index entries, even if the entry doesn't
begin with what you type.

For example, the index entry for compilation-scroll-output will be
found if you type "i scroll-output RET", even though the index entry
is "compilation-scroll-output".

> This
> variable is a perfect example since it is not mentioned in the main node
> to which it applies (i.e. "Compilation Mode").

Well, I don't agree that this variable applies to the Compilation Mode
node (since the variable is not specific to the Compilation Mode, it
is specific to the compilation buffer).  But I duplicated the fragment
which documents this variable to the Compilation Mode node as well.