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 _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
