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 module libary when I started So what I like trap error etc and print error mesages set nounset Try to keep the files in 2 parts source part and run part. Have a common args handler routine. rediculously comples log output etc timestamped, line file function etc... stack trace on errors color output red for errors etc. silly comples userinterface routines :) I guess just have a look see and try it out. Also note I think a lot of the files are empty/or silly files that should actually be deleted don't have time to go through them now though. I'd also advise using ctags, tagging it and navigating so, its what I do. On 03/02/2012 03:54 AM, Clark J. Wang wrote: > On Fri, Mar 2, 2012 at 08:20, John Kearney <dethrop...@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.