Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [RFC] new substitute path when loading feature
Date: Fri, 16 May 2008 15:27:00 -0000	[thread overview]
Message-ID: <uhccyk6gy.fsf@gnu.org> (raw)
In-Reply-To: <482C990A.60500@qnx.com>

> Date: Thu, 15 May 2008 16:11:54 -0400
> From: Aleksandar Ristovski <aristovski@qnx.com>
> CC: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com, 
>  Eli Zaretskii <eliz@gnu.org>
> 
> @Eli: Your 'if' wouldn't work as expected for common posix-style paths (it would default to case insensitive comparison which is unacceptable for posix paths)

I think you misunderstood what I was suggesting, but we don't have to
argue about that, as long as you agree with Daniel's solution (because
I was in effect suggesting the same thing).

> However, I'm not sure why you didn't like my original rewrite at readin... all the user would have to do for mixed path binaries is:
> 
> set substitute-path C: /
> (which would make iberty's IS_ABSOLUTE_PATH work on posix-ly configured gdbs)
> 
> and this could be done by default in main :-)

I think this suggestion is so subtle that no one who has such a
problem would ever be able to guess that substitute-path is the
solution.

In other words, when a user has problem with DOS-style file names, she
will look for a solution whose name has something in common with "DOS"
and "file name", and substitute-path doesn't qualify.  A good UI
should have high mnemonic significance to be helpful.


  parent reply	other threads:[~2008-05-16  8:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 18:56 Aleksandar Ristovski
2008-05-13 19:00 ` Daniel Jacobowitz
2008-05-13 20:24   ` Aleksandar Ristovski
2008-05-13 21:11     ` Daniel Jacobowitz
2008-05-13 21:18       ` Aleksandar Ristovski
2008-05-13 21:40         ` Daniel Jacobowitz
2008-05-15 17:37           ` Daniel Jacobowitz
2008-05-15 19:29             ` Joel Brobecker
2008-05-15 19:30             ` Eli Zaretskii
2008-05-15 19:44               ` Daniel Jacobowitz
2008-05-15 22:40                 ` Eli Zaretskii
2008-05-16  0:28                   ` Daniel Jacobowitz
2008-05-16  8:15                     ` Aleksandar Ristovski
2008-05-16  8:19                       ` Aleksandar Ristovski
2008-05-16  8:21                       ` Daniel Jacobowitz
2008-05-16 15:26                         ` Mark Kettenis
2008-05-16 15:27                           ` Eli Zaretskii
2008-05-16 15:27                         ` Aleksandar Ristovski
2008-05-16 15:27                           ` Aleksandar Ristovski
2008-05-16 15:27                           ` Eli Zaretskii [this message]
2008-05-16 19:21                             ` Aleksandar Ristovski
2008-05-16 19:35                               ` Eli Zaretskii
2008-05-16 19:22                             ` Aleksandar Ristovski
2008-05-16 15:26                       ` Eli Zaretskii
2008-05-15 20:05               ` Joel Brobecker
2008-05-15 19:35             ` Aleksandar Ristovski
2008-05-17 19:49             ` Vladimir Prus
2008-05-19  4:12               ` Vladimir Prus
2008-05-13 21:12     ` Eli Zaretskii

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=uhccyk6gy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /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