From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28578 invoked by alias); 11 Apr 2003 11:56:35 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 28570 invoked from network); 11 Apr 2003 11:56:33 -0000 Received: from unknown (HELO white) (68.14.146.65) by sources.redhat.com with SMTP; 11 Apr 2003 11:56:33 -0000 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 193x8z-0000TN-00 for ; Fri, 11 Apr 2003 07:56:33 -0400 Date: Fri, 11 Apr 2003 11:56:00 -0000 From: Bob Rossi To: gdb@sources.redhat.com Subject: set prompt & MI Message-ID: <20030411115633.GA1783@white> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-SW-Source: 2003-04/txt/msg00108.txt.bz2 Does gdb plan on providing the 'set prompt' command with MI? example below. (gdb) -interpreter-exec console "set prompt (foo) " ^done (gdb) Also, I kind of think that the prompt should be separated from what the user/front end sees. Maybe do prompt= to tell the front end that the prompt has been reached and what it is. That way front ends are not looking for the string "(gdb) ". ^done,prompt="(gdb) " Bob Rossi