[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFE: allow bash to have libraries
From: |
Clark J. Wang |
Subject: |
Re: RFE: allow bash to have libraries |
Date: |
Fri, 2 Mar 2012 10:54:53 +0800 |
On Fri, Mar 2, 2012 at 08:20, John Kearney <dethrophes@web.de> wrote:
> :) :))
> Personal best wrote about 10000 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.wooledge.org/ReadingFunctionKeysInBash
>
>
> Personally I'd have to say using path to source a moduel is a massive
> securtiy risk but thats just me.
> I actually have a pretty complex bash modules hierarchy solution.
> If anybodys interested I guess I could upload it somewhere if anybodys
> interested,
I just found https://gist.github.com/ a few days ago :)
Gist is a simple way to share snippets and pastes with others. All gists
are git repositories, so they are automatically versioned, forkable and
usable as a git repository.
> its just a play thing for me really but its couple 1000
> lines of code proabely more like 10000+.
> Its kinda why I started updating Gregs wiwi I noticed I'd found
> different/better ways of dealing with a lot of problems.
>
> Thiing like secured copy/move funtions. Task Servers.
> Generic approach to user interface interactions. i.e. supports both
> gui and console input in my scripts.
> Or I even started a bash based ncurses type system :), like I say some
> fune still got some performance issues with that one.
>
> Or improves select function that supports arrow keys and mouse
> selection, written in bash.
>
> Anybody interested in this sort of thing?
>
I'm interested.