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 modul
On Fri, Mar 2, 2012 at 08:20, John Kearney 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 lines inclu
:) :))
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 http://mywiki
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 initializatio
On Wednesday 29 February 2012 17:53:21 Linda Walsh wrote:
> Eric Blake wrote:
> > On 02/29/2012 12:26 PM, Linda Walsh wrote:
> >>> Any pathname that contains a / should not be subject to PATH searching.
> >
> > Agreed - as this behavior is _mandated_ by POSIX, for both sh(1) and for
> > execlp(2)
On 02/29/2012 11:53 PM, Linda Walsh wrote:
>
>
> Eric Blake wrote:
>
>> On 02/29/2012 12:26 PM, Linda Walsh wrote:
>>
Any pathname that contains a / should not be subject to PATH
searching.
>>
>> Agreed - as this behavior is _mandated_ by POSIX, for both sh(1)
>> and for execlp(2) an
Eric Blake wrote:
On 02/29/2012 12:26 PM, Linda Walsh wrote:
Any pathname that contains a / should not be subject to PATH searching.
Agreed - as this behavior is _mandated_ by POSIX, for both sh(1) and for
execlp(2) and friends.
Is it that you don't read english as a first language, or
