Emacs has always had the concept of a "hook", like a hook on the wall where you can hang, NOT a coat or hat but rather some CODE, that (once something is hanging from the hook) gets executed whenever execution hits that point. Is a really cool concept -- distribute these hooks around in interesting places in the emacs code, and then the USER can use an emacs' USER-cmd to PLACE code on this or that hook, and he has CHANGED how emacs works -- without EVER having to see (or hack!) the emacs's source! (All he has to do is read in the user-manual how to ADD something to one of the pre-placed hooks. And know ENOUGH of the language that the emacs interpreter knows (emacs lisp) to be able to WRITE the code he wants to hang there.) Seems like "hooks" would be a neat feature for lynx, ESPECIALLY for the SYS-ADMINS who have various in-house "customers" -- it would let them add pseudo-features TO lynx, and quickly, too. ---- Now, some lynx-hackers on this list also know PERL, a not bad language for perhaps adding quicko extensions to lynx -- esp with all the string-stuff, internet-stuff, etc, that it provides. Myself, am still learning perl (one HUGE language, filled with "dwim" that (unlike in emacs with IT'S dwim) you MUST know in order to read any code (which is I suppose why some people prefer python -- which itself might be a good (better?) lang for these "personal-extensions" to lynx)) -- -- but SOME LYNX-hackers likely also program in perl (or python, or scheme, or SOMETHING that might be good for this) -- which is why I make this suggestion to our list. -- So, perhaps a hook could be placed at, for instance, the central "get and execute next command" loop , enabling us to add our own commands? Etc, etc. Any comments or ideas on this "hooks for lynx" idea? David ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
