From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wordexp
Date: Tue, 30 Dec 2014 13:55:40 +0000 [thread overview]
Message-ID: <20141230135540.GB9985@spoons.adamthompson.me.uk> (raw)
In-Reply-To: <20141130061049.eklhad@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Tue, Dec 30, 2014 at 06:10:49AM -0500, Karl Dahlke wrote:
> After considerable waffling, I decided to give wordexp a try
> for variable expansion and globbing on file names.
> Odds are, we won't notice any difference.
> But at least it is somewhat standard now, and I got rid of a bunch of
> #ifdef Windows dos unix code.
> Some of the old code is still in there under #if 0,
> and I'll get rid of that when I have confidence in the new system.
Ok, everything appears to work ok, though I pushed a change to allow expansion of env variables etc for non-existant file names when writing or setting the file name.
For example:
export tmpdir=/tmp
then:
edbrowse
f $tmpdir/test.txt
w $tmpdir/test_2.txt
Now allows you to set the file name to /tmp/test.txt and write to /tmp/test_2.txt
rather than erroring as it did previously.
Note that, if the file doesn't exist, b,
r and e commands still error as expected.
> Speaking of old stuff, we'll have to decide when to delete
> jsdom.cpp jsloc.cpp js.h.
> That is, when are we committed to the new system?
> Of course, thanks to git, you never really delete stuff,
> you can always get it back if you want it.
Thus I'd say delete it now, since it appears to work just as well as the
previous system.
Cheers,
Adam.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-12-30 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 11:10 Karl Dahlke
2014-12-30 13:55 ` Adam Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-14 1:51 Karl Dahlke
2015-02-14 0:47 Chris Brannon
2014-12-28 21:45 Karl Dahlke
2014-12-29 0:25 ` 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=20141230135540.GB9985@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).