gdb.texinfo is getting too big

[Pedro Alves]

On 10/16/2013 08:01 PM, Eli Zaretskii wrote:
>> Date: Wed, 16 Oct 2013 11:55:00 -0700
>> From: Doug Evans <dje@google.com>
>> Cc: gdb-patches <gdb-patches@sourceware.org>, Stan Shebs <stan@codesourcery.com>
>>
>> The worry I have with any kind of grouping not based on the doc itself
>> is that it introduces a potentially non-intuitive layer that someone
>> has to learn in order to know which file contains the text one wants
>> to edit.  grep will find it of course, but if one is having to grep
>> too much, would that be a problem?
> 
> Emacs uses this scheme, and I didn't hear any complaints, FWIW.

Maybe it'd be easier to think in terms of things that would make
sense to split out of the main file.  E.g., the RSP chapter is useful
for GDB and stub developers, but not for regular users -- split that
one out.  Python scripting API stuff is useful for advanced users
that want to extend GDB, but it's not really the same class of manual
as the other chapters, so split that one out as another file too.
MI is useful for frontend writers, not for regular users, so out it
goes too.  Whatever other identifiable logic units we find, split
them out.  Then I suspect we'll end up with the core manual for
regular users that describes GDB's main features/CLI/commands,
and it'll be lean enough to be manageable.

-- 
Pedro Alves