Involves two major changements in bash usage. First, you won't need the cd command anymore: to enter a directory, simply go with its name as it would be a command, and let bash take the most appropriate action depending on the type, permissions, etc of the corresponding object. Second, you'll win triggers: every directory accessed in the lazy-way (without the cd builtin) will trig two I/O batches, called '.getin' and '.getout'. More precisely the '.getout' batch of the leaving directory (if present) will be executed before than the '.getin' batch of the entering directory (if present as well). In other words - except for the chdir side-effect - entering in a directory is now pretty equivalent to execute its triggers (when available). Clearly this opens new ways of user's interaction and system development (think about bash callbacks for example.) NOTICE This patch has been successfully tested for nearly one year on several production workstations. However, in case of problems you can inhibit its functioning via the LAZY_DISABLE variable. Please keep in mind that _often_ such problems are due to bugs in the target scripts and _not_ in the lazycd code itself (see RCS ebuild as a good exponent of such cases.) Sooner or later I'll submit LazyCD to the mainstream, but in the meantime comments are welcome (dmr@gmx.it).
Created attachment 104474 [details] Silly patching ebuild (just applies lazycd patch below.)
Created attachment 104476 [details, diff] LazyCD patch
i imagine some people would like this change, but i think that it'd break default spec defined behavior and for many, that would simply not be acceptable i would very much prefer it to go upstream, but i'm 99% sure upstream would reject it ... but i'm not upstream, so what do i know :)
(In reply to comment #3) > i imagine some people would like this change, but i think that it'd break > default spec defined behavior and for many, that would simply not be acceptable > > i would very much prefer it to go upstream, but i'm 99% sure upstream would > reject it ... but i'm not upstream, so what do i know :) ...and this is the very reason why I haven't submitted it to the upstream yet - really I have no time to vaste in discussions :-) Anyway if someone would give it a chance, I'll be glad to receive your feedback : comments, ideas, insults are welcome :-). Newer versions of lazycd will be posted right here: http://www.c0nc3pt.com/patches/bash-lazy-cd Bye
personally, i dont think i'd use the patch ... i typo things too often and i think your semantic changes would accept it as lazy input :) you could try and find peeps on the forums ... there are always people willing to run just about anything
