This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH] util.c + doc [was Re: [RFC] Queries and frontends]

 > Doesn't this amount to using "set confirm off"?
 > I might have missed it, but I don't remember why you didn't want
 > use that instead?

In the console, the user can type "set confirm on/off" according to his
preference.  This change ensures that confirmation isn't required for commands
that the frontend runs behind the users back independently of this setting,
provided they are prefixed with "server".  This is only for CLI commands and
does not affect frontends which use GDB/MI.

 > And this solution does not help (some) frontends with 
 > answering 'y' to nquery()

nquery will indeed default to 'n'.

 > How about:
 >    if (! caution)
 >        return def_value;
 >    if (server_command)
 >        return 1;

That might give surprising results, e.g. accidentally setting pending

AFAIK this change is for _one_ frontend (Emacs) to use _one_ command (record
stop).  I think too much generality detracts from this objective as, unlike
GDB/MI, the plan is not to develop annotations.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]