lynx-dev
[Top][All Lists]
Advanced

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

lynx-dev patch: lynx.cfg (was jumping)


From: Philip Webb
Subject: lynx-dev patch: lynx.cfg (was jumping)
Date: Tue, 13 Apr 1999 02:52:49 -0400 (EDT)

990413 Henry Nelson recommended:
>  JUMPFILE:./ltest/lynx2-8-2/jumps.html
> In the distribution lynx.cfg file, there are the instructions:
> # Do not include "file://localhost" in the definition.
> [...] #JUMPFILE:/Lynx_Dir/jumps.html

the following don't work:
 
JUMPFILE:/ltest/lynx2-8-2/jumps.html
JUMPFILE:./ltest/lynx2-8-2/jumps.html
JUMPFILE:~/ltest/lynx2-8-2/jumps.html

the next one does:

JUMPFILE:/homes/purslow/ltest/lynx2-8-2/jumps.html

this is bizarre: is there anywhere else
where the full  file://...  doesn't work nor does simply  ~... ,
but the spelled-out local-system path does?

anyway, yet another oldie among the documentation:  lynx.cfg  patch below.

*** old/lynx.cfg        Fri Mar  5 14:47:43 1999
--- new/lynx.cfg        Tue Apr 13 02:41:37 1999
***************
*** 82,111 ****
  #
  #JUMP_PROMPT:Jump to (use '?' for list):
  
! # JUMPFILE is the default local file checked for shortcut URLs when
! # the user presses the 'J' (JUMP) key.  The user will be prompted for
! # a shortcut entry (analogously to 'g'oto), and can enter one
! # or use '?' for a list of the shortcuts with associated links to
! # their actual URLs.  See the jumps files in the lynx*/samples
! # subdirectory.  Make sure your jumps file includes a '?' shortcut
! # for a file://localhost URL to itself:
  #
  # <dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>
  #
- # If not defined here or in userdefs.h, the JUMP command will invoke
- # the NO_JUMPFILE statusline message (see userdefs.h).
- #
  # On VMS, use Unix SHELL syntax (including a lead slash) to define it.
  #
! # Do not include "file://localhost" in the definition.
! #
! # Additional alternate jumps files can be defined and mapped to
! # keystrokes at the bottom of lynx.cfg, but you should first define
! # the default jumps file (mapped by default to 'J', and to 'j' when
! # the "VI keys" 'o'ption is not ON) here or in userdefs.h, if you
! # wish to implement the jumps mechanism.
! #
! #JUMPFILE:/Lynx_Dir/jumps.html
  
  # Set JUMPBUFFER to TRUE if you want to have the previous jump target,
  # if any, offered for reuse or editing when using the 'J'ump command.
--- 82,109 ----
  #
  #JUMP_PROMPT:Jump to (use '?' for list):
  
! # JUMPFILE is the local file checked for short-cut names for URLs
! # when the user presses the 'j' (JUMP) key.  The user will be prompted
! # to enter a short-cut name for an URL, which Lynx will then follow
! # in a similar manner to 'g'oto; alternatively, s/he can enter '?'
! # to view the full JUMPFILE list of short-cuts with associated URLs.
! # There is an example jumps file in the samples subdirectory.
! # If not defined here or in  userdefs.h , the JUMP command will invoke
! # the NO_JUMPFILE statusline message (cp  LYMessages_en.h ).
  #
+ # To allow '?' to work, include in the JUMPFILE
+ # a short-cut to the JUMPFILE itself, e.g.
  # <dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>
  #
  # On VMS, use Unix SHELL syntax (including a lead slash) to define it.
  #
! # Additional jumps files can be defined and mapped to keystrokes
! # in  lynx.cfg , but you should first define the default jumps file,
! # which is mapped by default to 'j' (or 'J' when VI keys are ON).
! #
! # In the following line, include the actual full local path to JUMPFILE,
! # but do not include 'file://localhost' in the line.
! #JUMPFILE:/FULL_LOCAL_PATH/jumps.html
  
  # Set JUMPBUFFER to TRUE if you want to have the previous jump target,
  # if any, offered for reuse or editing when using the 'J'ump command.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto

reply via email to

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