[PATCH 0/7] Adding startup files to GDB

[Eli Zaretskii]

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed,  7 Oct 2020 21:05:04 +0100
> Cc: Tom Tromey <tom@tromey.com>
> 
> This series introduces a new set of command line options and config
> files that can be read very early during the startup process, these
> files/command line flags can then be used to control the very early
> actions that would otherwise not be user controllable.

Even after I've read the documentation parts of the entire series
(which was confusing due to the docs being dispersed between the
messages, and the basic issue with email that you cannot ensure the
order in which the messages wind up in the addressee's inbox), I must
say that I don't understand why we need to expose the startup settings
as normal user options changeable during a session.  Since changing
those settings during a session is useless, why have them as options
at all?  We could simply honor them as "options" only in the startup
files, and do away with the auto-saving feature.  After all, how hard
is it for a developer who uses GDB to debug his/her programs to start
up an editor and edit the startup file?  It sounds like much ado about
nothing to me.  FWIW.

Thanks.