From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] glob
Date: Mon, 29 Dec 2014 16:42:21 +0000 [thread overview]
Message-ID: <20141229164221.GA3513@spoons.adamthompson.me.uk> (raw)
In-Reply-To: <20141128200309.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Sun, Dec 28, 2014 at 08:03:09PM -0500, Karl Dahlke wrote:
> By using wordexp, Adam suggests
>
> > "posix shell" or words to that effect and then it becomes fairly clear
>
> Clear? Really? To you and me maybe. Bash does so many crazy things
> at the shell ... arithmetic, regexp substitution,
> and tries to interpret so many characters as something,
> I really don't want to go there.
> I should be able to call up a file called $phones/at&t
> without having to think about it.
Ok, a couple of things:
wordexp is posix *not* bash. There's an important difference in that it
doesn't do as many crazy substitutions as bash does.
Also we can switch off the command substitution feature which makes things a
little simpler.
In addition, we need to standardise the escape character I think if we use glob as otherwise we're going to have ` for some things and \ for others, that's just a mess.
If you really want to keep your hand-rolled env var expansion,
then we definitely need the ${var} syntax,
and probably the \ as escape character to work with the glob call.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-29 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 1:03 Karl Dahlke
2014-12-29 16:42 ` Adam Thompson [this message]
2014-12-29 18:22 Karl Dahlke
2014-12-29 23:26 ` Adam Thompson
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=20141229164221.GA3513@spoons.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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;
as well as URLs for NNTP newsgroup(s).