John Kearney wrote: ...
[large repetitive included text elided...]
why not just do something like this?
26 line suggested 'header' elided...
gives you more control anyway, pretty quick and simple.
At least 30% of the point of this is to take large amounts
of common initialization
:) :))
Personal best wrote about 1 lines of code which finally became
about 200ish to implement a readkey function.
Actually ended up with 2 solutions 1 basted on a full bash script
vt100 parser weighing in a about 500 lines including state tables and
a s00 line hack.
Check out
On 2/29/12 2:42 PM, Eric Blake wrote:
In the middle of the histrionics and gibberish, we have the nugget of an
actual proposal (thanks, Eric):
[to allow `.' to look anchored relative pathnames up in $PATH]
About the best we can do is accept a patch (are you willing to write it?
if
On Fri, Mar 2, 2012 at 08:20, John Kearney dethrop...@web.de wrote:
:) :))
Personal best wrote about 1 lines of code which finally became
about 200ish to implement a readkey function.
Actually ended up with 2 solutions 1 basted on a full bash script
vt100 parser weighing in a about 500
https://github.com/dethrophes/Experimental-Bash-Module-System/blob/master/bash/template.sh
So can't repeat this enough !play code!!.
However suggestions are welcome. If this sort of thing is of
interesting I could maintain it online I guess.
basically I wan kinda thinking perl/python
On 03/02/2012 02:50 AM, Chet Ramey wrote:
On 2/29/12 2:42 PM, Eric Blake wrote:
In the middle of the histrionics and gibberish, we have the nugget of an
actual proposal (thanks, Eric):
[to allow `.' to look anchored relative pathnames up in $PATH]
About the best we can do is
