The command
lynx -anonymous '-restrictions=?'
under 2.8.4dev17 and dev18 shows that many restrictions have not
been correctly set.
The new "restrictions" table in LYUtils.c does not seem to be
set up properly for the -anonymous restrictions.
The TRUE settings for the "can" field should generally be changed to FALSE
or to the value of an appropriate CAN_ANONYMOUS... variable.
It would also seem that every CAN_ANONYMOUS.. variable in userdefs.h
should be inspected here (or elsewhere) in order that the
configurations specified in userdefs.h take effect. I can't
figure out how that happens.
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]