From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] wordexp again
Date: Fri, 17 Apr 2015 09:33:11 -0400 [thread overview]
Message-ID: <20150317093311.eklhad@comcast.net> (raw)
In-Reply-To: <20150417125002.GA14517@toaster.adamthompson.me.uk>
> Basically the "quick check" in envFile is just wrong and needs to go since it
And yet, I feel like this check was doing something from the user's perspective.
Like maybe edbrowse only tries to expand a filename through the shell
if you really intended that it do that.
So it wouldn't try to expand just because the file had a parenthesis or some such.
Maybe that doesn't matter IDK.
And is this really involved at all in the directory backslash bug that started this thread?
Karl Dahlke
next prev parent reply other threads:[~2015-04-17 13:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 21:40 Karl Dahlke
2015-04-17 7:12 ` Adam Thompson
2015-04-17 12:50 ` Adam Thompson
2015-04-17 13:33 ` Karl Dahlke [this message]
2015-04-17 17:59 ` Adam Thompson
2015-04-17 13:47 ` Karl Dahlke
2015-04-17 18:01 ` Karl Dahlke
2015-04-17 21:34 ` Adam Thompson
2015-04-17 21:58 ` Adam Thompson
2015-04-17 22:25 ` Karl Dahlke
2015-04-17 22:43 ` Adam Thompson
2015-04-17 23:14 ` Karl Dahlke
2015-04-17 22:28 ` Adam Thompson
2015-04-17 22:39 ` Karl Dahlke
2015-04-18 10:53 ` Adam Thompson
2015-04-18 4:18 ` Karl Dahlke
2015-04-18 10:49 ` Adam Thompson
2015-04-18 11:34 ` Karl Dahlke
2015-04-18 13:09 ` Adam Thompson
2015-04-18 19:33 ` Chris Brannon
2015-04-18 20:05 ` Adam Thompson
2015-04-18 23:03 ` Chris Brannon
2015-04-18 12:36 ` Karl Dahlke
2015-04-18 12:54 ` Adam Thompson
2015-04-18 13:09 ` Karl Dahlke
2015-04-18 13:24 ` Adam Thompson
2015-04-18 13:45 ` Karl Dahlke
2015-04-18 17:44 ` Adam Thompson
2015-04-18 19:48 ` Karl Dahlke
-- strict thread matches above, loose matches on Subject: below --
2015-01-09 22:44 Karl Dahlke
2015-01-09 22:19 Karl Dahlke
2015-01-09 22:29 ` Chris Brannon
2015-01-09 21:16 Chris Brannon
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=20150317093311.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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;
as well as URLs for NNTP newsgroup(s).