[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev lynx: questions and suggestions
From: |
Webmaster Jim |
Subject: |
Re: lynx-dev lynx: questions and suggestions |
Date: |
Mon, 29 Mar 1999 06:32:08 -0500 |
On Fri, Mar 26, 1999 at 03:42:51PM +0400, Vlad Harchev wrote:
> Here are some questions:
>
> Memory management:
[...]
Your analysis sounds correct. Zeroing memory is not very
time-consuming, but I've noticed a much longer startup time when
comparing very old lynx (2-3) with today's.
> Keyboard layout:
> * It seems that there are only very few keys that are unassigned. May be it's
> time to switch to handling of key sequences (may be limiting their length by
> two keys for now, like ^x-s)
[a FAQ]
> New features I hope I will be able to add sometime (but I'd like somebody
> implemented them :) :
> *Regex matching
> I'm planning to use Stallman's regex library since it offers the ability to
> select the regex style - for example - whether |,+,?,(,),{,} are special
> symbols (and their slash-escaped versions are literals) or vice versa.
> Since it's impossible to make rx searches in multibyte strings, IMO the
> string
> search command (as implemented now) should be preseved.
> Now, the question is: what keys should the rx searches be assigned to.
> Note: IMO ability to do case sensitve and case insensitive rx-searches is
> very
> desirable (and may be these variants should be treated as different
> commands).
> IMO they should be key-sequences if key sequence support will be
> implemented. What do you think?
Searches should optionally be done with or without regexp support. It
would make sense to use the same keys as the current search method ("/",
"n", "s"). This option should be configurable as well as switchable.
++++++++++++++++++++++++++++
Marvin the Paranoid Android.