Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] usage of environment variable from the command line
Date: Fri, 21 Sep 2007 22:55:00 -0000	[thread overview]
Message-ID: <20070921225527.GA28500@caradoc.them.org> (raw)
In-Reply-To: <46F13F2A.8010507@st.com>

On Wed, Sep 19, 2007 at 05:24:26PM +0200, Denis PILAT wrote:
> Hi,
> 
> I have a patch that allows to use environment variable when typing commands.
> Environment variable must be surrounded by "%%" string.
> (Ex: "file %%REPOSITORY%%/obj/a.out" would be supported.)
> 
> 
> Is there any chance that such a patch could be accepted ?
> I've read from the gdb mailing list that I'm not the only one who wants to 
> handle environment variable from the command line.

I think it would probably be useful to allow if we can find a way that
won't break something else.

I think that syntax is really ugly :-( Before we go ahead with this
can anyone think of a better one that won't conflict with source
language expressions?

Another problem is escaping.  Right now, you're supposed to be able to
give either quoted strings or raw text to most commands (it
varies, I posted a summary a while back).  Front ends won't know how
to escape the string if you have e.g. %% in your $PWD or want to
print a string containing %%.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-09-21 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 15:24 Denis PILAT
2007-09-21 22:55 ` Daniel Jacobowitz [this message]
2007-09-22  7:16   ` Eli Zaretskii
2007-09-22 13:58     ` Daniel Jacobowitz
2007-09-24 15:05       ` Denis PILAT
2007-09-24 16:44       ` Jim Blandy
2007-09-24 21:41         ` Eli Zaretskii
2007-09-25 17:11           ` Jim Blandy
2007-09-25 21:38             ` Eli Zaretskii
2007-09-30  1:30         ` Daniel Jacobowitz
2007-09-30  7:17           ` Eli Zaretskii
2007-10-11 17:51             ` Daniel Jacobowitz
2007-12-21 15:31             ` Denis PILAT
2007-12-22 19:27               ` 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=20070921225527.GA28500@caradoc.them.org \
    --to=drow@false.org \
    --cc=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    /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