This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: gdb.texinfo is getting too big
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Doug Evans <dje at google dot com>
- Cc: gdb-patches at sourceware dot org, stan at codesourcery dot com
- Date: Wed, 16 Oct 2013 22:01:17 +0300
- Subject: Re: gdb.texinfo is getting too big
- Authentication-results: sourceware.org; auth=none
- References: <CADPb22S7Yjz=um_7P_9M_yS-ko7+jNQXzf8HqtWn3QdWqoD2DA at mail dot gmail dot com> <83ob6rpqa5 dot fsf at gnu dot org> <CADPb22SdNrdrhsQJuQYAzQTEQtj7j+Pwf5VQo05qUETLJ5Zbuw at mail dot gmail dot com> <83mwmbp80v dot fsf at gnu dot org> <CADPb22QOG=kH_HPr59rEZEQPhQh0QS_JYi82W-McmfLf+fifCA at mail dot gmail dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.