This is the mail archive of the gdb-patches@sourceware.org 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]


 

> -----Original Message-----
> From: Nick Roberts [mailto:nickrob@snap.net.nz] 
> Sent: Thursday, July 30, 2009 12:40 AM
> To: Marc Khouzam
> Cc: Tom Tromey; gdb-patches@sourceware.org
> Subject: 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.

You are right, that won't help me.
Sorry about the confusion.

> 
>  > 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
> breakpoints.
> 
> 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.
> 
> -- 
> Nick                                           
> http://www.inet.net.nz/~nickrob
> 


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