From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Eli Zaretskii <eliz@gnu.org>,Ofir Cohen <ofircohenn@gmail.com>
Cc: "ssbssa@yahoo.de" <ssbssa@yahoo.de>,"gdb@sourceware.org"
<gdb@sourceware.org>
Subject: Re: building gdb with TUI support on Windows
Date: Thu, 01 Jan 2015 16:48:00 -0000 [thread overview]
Message-ID: <9E85FD9B-532C-46CA-B658-5EC0E4A49E5C@oarcorp.com> (raw)
In-Reply-To: <83h9wabgfu.fsf@gnu.org>
On January 1, 2015 10:42:45 AM CST, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 1 Jan 2015 18:33:35 +0200
>> From: Ofir Cohen <ofircohenn@gmail.com>
>> Cc: Hannes Domani <ssbssa@yahoo.de>, "gdb@sourceware.org"
><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
next prev parent reply other threads:[~2015-01-01 16:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:13 Ofir Cohen
2014-12-26 8:04 ` Eli Zaretskii
2014-12-27 13:53 ` Ofir Cohen
[not found] ` <CAHOBVAdux2M9aRnkJh1hDm_9VCTD6kVzWkF2fjj84qy8UJuh7w@mail.gmail.com>
2014-12-27 14:13 ` Eli Zaretskii
2014-12-27 14:40 ` Hannes Domani
2014-12-27 18:32 ` Eli Zaretskii
2014-12-28 13:58 ` Hannes Domani
2014-12-28 16:41 ` Ofir Cohen
2014-12-28 17:09 ` Hannes Domani
2014-12-28 23:34 ` Ofir Cohen
2014-12-29 0:41 ` Hannes Domani
2014-12-29 15:28 ` Ofir Cohen
[not found] ` <946370725.2390231.1419869855237.JavaMail.yahoo@jws11110.mail.ir2.yahoo.com>
2014-12-29 16:20 ` Hannes Domani
2014-12-30 19:15 ` Hannes Domani
2014-12-30 20:10 ` Ofir Cohen
2014-12-30 20:39 ` Hannes Domani
2014-12-31 16:34 ` Eli Zaretskii
2015-01-01 12:28 ` Hannes Domani
2015-01-01 15:42 ` Eli Zaretskii
2014-12-31 21:12 ` Ofir Cohen
2015-01-01 14:26 ` Hannes Domani
2015-01-01 15:14 ` Ofir Cohen
2015-01-01 15:47 ` Eli Zaretskii
2015-01-01 16:33 ` Ofir Cohen
2015-01-01 16:42 ` Eli Zaretskii
2015-01-01 16:48 ` Joel Sherrill [this message]
2015-01-01 17:18 ` Eli Zaretskii
[not found] ` <CAHOBVAcF824319G6O_LfJBYAQP3M0-LbhAV_d=SrR6jM4=0k5w@mail.gmail.com>
[not found] ` <83d26ybcap.fsf@gnu.org>
2015-01-02 0:32 ` Ofir Cohen
2014-12-28 18:38 ` Sergio Durigan Junior
2014-12-29 2:43 ` Joel Brobecker
2014-12-29 3:15 ` Joel Sherrill
2014-12-29 3:21 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9E85FD9B-532C-46CA-B658-5EC0E4A49E5C@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=ofircohenn@gmail.com \
--cc=ssbssa@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox