On Fri, Sep 06, 2002 at 11:33:16PM +0100, RobertM wrote: > However wouldit be possible rather than adding all of these as > anonymous options to have a compile type option of something like: > ANONYMOUS_RESTRICTIONS= > Which could then be followed by a list of valid restriction options, > so that all options specified there are automatically restricted as if > specified on the command line.
I suppose so. That's equivalent to editing userdefs.h (replaces yet another manual operation with a script ;-) > e.g. specifying at compile time: > ANONYMOUS_RESTRICTIONS="file_url,download,lynxcfg_info" better LYNX_RESTRICTIONS > would cause running "lynx -anonymous" to have the same effect as > running: > lynx -restrictions=file_url,download,lynxcfg_info -anonymous > > This would seem to me to allow far more flexibility with out adding > huge numbers of options, the default would be to leave blank. > > -- > Robm > 873 > "Ask not what I can do for the stupid, > but what the stupid can do for me" - Graeme Garden > > ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED] -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
