[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev "sticky" things, and a half-serious proposal
From: |
Vlad Harchev |
Subject: |
Re: lynx-dev "sticky" things, and a half-serious proposal |
Date: |
Mon, 18 Oct 1999 15:24:14 +0500 (SAMST) |
On Sun, 17 Oct 1999, Klaus Weide wrote:
> On Sun, 17 Oct 1999 address@hidden wrote:
>[...]
>
> Well, I have come up with the ultimate option:
>
> # The LAKABOFTIF option controls controls how lynx behaves when a
> # Left Arrow Key is pressed while the text cursor is at the Beginning
> # Of a Form Text Input Field (in line-edition mode). The normal behavior
> # of the Left Arrow key is to return to the previous document in browsing
> # history (PREV_DOC). This option can be used for setting various different
> # behaviors in the specific situation, to prevent accidentally leaving
> # the current document when you didn't mean to.
> # LAKABOFTIF takes directives in the form 'action=condition', several of
> # these can be given separated by comma. Condition is one of:
> # NEVER - never do this (same as omitting 'action' altogether)
> # ALWAYS - always do this
> # IF_CHANGED - if the current text input field was edited
> # IF_NOT_EMPTY - if the current text input field is empty
> # IF_FORMS_CHANGED - if *any* form fields in the current page were changed
> # Action is one of:
> # PROMPT - Lynx will ask what to do, giving a choice of going to the
> # previous document or staying in the input field.
> # IGNORE - The key is ignored, and the cursor remains in the input field.
> # BEEP - The key is ignored as for IGNORE, additionally lynx tries to
> # produce and audible warning.
> # COMMIT - The last editing changes (if any) will be committed, instead
> # of being forgotten, even if lynx exits from line editing to
> # return to the previous document. This is useful in case you
> # return later to the current document while it is still in
> # memory, for example by following a forward link again.
> # If several 'action=condition' pairs are given, [ ...to be filled in... ]
> # If no LAKABOFTIF option is specified, the default is to PROMPT
> # if the input field has been changed, and to never IGNORE or BEEP.
> # If the option is present but empty, i.e. just 'LAKABOFTIF:', The Left
> # Arrow key always has its PREV_DOC meaning (or other, if changed with
> # a KEYMAP options).
> #
> #LAKABOFTIF:PROMPT=IF_CHANGED
Klaus, how serious are you about this proposal?
>[...]
Best regards,
-Vlad
- Re: lynx-dev "sticky" things, (continued)
- Re: lynx-dev "sticky" things, Klaus Weide, 1999/10/16
- Re: lynx-dev "sticky" things, Vlad Harchev, 1999/10/16
- Re: lynx-dev "sticky" things, Klaus Weide, 1999/10/16
- Re: lynx-dev "sticky" things, Janina Sajka, 1999/10/16
- Re: lynx-dev "sticky" things, Klaus Weide, 1999/10/17
- Re: lynx-dev "sticky" things, mattack, 1999/10/16
- Re: lynx-dev "sticky" things, Klaus Weide, 1999/10/17
- Re: lynx-dev "sticky" things, Leonid Pauzner, 1999/10/17
- Re: lynx-dev "sticky" things, mattack, 1999/10/17
- Re: lynx-dev "sticky" things, and a half-serious proposal, Klaus Weide, 1999/10/17
- Re: lynx-dev "sticky" things, and a half-serious proposal,
Vlad Harchev <=
- Re: lynx-dev "sticky" things, and a half-serious proposal, Klaus Weide, 1999/10/18
- Re: lynx-dev "sticky" things, and a half-serious proposal, Vlad Harchev, 1999/10/18
- Re: lynx-dev "sticky" things, and a half-serious proposal, Klaus Weide, 1999/10/18
- Re: lynx-dev "sticky" things, and a half-serious proposal, Vlad Harchev, 1999/10/18
- Re: lynx-dev "sticky" things, and a half-serious proposal, Klaus Weide, 1999/10/18
- Re: lynx-dev "sticky" things, and a half-serious proposal, Leonid Pauzner, 1999/10/18
- Re: lynx-dev "sticky" things, Leonid Pauzner, 1999/10/16
- Re: lynx-dev "sticky" things, mattack, 1999/10/16
- Re: lynx-dev "sticky" things, Vlad Harchev, 1999/10/16
- Re: lynx-dev "sticky" things, Klaus Weide, 1999/10/16