[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Re: [patch] LYNXMESSAGES:/ without temp-files

From: Henry Nelson
Subject: Re: lynx-dev Re: [patch] LYNXMESSAGES:/ without temp-files
Date: Tue, 19 Oct 1999 10:14:41 +0900 (JST)

> (The VLINKS page is different: following links from there acts just like
> a normal forward link.  LYNXMESSAGES: should probably be reachable from
> the VLINKS page now, I see no reason why it shouldn't.  As well is being

Hmmm.  I use the 'V'isited page MUCH more often than the '^H'istory page,
mainly because the latter can get too cluttered with irrelevant (for me)
information.  I would prefer that ALL internal pages be excluded from the
V page (to keep it concise) and only the ^H page be a "complete" listing
of what was displayed.  Another strategy I could think of would be to do
away with ^H as a hot key (thus freeing ^H for some other use) and have
it as a link, along with the messages list, on the 'V'isited page.  Rather
than two pages, a consolidated and more compact single page:
                                   ^^^^^^^^^^^^ ~~~~~~
                                                             Visited Links Page

        Visited Links (POSTs, bookmark, menu and list files excluded)

                         *  [1][Stack of currently-suspended documents]
                         *  [2][Your recent statusline messages]

  0. [3]< Hello page. >

By "more compact" I specifically mean 1) not putting "Lynx Version 2.8.3dev.9"
on every internal page, 2) not always parroting TITLE in the header, and 3)
doing away with repetitive and obvious message lines like "You visited:".
(I've found some of them so inane that it makes more sense to patch Lynx to
not print them and get rid of one more gettext call -- like _four_ birds
with one stone!)  I mean, why do I have to see "visited" three whole times,
or "printing" or "download", etc?  That's why I pressed ** V **, ** P **, or
** D **; I know already.  Even a first-time user knows already.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]