Re: lynx-dev [PATCH] "change directory" command

[Klaus Weide]

On Tue, 18 Jul 2000, Vlad Harchev wrote:
> On Tue, 18 Jul 2000, Ismael Cordeiro wrote:
> > Anyway, your patch fixed it and the problem was corrected in dev.5/dev.6.
> 
>  No, Tom wrote his version of the fix that differs from mine - his version
> won't allow Ctrl-C as synonim for C in the "D)ocument or C)ancel" prompt. I've
> posted the note about this on lynx-dev.

I think you mean Ctrl-G.  Ctrl-C should normally kill lynx.

> > Another confusing thing is the text in userdefs.h: 
> > 
> > | + * SUPPORT_CHDIR provides CD command (bound to 'C' by default). It allows
> > | + * changing directory to arbitrary location (if OS allows them). If dired
> > | + * is enabled, user will be able to visit any directory and view any file
> > | + * allowed accroding to file permissions or ACLs.
> > 
> > To do that one doesn't need the "C" command. One can use the "g" command or
> > follow links in DIRED "to visit any directory and view any file allowed
> > accroding to file permissions or ACLs."
>  
>  In case somebody provides lynx-based services (e.g. advanced BBS), they could
> disable hrefs to parent dir in dired (configure option) and disallow 'g'
> command. If under this setup dired is enabled (for some reason), then using
> 'C' command in dired user will be able to visit any directory (since when in
> dired, 'C' command automatically 'g'oes to the directory specified by 'C'
> command). So, 'C' is unacceptable in that configuration - that comment tells.

If that's what is is supposed to tell, I find the quoted text not clear enough.
It should clearly say "Any attempts to limit access to only certain directories
with other options or -restrictions= flags will be pointless if this feature
is enabled", or something similar.  (Assuming that is actually the case.)

> > >  Thanks for evaluating dev4. Seems nobody else uses it (probably Eduardo
> > > uses it too).
> > 
> > I'm always using the latest version and I believe that many do the same. 
> > It's
> > just that we're not finding many bugs... :-)

Haven't gotten around to it yet.

   Klaus


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden