[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev lynx2.8.3dev.17
From: |
Vlad Harchev |
Subject: |
Re: lynx-dev lynx2.8.3dev.17 |
Date: |
Thu, 16 Dec 1999 18:17:24 +0400 (SAMT) |
On Fri, 17 Dec 1999, Henry Nelson wrote:
> > As other say, no .lynxrc option exists for it. It should be saved
> > somewhere,
> > and I don't insist on lynx.cfg at all.
>
> Whew! Glad to hear that.
The need of saving options is so obvious..
> > > "feature" itself. All it does for me in its present form is 1) take away
> > > 2 lines of information that I want on the Visited Page, 2) when I try to
> > > change back to a regular list, after pressing enter on the accept changes
> > > I am thrown back to the page I was viewing before rather than a revised
> > > Visited Page, and 3) it just keeps moving the visited links more and more
> > > to the right so that long ones quickly have to be wrapped (making them
> > > harder to read AND wasting more space). To me it is worthless and I don't
> > > want it, but there is no way for me to turn it off. Why do I have to be
> > > the one to create and maintain a backout patch?
> >
> > 1) For Tree mode, those 2 lines added are not visible since page is
> > scrolled
>
> ? Below is the out-of-the-box Visited Links Page. I'm talking about that
> " [View As Visit Tree___________] Accept Changes" line and the following
> blank line.
>
> Visited Links
> Page
>
> Visited Links Page (Lynx$B%P!<%8%g%s(J 2.8.3dev.16)
>
> [View As Visit Tree___________] Accept Changes
>
> You visited (POSTs, bookmark, menu and list files excluded):
> 0. [1]
> ***** snipped ********
> ==> 5. [6]NoxWeeds Project List
> http://endeavor.des.ucdavis.edu/weeds/specieslist.asp
Of course I understand what lines you meant. I said that if your session
lasts some time and you've visited a lot of files in the session, VLP will
occupy several pages. Currently selected link will be the one that corresponds
to documend opened recently - so last link on the VLP will be current (at
least for Tree mode) - this means that VLP will be scrolled to the last page
so you won't see 2 lines you are talking about.
> > 3) This seems a problem, but for Tree mode only. I don't know how to fix
this
>
> That's what I mean! Who needs it?
It's easier to fix it than remove this feature. At least this doesn't harm
you I guess - seems you don't use Tree Mode.
Your "who needs it?" could be treated as "everybody thinks it's useless".
If yes then how did you get this info?
> > hope that you won't be willing to do so that much when all problems listed
> > will be fixed.
>
> _If_ and _when_, we'll see.
>
> > > I also am very much opposed to allowing the Visited Page posting (writing
> > > to disk) privileges.
> >
> > I see this as useless feature too (but I'd like to be able to have much
> > more
> ^^^^^^^
> I'm not saying "useless." In this case I am specifically saying
> _undesirable_.
Seems that I misunderstood something when posting this note (Seems I was
thinking about special support for VLP page - ie that VLP page is saved on
exit, loaded at startup and that new entries are appended to it). Now I wish
to correct my POV: I haven't saved my VLP (ie didn't use ability to save VLP),
but disabling the ability to save VLP seems useless for me.
> > bookmark files than 26, so I won't have to invent one-letter association for
> > bookmark files. Having implemented ability for adding (and probably
> > deleting) links to/from arbitrary files will allow user to save favorite
> > links
> > from his/her session to some file - IMO 95% of links in the V.L. page would
> > b
>
> I don't really understand your point here. What I do is 'a' => 'l' with
> the Visited Page, though in my case I would say that is closer to 99.9% of
> the links are useless/redundant. All of my bookmark files are hand-edited
> except for one "pending" bookmark that is left stock so Lynx can do erasures
> safely, so I have the use of ul nesting and links to sub-bookmarks on disk,
> granted Lynx can't use them directly.
Of course anything could be done manually...
> __Henry
>
Best regards,
-Vlad
Re: lynx-dev lynx2.8.3dev.17, David Combs, 1999/12/16
Re: lynx-dev lynx2.8.3dev.17, Henry Nelson, 1999/12/16
Re: lynx-dev lynx2.8.3dev.17, Henry Nelson, 1999/12/17
- Re: lynx-dev lynx2.8.3dev.17,
Vlad Harchev <=