From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use search path for scripts
Date: Thu, 17 Nov 2005 00:04:00 -0000 [thread overview]
Message-ID: <u3blw73ct.fsf@gnu.org> (raw)
In-Reply-To: <437B6718.7070300@st.com> (message from Andrew STUBBS on Wed, 16 Nov 2005 17:06:32 +0000)
> Date: Wed, 16 Nov 2005 17:06:32 +0000
> From: Andrew STUBBS <andrew.stubbs@st.com>
>
> The search strategy employed is the one we have found most useful. If
> the path contains '/' then search relative to current directory first,
> otherwise search the path first.
How about trying in the current directory if the file name does not
have any slash characters? That sounds like the least surprising
behavior, and also keeps backward compatibility.
> doc/
> * gdb.texinfo (Choosing files): Mention that -directory is used
> for script files.
> (Specifying source directories): Likewise.
> (Command files): Explain how script files are found.
This part is approved (but if we decide to change the behavior, please
post a modified patch).
next prev parent reply other threads:[~2005-11-16 20:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:36 Andrew STUBBS
2005-11-17 0:04 ` Eli Zaretskii [this message]
2005-11-17 12:41 ` Andrew STUBBS
2005-11-17 19:42 ` Eli Zaretskii
2005-11-18 13:23 ` Andrew STUBBS
2005-11-18 14:53 ` Eli Zaretskii
2005-11-18 15:54 ` Andrew STUBBS
2005-11-25 18:02 ` Andrew STUBBS
2005-11-25 18:12 ` Daniel Jacobowitz
2005-11-25 18:33 ` Andrew STUBBS
2005-11-25 18:39 ` Daniel Jacobowitz
2005-11-25 20:12 ` Andrew STUBBS
2005-11-25 21:26 ` Daniel Jacobowitz
2005-11-25 22:33 ` Eli Zaretskii
2005-11-28 19:34 ` Andrew STUBBS
2005-11-25 21:56 ` Eli Zaretskii
2005-11-25 21:43 ` Eli Zaretskii
2006-01-12 0:09 ` Andrew STUBBS
2006-01-22 20:40 ` Daniel Jacobowitz
2006-01-23 16:29 ` Andrew STUBBS
2006-01-23 17:41 ` Andrew STUBBS
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=u3blw73ct.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--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