Re: LYNX-DEV A bunch of patches

[Klaus Weide]

On Mon, 9 Dec 1996, Ryan Hung wrote:
> On Thu, 5 Dec 1996, Klaus Weide wrote:
> > I did some fixes of the DIRED code.  Most of them are now included in
> > Hiram Lester's composite updates, available from
> > 
> >         <URL: http://www.mtsu.edu/~ripa0003/lynx.html>.
> >
> > The zip problem should be already fixed.
> 
> I'll take a look ASAP.
> 
> [snip]
> > > LYGetFile.c:
> > > 
> > > - One small change so that documents are reloaded after finishing a
> > > lynxprog or lynxexec.  Because Lynx does not reload no-cache pages after
> > > exiting from a lynxprog or lynxexec, as it should.
> > 
> > Could you explain why you think it should?
> 
> Well, in general, anytime running a lynxprog or lynxexec changes something
> on the screen prior to loading the program, the changes should be
> reflected on that screen.  E.g., on our system, we have a CGI for the
> E-mail page which both provides a link to Pine through a lynxprog link, as
> well as providing an index of messages in the user's inbox.  If the E-mail
> page is not updated after exiting from Pine, the page no longer provides a
> current display of the status of the user's inbox.

Sounds like a nice system.  Yes, I see why you want to reload the page
in that case.  But isn't this just a case of a more general problem,
that one URL has no way to affect the caching of another?  I could also
imagine that someone would want something like that if the link is not
a lynxprog link but a more "normal" link.  Anyway I don't know how often
lynxprogs links are used in such a way...

---

I think one could actually define one new function in LYLocal.c, as
a general handler for running-a-command-for-all-tagged-files,
and then have various DIRED_MENU definitions which use that.  For example
in your case:

DIRED_MENU:TAG::blah::LYNXDIRED://DO_WITH_ALL_TAGGED/usr/bin/zip%20-9jrq 
DIRED_MENU:TAG::blah::LYNXDIRED://DO_WITH_ALL_TAGGED/usr/bin/sz%20-b%20-w1024

Then adding some new compressor or whatever could be done without
recompiling.  But of course then lynx.cfg has to be totally trusted.

  Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;