From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-17256-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 17846 invoked by alias); 17 Feb 2004 20:13:21 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 17838 invoked from network); 17 Feb 2004 20:13:20 -0000
Received: from unknown (HELO localhost.redhat.com) (216.129.200.20)
  by sources.redhat.com with SMTP; 17 Feb 2004 20:13:20 -0000
Received: from gnu.org (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 378562B92; Tue, 17 Feb 2004 15:13:19 -0500 (EST)
Message-ID: <403275DF.6070209@gnu.org>
Date: Tue, 17 Feb 2004 20:13:00 -0000
From: Andrew Cagney <cagney@gnu.org>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820
MIME-Version: 1.0
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: Pending breakpoints and scripts
References: <4027E74B.6090805@gnu.org> <20040209223227.GA7344@nevyn.them.org> <40294BA1.3020906@gnu.org> <20040210222616.GA32636@nevyn.them.org> <402A3CBB.1060508@gnu.org> <20040211144755.GA487@nevyn.them.org> <40326A70.8050601@gnu.org> <20040217193118.GA31755@nevyn.them.org> <40326DD9.8030807@gnu.org> <20040217194114.GA32400@nevyn.them.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-02/txt/msg00208.txt.bz2


>> >>Lets see if we can pin down the interface (adding JeffJ to the CC list):
>> >>
>> >>nquery("A question?")
>> >>
>> >>	A question? [n]:
>> >>
>> >>	- press return => implied "n"
>> >>	- batch mode => implied "n"
> 
>> >
>> >
>> >How would you feel about "[n/y]"?  Otherwise, I like this.
> 
>> 
>> As in?
> 
> 
> nquery("A question?");
>   A question? (n or y) <CURSOR>
> 
> or
> 
>   A question? [n/y]: <CURSOR>
> 
> Simply to clarify that it is a yes-no question.

Er, ...

 > How about this, we introduce:
 > 	nquery()
 > 	yquery()
 > where the default (batch mode, and when return is pressed is n/y
 > respectively).

with what you suggest, how is the user to differientiate the 
consequences of entering return when presented with either of:
	nquery("A question?")
	A question? [y/n]:
and
	yquery("A question?")
	A question? [y/n]:
something like:
	A question? (y or n) [n]:
would be needed (which would be getting into redundant verbage).
	
Andrew