Alex, I don't know how you plan to implement things, so some of my questions and concerns might seem obvious. > * Keeping the alias definitions within the main ARB script
I'm curious as to how you would achieve the "no longer requiring a refresh" objective if you keep everything in one file. New items in this file would still have to be parsed out wouldn't they? > * Storing ARB aliases as scripts instead of labels eliminates the > need for an alias cache and the inherent rebuilding thereof. I have well over 1000 aliases, and having a script file for each item (some of them very simple, often one line) seems a bit clunky to me. If ARB is to have autocomplete, these files still have to be listed and their names placed into a vector - which is much faster than the current rebuild process, but a rebuild (of the alias vector) nonetheless. Perhaps you will generate the autocomplete list anew whenever ARB is called? How about history? These would still have to be stored and reloaded separately right? > * Storing ARB aliases as scripts with a prefixed name ... Personally I'm not too bothered whether the files are prefixed, stored in a specific folder or both/neither - whichever you find neater. I agree with David's suggestion of a user-defined prefix/path. -- Ravi (http://shell-shocked.org) Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
