From: Andrew STUBBS <andrew.stubbs@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Use search path for scripts
Date: Fri, 25 Nov 2005 18:33:00 -0000 [thread overview]
Message-ID: <438752FE.9070302@st.com> (raw)
In-Reply-To: <20051125175735.GB736@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Fri, Nov 18, 2005 at 02:45:13PM +0000, Andrew STUBBS wrote:
>
>> * cli-cmds.c: Include fcntl.h.
>> (source_command): Use the GDB search path to find script files.
>>
>>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.
>
>
> Could you explain why you used the source path to search for scripts,
> instead of a separate search path? Was it just because it was handy?
> Are scripts likely to be in manually-added directories on the source
> search path?
>
> I don't see the correspondence.
Because it was handy, but who says it is the 'source search path'? It's
just that that's all it's been used for up till now.
The source directory is as likely a place as any for script files
(perhaps with some commands to help visualise the data). As it happens
we *always* add a directory (via -d in a wrapper) which contains nothing
but scripts, but since there are no sources that causes no problems.
Conversely, there's no technical reason why they couldn't have different
search paths. However, having more may lead to confusion, command/option
bloat, and the possibility that the user will have to add the same path
twice - once to each path.
If you wish I can split it out into a new list, with new commands, new
command-line options and new documentation. It solves the same problems
in the end.
Thanks
Andrew Stubbs
next prev parent reply other threads:[~2005-11-25 18:11 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
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 [this message]
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=438752FE.9070302@st.com \
--to=andrew.stubbs@st.com \
--cc=drow@false.org \
--cc=eliz@gnu.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