From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] glob, wordexp
Date: Sun, 28 Dec 2014 14:09:19 -0500 [thread overview]
Message-ID: <20141128140919.eklhad@comcast.net> (raw)
Edbrowse has the feature that you can read or write files using shell variables
and even wildcard expansion, if the result is one file.
I use this feature all the time!
r ~/work/whatever/st*k.c
w $backup/12-25-14.c
and things like that.
Most of this is done by envFile() in stringfile.c,
which is 200 lines of rather awkward code.
I would like to replace most of this with a call to glob or wordexp.
This leverages existing libraries, and is more portable,
since someone else is reading through subdirectories etc.
Are there any reasons I should or should not do this, or any thoughts on this?
I know glob does too little, it doesn't expand shell variables,
but wordexp may do too much,
like all the fancy things bash does to a line.
I need to see how much I can control it with flags.
Karl Dahlke
next reply other threads:[~2014-12-28 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 19:09 Karl Dahlke [this message]
2014-12-28 19:35 ` 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=20141128140919.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).