From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31438 invoked by alias); 11 Apr 2003 14:32:10 -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 31431 invoked from network); 11 Apr 2003 14:32:09 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 11 Apr 2003 14:32:09 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 20C812B2F; Fri, 11 Apr 2003 10:32:10 -0400 (EDT) Message-ID: <3E96D1E9.7060700@redhat.com> Date: Fri, 11 Apr 2003 14:32:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Rossi Cc: gdb@sources.redhat.com Subject: Re: set prompt & MI References: <20030411115633.GA1783@white> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00110.txt.bz2 > Does gdb plan on providing the 'set prompt' command with MI? > > example below. > > (gdb) > -interpreter-exec console "set prompt (foo) " > ^done > (gdb) The "(gdb)\n" in the above is the MI output terminator: http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC213 and not CLI prompt. The CLI's prompt will have been changed, it just isn't possible to directly see it. Last time this came it, it was suggested that the MI "(gdb)\n" be replaced with "(mi)\n". > 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) " Two possabilities, the -interpreter-exec console output include the CLI prompt vis: (gdb) -interpreter-exec console "set prompt (foo) " ~"(foo) " ^done (gdb) or, MI notify the GUI of changes to internal variables vis: (gdb) -interpreter-exec console "set prompt (foo) " *set,prompt="(foo) " ^done (gdb) or, both. I'm not sure how robust or feasible a generic "*set" event is though. Andrew