Re: [dev] Text-only browser that sucks less?

From: Silvan Jegen <s.jegen_AT_gmail.com>
Date: Mon, 30 Jun 2014 09:39:26 +0200

On Mon, Jun 30, 2014 at 3:39 AM, Wolfgang Corcoran-Mathe
<first.lord.of.teal_AT_gmail.com> wrote:
> Quoth Nick on Sun, Jun 29 2014 19:56 -0400:
>
>> Quoth Wolfgang Corcoran-Mathe:
>>>
>>> Beyond rendering pages, the biggest
>>> challenge seems to me to lie in coming up with a more intelligent
>>> method of selecting links than the usual crufty vi/emacs/Lynx-style
>>> interfaces.
>>
>>
>> I always liked the way elinks (I think) did it, with a numbers
>> mode where you type the number of the link you want to go to. I
>> did have a similar thing to that working with surf too, but it
>> doesn't work when you disable javascript, which is overall more
>> important for basic usability.
>
>
> Link-numbering works, but it starts to break down with link-heavy
> pages, or, worse, with numeric links. After trying to sift through
> 'Page 1[89] 2[90] 3[91] ... 20[92]' and similar horrors in elinks,
> I had to disable it.


Better than link-numbering using numbers is the link-enumeration using
characters on the homerow on the keyboard:

Page 1[aa] 2[ab] 3[js]...

I am not aware of a text-based browser that works that way though.


Cheers,

Silvan
Received on Mon Jun 30 2014 - 09:39:26 CEST