Debian Codegraph @

docs/FM.announce

raw
1 LYNX FILE MANAGEMENT SUPPORT
2
3 New facilities have been added since Lynx 2-3 to provide support
4 for managing files on the local filesystem. These facilities allow
5 the user to delete, rename, and re-locate files and/or directories and
6 to create and/or upload new files and directories. This will mainly
7 be of interest to systems administrators who are interested in running
8 lynx as a restricted shell in order to provide controlled access to a
9 range of services (as in a freenet). It may also be of use at sites
10 where some of the users are experiencing difficulty with the raw Unix
11 interface.
12
13 Support for the new facilities is enabled at compile time by defining
14 the variable `DIRED_SUPPORT' in the `MCFLAGS' list in the Lynx
15 Makefile, and in the WWW makefile `CommonMakefile'. Runtime support
16 for disabling the facilities is provided by way of the restriction
17 `dired_support' which can be set on the command line for a particular
18 session.
19
20 The Makefile also provides additional compile time flags for
21 controlling the extent and application of the file management
22 facilities; specifically, `OK_TAR' which enables support for creating
23 and expanding tar archives, `OK_GZIP' which enables use of gzip to
24 compress and decompress files, and `OK_OVERRIDE' which allows access
25 to the file management facilities directly from the keyboard in
26 addition to access by way of a file management menu.
27
28 There are two possible modes of operation; the first in which a single
29 file management menu is invoked via the `f', or `F' key; the second,
30 in which the more often used facilities are made available directly
31 from the keyboard in addition to access via the menu. The second
32 method provides a much better user interface but requires re-mapping
33 some of the keys from their standard lynx interpretation, temporarily
34 when file management mode is in effect. For example, if OK_OVERRIDE is
35 defined at compile-time, then the line at the bottom of the screen, in
36 novice mode, will be
37
38 C)reate D)ownload E)dit F)ull menu M)odify R)emove T)ag U)pload
39
40 rather than the standard second noviceline,
41
42 H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list
43
44 when the user is browsing part of the file system. If OK_OVERRIDE is not
45 defined then all access to file management functionality must be by way
46 of the menu. The only exception is that the facility to tag files for
47 subsequent removal and/or re-location is always available directly from
48 the keyboard using `t', and `T'.
49
50 This is a first release of the file management enhancements and suggestions
51 for improvements are welcome. Among the enhancements which are currently
52 being considered are facilities for changing file access attributes, and
53 a facility for listing and extracting part of an archive.
54
55 In order to use the file management facilities you may either point
56 the program at a directory on the command line or point the program at
57 an html file which contains a link of the following form:
58
59 <a href="file://localhost/~/"> Manage Personal Directory ? </a>
60
61 where the anchor `file://localhost/~/' implies a reference to
62 /home/username. Because the `~/' in a file URL is converted to
63 `/home/username' regardless of origin, these facilities also work when
64 the anchor shown above is served from an http server as well. In
65 either case the reference is to files on the local system and not
66 files in the domain of the server.
67
68 By default the file listing is in standard Unix mixed format, but you
69 may use the Options menu to select WWW `directories first' format, or
70 `files first' format if you prefer.
71
72 Rick Mallett, Carleton University, Ottawa Canada. ([email protected])