From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15314 invoked by alias); 23 Jan 2012 17:19:41 -0000 Received: (qmail 15306 invoked by uid 22791); 23 Jan 2012 17:19:40 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Jan 2012 17:19:28 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q0NHJ6BD004074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Jan 2012 12:19:06 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id q0NHJ4Ac003980; Mon, 23 Jan 2012 12:19:05 -0500 Message-ID: <4F1D9688.5030904@redhat.com> Date: Mon, 23 Jan 2012 17:36:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Joel Brobecker CC: GDB Patches Subject: Re: Decouple "set confirm" from `from_tty'. References: <4F194C6F.2080404@redhat.com> <20120120113331.GM31383@adacore.com> In-Reply-To: <20120120113331.GM31383@adacore.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00786.txt.bz2 On 01/20/2012 11:33 AM, Joel Brobecker wrote: >> Eventually, I figured out this was caused by having done >> "set confirm off" before the source command. >> >> (gdb) source /wrong/path/to/file.py >> /wrong/path/to/file.py: No such file or directory. >> (gdb) set confirm off >> (gdb) source /wrong/path/to/file.py >> (gdb) >> >> This was very surprising to me, and I assume to surprise other >> users too. Turns out that "set confirm off" also has the >> side-effect of running commands with from_tty == 0, which >> silences many things. E.g., > > I agree this is very surprising! I'm even amazed that we did not > realize this until now.... Yeah... > Sounds good to me. To me, "set confirm off" means do everything > the same except auto-answer "y" when I said to do something that > GDB think might be questionable. Yeah. > No problem spotted with the patch. Thanks. The patch is now in, committed in two pieces. -- Pedro Alves