From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14349 invoked by alias); 20 Jan 2012 11:33:54 -0000 Received: (qmail 14341 invoked by uid 22791); 20 Jan 2012 11:33:53 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 20 Jan 2012 11:33:41 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 6C40A2BB3E4; Fri, 20 Jan 2012 06:33:40 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id M39iFNgLqqS2; Fri, 20 Jan 2012 06:33:40 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 042262BB3A8; Fri, 20 Jan 2012 06:33:39 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 0DEC2145615; Fri, 20 Jan 2012 15:33:31 +0400 (RET) Date: Fri, 20 Jan 2012 14:31:00 -0000 From: Joel Brobecker To: Pedro Alves Cc: GDB Patches Subject: Re: Decouple "set confirm" from `from_tty'. Message-ID: <20120120113331.GM31383@adacore.com> References: <4F194C6F.2080404@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F194C6F.2080404@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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/msg00731.txt.bz2 > 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.... > So I'd like to stop it doing that. > Comments? 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. No problem spotted with the patch. -- Joel