From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2628 invoked by alias); 1 Jan 2015 16:48:50 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 2618 invoked by uid 89); 1 Jan 2015 16:48:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: OARmail.OARCORP.com Received: from oarmail.oarcorp.com (HELO OARmail.OARCORP.com) (67.63.146.244) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Jan 2015 16:48:48 +0000 Received: from [192.168.0.9] (24.96.88.41) by OARmail.OARCORP.com (192.168.2.2) with Microsoft SMTP Server (TLS) id 8.3.342.0; Thu, 1 Jan 2015 10:48:45 -0600 User-Agent: K-9 Mail for Android In-Reply-To: <83h9wabgfu.fsf@gnu.org> References: <1158788672.3333170.1420122368468.JavaMail.yahoo@jws11107.mail.ir2.yahoo.com> <83lhlmbj0v.fsf@gnu.org> <83h9wabgfu.fsf@gnu.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: Re: building gdb with TUI support on Windows From: Joel Sherrill Date: Thu, 01 Jan 2015 16:48:00 -0000 To: Eli Zaretskii ,Ofir Cohen CC: "ssbssa@yahoo.de" ,"gdb@sourceware.org" Message-ID: <9E85FD9B-532C-46CA-B658-5EC0E4A49E5C@oarcorp.com> X-IsSubscribed: yes X-SW-Source: 2015-01/txt/msg00007.txt.bz2 On January 1, 2015 10:42:45 AM CST, Eli Zaretskii wrote: >> Date: Thu, 1 Jan 2015 18:33:35 +0200 >> From: Ofir Cohen >> Cc: Hannes Domani , "gdb@sourceware.org" > >> >> I launch gdb from DOS, using: >> 1) set PATH=c:\msys64\mingw64\bin;%PATH% >> 2) c:\gdb\build\gdb\gdb --tui >> >> When launching from DOS, how does it find ~/.inputrc? >> Will the following work: >> 1. Set HOME=c:/temp/ >> 2. populate c:/temp/.inputrc with your contents (for example) >> 3. Launch gdb >> >> ? >> >> Will readline successfully locate the DOS path to ~/.inputrc ? > >Sure, why not? It works for me. This sounds like a workable solution but it requires each user to do this. Will this be documented? The other solution fixes it without any other user being impacted. Just pointing out there is a difference. --joel