From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: denis.pilat@st.com, gdb-patches@sourceware.org
Subject: Re: [RFC] usage of environment variable from the command line
Date: Sat, 22 Sep 2007 07:16:00 -0000 [thread overview]
Message-ID: <u6423186h.fsf@gnu.org> (raw)
In-Reply-To: <20070921225527.GA28500@caradoc.them.org> (message from Daniel Jacobowitz on Fri, 21 Sep 2007 18:55:27 -0400)
> Date: Fri, 21 Sep 2007 18:55:27 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org
>
> I think that syntax is really ugly :-(
Yes, because it comes from the DOS/Windows shell syntax. I don't
think we should use it, as it makes trouble even in the Windows shell.
> Before we go ahead with this can anyone think of a better one that
> won't conflict with source language expressions?
How about env("FOO") ? Or maybe $env("FOO"), to avoid a possibility
that the debuggee has a real function by the name of `env'?
> 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 %%.
The above suggestion solves this problem as well, I think.
next prev parent reply other threads:[~2007-09-22 7:16 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
2007-09-22 7:16 ` Eli Zaretskii [this message]
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=u6423186h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=denis.pilat@st.com \
--cc=drow@false.org \
--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