Debian Codegraph @

lynx_help/Lynx_users_guide.html

raw
1 <!-- $LynxId: Lynx_users_guide.html,v 1.166 2026/05/26 08:24:07 tom Exp $ -->
2 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
3 <html>
4 <head>
5 <meta name="generator" content=
6 "HTML Tidy for HTML5 for Linux version 5.6.0">
7 <title>Lynx Users Guide v2.9.3</title>
8 <link rel="author" href="mailto:[email protected]">
9 <meta http-equiv="Content-Type" content=
10 "text/html; charset=us-ascii">
11 <meta name="description" content=
12 "This is the user's guide to Lynx, giving detailed information on how to use the program, and how to change its configuration using the options menu.">
13 </head>
14 <body>
15 <h1>Lynx Users Guide v2.9.3</h1>
16
17 <p>Lynx is a fully-featured <em>World Wide Web</em>
18 (<em>WWW</em>) client for users running cursor-addressable,
19 character-cell display devices (e.g., vt100 terminals, vt100
20 emulators running on PCs or Macs, or any other character-cell
21 display). It will display <em>Hypertext Markup Language</em>
22 (<em>HTML</em>) documents containing links to files on the local
23 system, as well as files on remote systems running <em>http</em>,
24 <em>gopher</em>, <em>ftp</em>, <em>wais</em>, <em>nntp</em>,
25 <em>finger</em>, or <em>cso</em>/<em>ph</em>/<em>qi</em> servers,
26 and services accessible via logins to <em>telnet</em>,
27 <em>tn3270</em> or <em>rlogin</em> accounts (see <a href=
28 "lynx_url_support.html">URL Schemes Supported by Lynx</a>).
29 <a href="#Hist">Current</a> versions of Lynx run on Unix, VMS,
30 Windows3.x/9x/NT and later, 386DOS and OS/2 EMX.</p>
31
32 <p>Lynx can be used to access information on the <em>WWW</em>, or
33 to build information systems intended primarily for local access.
34 For example, Lynx has been used to build several <em>Campus Wide
35 Information Systems</em> (<em>CWIS</em>). In addition, Lynx can
36 be used to build systems isolated within a single LAN.</p>
37
38 <h2 id="TOC"><a name="Contents" id="Contents">Table of
39 Contents</a></h2>
40
41 <ul>
42 <li><a href="#Help" name="ToC-Help" id="ToC-Help">Lynx online
43 help</a></li>
44
45 <li><a href="#Local" name="ToC-Local" id="ToC-Local">Viewing
46 local files with Lynx</a></li>
47
48 <li><a href="#Leaving" name="ToC-Leaving" id=
49 "ToC-Leaving">Leaving Lynx</a></li>
50
51 <li><a href="#Remote" name="ToC-Remote" id=
52 "ToC-Remote">Starting Lynx with a Remote File</a></li>
53
54 <li><a href="#EnVar" name="ToC-EnVar" id="ToC-EnVar">Starting
55 Lynx with the WWW_HOME environment variable.</a></li>
56
57 <li><a href="#IntraDocNav" name="ToC-IntraDocNav" id=
58 "ToC-IntraDocNav">Navigating hypertext documents with Lynx</a></li>
59
60 <li><a href="#Disposing" name="ToC-Disposing" id=
61 "ToC-Disposing">Printing, Mailing, and Saving rendered files to
62 disk.</a></li>
63
64 <li><a href="#LocalSource" name="ToC-LocalSource" id=
65 "ToC-LocalSource">Viewing the HTML document source and editing
66 documents</a></li>
67
68 <li><a href="#RemoteSource" name="ToC-RemoteSource" id=
69 "ToC-RemoteSource">Downloading and Saving source files.</a></li>
70
71 <li><a href="#ReDo" name="ToC-ReDo" id="ToC-ReDo">Reloading
72 files and refreshing the display</a></li>
73
74 <li><a href="#Search" name="ToC-Search" id="ToC-Search">Lynx
75 searching commands</a></li>
76
77 <li><a href="#InteractiveOptions" name="ToC-InteractiveOptions"
78 id="ToC-InteractiveOptions">Lynx Options Menu</a></li>
79
80 <li><a href="#Mail" name="ToC-Mail" id="ToC-Mail">Comments and
81 mailto: links</a></li>
82
83 <li><a href="#News" name="ToC-News" id="ToC-News">USENET News
84 posting</a></li>
85
86 <li><a href="#Bookmarks" name="ToC-Bookmarks" id=
87 "ToC-Bookmarks">Lynx bookmarks</a></li>
88
89 <li><a href="#Jumps" name="ToC-Jumps" id="ToC-Jumps">Jump
90 command</a></li>
91
92 <li><a href="#DirEd" name="ToC-DirEd" id="ToC-DirEd">Directory
93 Editing</a></li>
94
95 <li><a href="#ColorMouse" name="ToC-ColorMouse" id=
96 "ToC-ColorMouse">Using Color &amp; the Mouse</a></li>
97
98 <li><a href="#MiscKeys" name="ToC-MiscKeys" id=
99 "ToC-MiscKeys">Scrolling and Other useful commands</a></li>
100
101 <li><a href="#Forms" name="ToC-Forms" id="ToC-Forms">Lynx and
102 HTML Forms</a> | <a href="#Images" name="ToC-Images" id=
103 "ToC-Images">Lynx and HTML Images</a></li>
104
105 <li><a href="#Tables" name="ToC-Tables" id="ToC-Tables">Lynx
106 and HTML Tables</a> | <a href="#Tabs" name="ToC-Tabs" id=
107 "ToC-Tabs">Lynx and HTML Tabs</a></li>
108
109 <li><a href="#Frames" name="ToC-Frames" id="ToC-Frames">Lynx
110 and HTML Frames</a> | <a href="#Banners" name="ToC-Banners" id=
111 "ToC-Banners">Lynx and HTML Banners</a></li>
112
113 <li><a href="#Footnotes" name="ToC-Footnotes" id=
114 "ToC-Footnotes">Lynx and HTML Footnotes</a> | <a href="#Notes"
115 name="ToC-Notes" id="ToC-Notes">Lynx and HTML Notes</a></li>
116
117 <li><a href="#Lists" name="ToC-Lists" id="ToC-Lists">Lynx and
118 HTML Lists</a></li>
119
120 <li><a href="#Quotes" name="ToC-Quotes" id="ToC-Quotes">Lynx
121 and HTML Quotes</a></li>
122
123 <li><a href="#Eightbit" name="ToC-Eightbit" id=
124 "ToC-Eightbit">Lynx and HTML Internationalization: 8bit,
125 UNICODE, etc.</a></li>
126
127 <li><a href="#USEMAP" name="ToC-USEMAP" id="ToC-USEMAP">Lynx
128 and Client-Side-Image-Maps</a></li>
129
130 <li><a href="#Refresh" name="ToC-Refresh" id="ToC-Refresh">Lynx
131 and Client-Side-Pull</a></li>
132
133 <li><a href="#Cookies" name="ToC-Cookies" id="ToC-Cookies">Lynx
134 and State Management</a> (Me want <em>cookie</em>!)</li>
135
136 <li><a href="#Cache" name="ToC-Cache" id="ToC-Cache">Lynx and
137 Cached Documents</a></li>
138
139 <li><a href="#Sessions" name="ToC-Sessions" id=
140 "ToC-Sessions">Lynx and Sessions</a></li>
141
142 <li><a href="#Invoking" name="ToC-Invoking" id=
143 "ToC-Invoking">The Lynx command line</a></li>
144
145 <li><a href="#Environment" name="ToC-Environment" id=
146 "ToC-Environment">Environment variables used by Lynx</a></li>
147
148 <li><a href="#lynx.cfg" name="ToC-lynx.cfg" id=
149 "ToC-lynx.cfg">Main configuration file lynx.cfg</a></li>
150
151 <li><a href="#Hist" name="ToC-Hist" id="ToC-Hist">Lynx
152 development history</a></li>
153 </ul>
154
155 <h2 id="id-Help"><a name="Help" id="Help">Lynx online help</a></h2>
156
157 <p>Online help is available while viewing any document. Press the
158 &ldquo;<samp>?</samp>&rdquo; or &ldquo;<samp>H</samp>&rdquo; key
159 (or the &ldquo;<samp>h</samp>&rdquo; key if vi-like key movement
160 is not on) to see a list of help topics. See the section titled
161 <a href="#IntraDocNav">Navigating hypertext documents with
162 Lynx</a> for information on navigating through the help
163 files.</p>
164
165 <p>In addition, a summary description of all the Lynx keystroke
166 commands and their key bindings is available by pressing the
167 &ldquo;<samp>K</samp>&rdquo; key (or the
168 &ldquo;<samp>k</samp>&rdquo; key if vi-like key movement is not
169 on).</p>
170
171 <p>If you want to recall recent status-line messages, you can do
172 so by entering the &ldquo;g&rdquo; command, followed by
173 &ldquo;LYNXMESSAGES:&rdquo;.</p>
174
175 <p>[<a href="#ToC-Help">ToC</a>]</p>
176
177 <h2 id="id-Local"><a name="Local" id="Local">Viewing local files
178 with Lynx</a></h2>
179
180 <p>Lynx can be started by entering the Lynx command along with
181 the name of a file to display. For example these commands could
182 all be used to display an arbitrary ASCII text or HTML file:</p>
183
184 <dl>
185 <dt>UNIX</dt>
186
187 <dd><code>lynx filename</code>
188 </dd>
189
190 <dd><code>lynx /home/my-dir/filename</code>
191 </dd>
192
193 <dd><code>lynx ~/filename</code>
194 </dd>
195
196 <dt>VMS</dt>
197
198 <dd><code>lynx filename</code>
199 </dd>
200
201 <dd><code>lynx dua5:[my-directory]filename</code>
202 </dd>
203
204 <dd><code>lynx /dua5/my-directory/filename</code>
205 </dd>
206
207 <dd><code>lynx ~/filename</code>
208 </dd>
209
210 <dd><code>lynx sys$login:filename</code>
211 </dd>
212
213 <dd><code>lynx /sys$login/filename</code>
214 </dd>
215
216 <dt>Win32/DOS</dt>
217
218 <dd><code>lynx file:///filename</code>
219 </dd>
220
221 <dd><code>lynx filename</code>
222 </dd>
223
224 <dd><code>lynx c:/dir/filename</code>
225 </dd>
226
227 <dd><code>lynx //n/dir/filename</code>
228 </dd>
229 </dl>
230
231 <p>When executed, Lynx will clear the screen and display as much
232 of the specified file as will fit on the screen. Pressing a
233 <em>down-arrow</em> will bring up the next screen, and pressing
234 an <em>up-arrow</em> will bring up the previous screen. If no
235 file is specified at startup, a default file will be displayed,
236 depending on settings e.g., in <em>lynx.cfg</em>.</p>
237
238 <p>Lynx will display local files written in the <em>HyperText
239 Markup Language</em> (<em>HTML</em>), if the file's name ends
240 with the characters <em>.html</em>, <em>.htm</em>,
241 <em>.shtml</em>, <em>.htmlx</em>, <em>.html3</em>, or
242 <em>.ht3</em>. HTML is a file format that allows users to create
243 a file that contains (among other things) hypertext links to
244 other files. Several files linked together may be described as a
245 <em>hypertext document</em>. If the filename does not have one of
246 the suffixes mapped by Lynx to HTML, the <em>-force_html</em>
247 command line option can be included to force treatment of the
248 file as hypertext.</p>
249
250 <p>When Lynx displays an HTML file, it shows links as "bold face"
251 text, except for one link, which is shown as "highlighted" text.
252 Whether "boldface" or "highlighted" text shows up as reverse
253 video, boldface type, or a color change, etc. depends on the
254 display device being used (and the way in which that device has
255 been configured). Lynx has no control over the exact presentation
256 of links.</p>
257
258 <p>The one link displayed as "highlighted" text is the currently
259 "selected" link. Lynx will display the file associated with the
260 selected link when a <em>right-arrow</em> or a <em>Return</em>
261 key is pressed. To select a particular link, press the
262 <em>up-arrow</em> or <em>down-arrow</em> keys until the desired
263 link becomes "highlighted," and then press the
264 <em>right-arrow</em> or <em>Return</em> key to view the linked
265 information. Information included in the HTML file tells Lynx
266 where to find the linked file and what kind of server will
267 provide it (i.e., HTTP, Gopher, etc.).</p>
268
269 <p>Lynx renders HTML files and saves the rendition (and the
270 source, if so configured in the <a href="#lynx.cfg">lynx.cfg</a>
271 file) for initial display and should you select the link again.
272 If you do select a link again and have reason to desire a new
273 fetch and rendering of the file, use the NOCACHE command,
274 normally mapped to &ldquo;<samp>x</samp>&rdquo; and
275 &ldquo;<samp>X</samp>&rdquo;, instead of the <em>right-arrow</em>
276 or <em>Return</em> key when positioned on the link. You also can
277 force a new fetch and rendering of the currently displayed
278 document via the RELOAD command, normally mapped to
279 <em>Control-R</em>.</p>
280
281 <p>When a binary file is encountered Lynx will ask the user if
282 he/she wishes to download the file or cancel. If the user selects
283 &ldquo;<samp>D</samp>&rdquo; for download, Lynx will transfer the
284 file into a temporary location and present the user with a list
285 of options. The only default option is <em>Save to disk</em>,
286 which is disabled if Lynx is running in anonymous mode.
287 Additional download methods may be defined in the <a href=
288 "#lynx.cfg">lynx.cfg</a> file. Programs like kermit, zmodem and
289 FTP are some possible options.</p>
290
291 <p>[<a href="#ToC-Local">ToC</a>]</p>
292
293 <h2 id="id-Leaving"><a name="Leaving" id="Leaving">Leaving
294 Lynx</a></h2>
295
296 <p>To exit Lynx use the &ldquo;<samp>q</samp>&rdquo; command. You
297 will be asked whether you really want to quit. Answering
298 &ldquo;<samp>y</samp>&rdquo; will exit and
299 &ldquo;<samp>n</samp>&rdquo; will return you to the current
300 document. Use &ldquo;<samp>Q</samp>&rdquo; or <em>Control-D</em>
301 to quit without verification.</p>
302
303 <p>[<a href="#ToC-Leaving">ToC</a>]</p>
304
305 <h2 id="id-Remote"><a name="Remote" id="Remote">Starting Lynx
306 with a Remote File</a></h2>
307
308 <p>If you wish to view a remote file (that is, a file residing on
309 some computer system other than the one upon which you are
310 running Lynx) without first viewing a local file, you must
311 identify that file by using a Uniform Resource Locator (URL).
312 URLs take the general form:</p>
313
314 <blockquote>
315 <p><code>PROTOCOL :// HOST / PATH</code>
316 </p>
317 </blockquote>
318
319 <p>where</p>
320
321 <dl>
322 <dt><code>PROTOCOL</code>
323 </dt>
324
325 <dd>
326 <p>identifies the communications protocol (<em>scheme</em>)
327 used by the server that will provide the file. As mentioned
328 earlier, Lynx (and any WWW client) can interact with a
329 variety of servers, each with its own protocol.</p>
330 </dd>
331
332 <dt><code>HOST</code>
333 </dt>
334
335 <dd>
336 <p>is the Internet address of the computer system on which
337 the server is running, and</p>
338 </dd>
339
340 <dt><code>PATH</code>
341 </dt>
342
343 <dd>
344 <p>is a scheme-specific field which for some schemes may
345 correspond to a directory path and/or filename.</p>
346 </dd>
347 </dl>
348
349 <p>Here are some sample URLs.</p>
350
351 <dl>
352 <dt>HTTP (HyperText Transfer Protocol)</dt>
353
354 <dd><code>https://invisible-island.net/lynx/</code>
355 </dd>
356
357 <dt>Gopher</dt>
358
359 <dd><code>gopher://gopher.micro.umn.edu/11/</code>
360 </dd>
361
362 <dt>FTP (File Transfer Protocol)</dt>
363
364 <dd><code>ftp://ftp2.cc.ukans.edu/pub/lynx/README</code>
365 </dd>
366
367 <dt>WAIS (Wide Area Information Service protocol)</dt>
368
369 <dd><code>wais://cnidr.org/directory-of-servers</code>
370 </dd>
371
372 <dt>A URL may be specified to Lynx on the command line, as
373 in:</dt>
374
375 <dd><code>lynx
376 http://kufacts.cc.ukans.edu/cwis/kufacts_start.html</code>
377 </dd>
378 </dl>
379
380 <p>Lynx also will attempt to create a complete URL if you include
381 adequate portions of it in the startfile argument. For
382 example:</p>
383
384 <pre>
385 <em>wfbr</em> will be expanded to:
386 <em>http://www.wfbr.edu/</em> and:
387 <em>ftp.more.net/pub</em> will be expanded to:
388 <em>ftp://ftp.more.net/pub</em>
389 </pre>
390 <p>See <a href="lynx_url_support.html">URL Schemes Supported by
391 Lynx</a> for more detailed information.</p>
392
393 <p>[<a href="#ToC-Remote">ToC</a>]</p>
394
395 <h2 id="id-EnVar"><a name="EnVar" id="EnVar">Starting Lynx with
396 the WWW_HOME environment variable.</a></h2>
397
398 <p>You may also specify a starting file for Lynx using the
399 WWW_HOME environment variable,</p>
400
401 <dl>
402 <dt>UNIX</dt>
403
404 <dd>
405 <dl>
406 <dt>ksh</dt>
407
408 <dd><code>export WWW_HOME=http://www.w3.org/</code>
409 </dd>
410
411 <dt>csh</dt>
412
413 <dd><code>setenv WWW_HOME http://www.w3.org/</code>
414 </dd>
415 </dl>
416 </dd>
417
418 <dt>VMS</dt>
419
420 <dd><code>define "WWW_HOME" "http://www.w3.org/"</code>
421 </dd>
422
423 <dt>win32</dt>
424
425 <dd><code>WWW_HOME=http://www.w3.org/ [or in registry]</code>
426 </dd>
427 </dl>
428
429 <p>Note that on VMS the double-quoting <em>must</em> be included
430 to preserve casing.</p>
431
432 <p>[<a href="#ToC-EnVar">ToC</a>]</p>
433
434 <h2 id="id-IntraDocNav"><a name="IntraDocNav" id=
435 "IntraDocNav">Navigating hypertext documents with Lynx</a></h2>
436
437 <p>The process of moving within a hypertext web, selecting and
438 displaying links is known as "navigation." With Lynx almost all
439 navigation can be accomplished with the arrow keys and the
440 numeric keypad.</p>
441
442 <pre>
443 +-------+-------+-------+
444 | TOP | /|\ | Page |
445 arrow keys | of | | | UP |
446 | text 7| | 8| 9|
447 +---------+ +-------+-------+-------+
448 | SELECT | | | | |
449 | prev /|\| | &lt;--- | | ---&gt; |
450 | link | | | 4| 5| 6|
451 +---------+---------+---------+ +-------+-------+-------+
452 | BACK | SELECT | DISPLAY | | END | | | Page |
453 |&lt;-- prev | next | | sel. --&gt;| | of | | | DOWN |
454 | doc. | link \|/| link | | text 1| \|/ 2| 3|
455 +---------+---------+---------+ +-------+-------+-------+
456 </pre>
457 <p>There are also a few other keyboard commands to aid in
458 navigation. The Control and Function keys used for navigation
459 within the current document are described in <a href=
460 "#MiscKeys"><em>Scrolling and Other useful commands</em></a>.</p>
461
462 <p>Some additional commands depend on the fact that Lynx keeps a
463 list of each link you visited to reach the current document,
464 called the <a href="keystrokes/history_help.html">History
465 Page</a>, and a list of all links visited during the current Lynx
466 session, called the <a href=
467 "keystrokes/visited_help.html">Visited Links Page</a>.</p>
468
469 <ul>
470 <li>
471 <p>The HISTORY keystroke command, normally mapped to
472 <em>Backspace</em> or <em>Delete</em>, will show you the
473 <em>History Page</em> of links leading to your access of the
474 current document. Any of the previous documents shown in the
475 list may be revisited by selecting them from the history
476 screen.</p>
477 </li>
478
479 <li>
480 <p>The VLINKS keystroke command, normally mapped to uppercase
481 &ldquo;<samp>V</samp>&rdquo;, will show the <em>Visited Links
482 Page</em>, and you similarly can select links in that
483 list.</p>
484 </li>
485
486 <li>
487 <p>The MAIN_MENU keystroke command, normally mapped to
488 &ldquo;<samp>m</samp>&rdquo; and
489 &ldquo;<samp>M</samp>&rdquo;, will take you back to the
490 starting document unless you specified the
491 <em>-homepage=URL</em> option at the command line.</p>
492 </li>
493
494 <li>
495 <p>Also, the LIST and ADDRLIST keystroke commands, normally
496 mapped to &ldquo;<samp>l</samp>&rdquo; and
497 &ldquo;<samp>A</samp>&rdquo; respectively, will create a
498 compact lists of all the links in the current document, and
499 they can be selected via those lists.</p>
500 </li>
501 </ul>
502
503 <p>The &ldquo;<samp>i</samp>&rdquo; key presents an index of
504 documents. The default index offered contains many useful links,
505 but can be changed in <em>lynx.cfg</em> or on the command line
506 using the <em>-index=URL</em> switch.</p>
507
508 <p>If you choose a link to a server with active access
509 authorization, Lynx will automatically prompt for a username and
510 a password. If you give the correct information, you will then be
511 served the requested information. Lynx will automatically send
512 your username and password to the same server if it is needed
513 again.</p>
514
515 <p>[<a href="#ToC-IntraDocNav">ToC</a>]</p>
516
517 <h2 id="id-Disposing"><a name="Disposing" id=
518 "Disposing">Printing, Mailing, and Saving rendered files to
519 disk.</a></h2>
520
521 <p>Rendered HTML documents, and plain text files, may be printed
522 using the &ldquo;<samp>p</samp>&rdquo; command while viewing the
523 document. After pressing the &ldquo;<samp>p</samp>&rdquo; key a
524 menu of <em>Print Options</em> will be displayed. The menu will
525 vary according to several factors. First, some sites set up
526 special accounts to let users run Lynx to access local
527 information systems. Typically these accounts require no
528 passwords and do not require users to identify themselves. As a
529 result such accounts are called "anonymous" accounts, and their
530 users are considered "anonymous" users. In most configurations,
531 all Lynx users (including anonymous users) are able to mail files
532 to themselves and print the entire file to the screen.</p>
533
534 <p>Additional print options are available for users who are using
535 Lynx from their own accounts (that is, so-called "non-anonymous
536 users"). In particular, the <em>Save to a local file</em> option
537 allows you to save the document into a file on your disk space.
538 Additional print options may also be available as configured in
539 the <a href="#lynx.cfg">lynx.cfg</a> file.</p>
540
541 <p>Some options, such as <em>Save to a local file</em>, involve
542 prompting for an output filename. All output filename entries are
543 saved in a circular buffer, and any previous entries can be
544 retrieved for re-use by pressing the <em>up-arrow</em> or
545 <em>down-arrow</em> keys at the prompt.</p>
546
547 <p>Note that if you want exact copies of text files without any
548 expansions of TAB characters to spaces you should use the
549 <a href="#RemoteSource">Download</a> options.</p>
550
551 <p>[<a href="#ToC-Disposing">ToC</a>]</p>
552
553 <h2 id="id-LocalSource"><a name="LocalSource" id=
554 "LocalSource">Viewing the HTML document source and editing
555 documents</a></h2>
556
557 <p>When viewing HTML documents it is possible to retrieve and
558 display the unrendered (i.e., the original HTML) source of the
559 document by pressing the &ldquo;<samp>\</samp>&rdquo; (backslash)
560 key. Lynx usually caches only the rendering of the document and
561 does not keep the source (unless it is configured to do so in the
562 <a href="#lynx.cfg">lynx.cfg</a> file), so to display the source
563 unrendered, Lynx must reload it from the server or disk. When
564 viewing unrendered documents you may print them as any normal
565 document.</p>
566
567 <p>Selecting the <em>Print to a local file</em> option from the
568 Print Menu makes it possible to save the source of the document
569 to disk so that you may have a local copy of the document source,
570 but it is better to <a href="#RemoteSource">Download</a> the
571 source.</p>
572
573 <p>NOTE: When saving an HTML document it is important to name the
574 document with a <em>.html</em> or <em>.htm</em> extension, if you
575 want to read it with Lynx again later.</p>
576
577 <p id="FileEdit">Lynx can allow users to edit documents that
578 reside on the local system. To enable editing, documents must be
579 referenced using a "file:" URL or by specifying a plain filename
580 on the command line as in the following two examples:</p>
581
582 <dl>
583 <dt>Command</dt>
584
585 <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code>
586 </dd>
587
588 <dd><code>lynx path/filename.html</code>
589 </dd>
590 </dl>
591
592 <p>In addition, the user must also specify an editor in the
593 <em>Options Menu</em> so that Lynx knows which editor to use. If
594 the file is specified correctly and an editor is defined, then
595 you may edit documents by using the &ldquo;<samp>e</samp>&rdquo;
596 command. When the &ldquo;<samp>e</samp>&rdquo; command is entered
597 your specified editor is spawned to edit the file. After changes
598 are completed, exit your editor and you will return to Lynx. Lynx
599 will reload and render the file so that changes can be
600 immediately examined.</p>
601
602 <p>[<a href="#ToC-LocalSource">ToC</a>]</p>
603
604 <h2 id="id-RemoteSource"><a name="RemoteSource" id=
605 "RemoteSource">Downloading and Saving source files.</a></h2>
606
607 <p>If the DOWNLOAD keystroke command
608 (&ldquo;<samp>d</samp>&rdquo; or &ldquo;<samp>D</samp>&rdquo;) is
609 used when positioned on a link for an HTML, plain text, or binary
610 file, Lynx will transfer the file, without rendering, into a
611 temporary location and present the user with a list of options,
612 just as it does when a link for a binary file of a type for which
613 no viewer has been mapped is activated.</p>
614
615 <p>There is a default <em>Download option</em> of <em>Save to
616 disk</em>. This is disabled if Lynx is running in anonymous mode.
617 Any number of download methods such as kermit and zmodem may be
618 defined in addition to this default in the <em>lynx.cfg</em>
619 file. Using the <em>Save to disk</em> option under the PRINT
620 command after viewing the source of an HTML with the VIEW SOURCE
621 (<samp>\</samp>) command will result in a file which differs from
622 the original source in various ways such as tab characters
623 expanded to spaces. Lynx formats the source presentation in this
624 mode. On the other hand, if the DOWNLOAD command is used, the
625 only change will be that Lynx optionally puts</p>
626
627 <blockquote>
628 <p>&lt;!--X-URL: http://www.site.foo/path/to/file.html
629 --&gt;<br>
630 &lt;BASE href="http://www.site.foo/path/to/file.html"&gt;</p>
631 </blockquote>
632
633 <p>at the start of the file so that relative URLs in the document
634 will still work. Even this modification can be prevented by
635 setting PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg.</p>
636
637 <p>Some options, such as <em>Save to disk</em>, involve prompting
638 for an output filename. All output filename entries are saved in
639 a circular buffer, and any previous entries can be retrieved for
640 re-use by pressing the <em>up-arrow</em> or <em>down-arrow</em>
641 keys at the prompt.</p>
642
643 <p>[<a href="#ToC-RemoteSource">ToC</a>]</p>
644
645 <h2 id="id-ReDo"><a name="ReDo" id="ReDo">Reloading files and
646 refreshing the display</a></h2>
647
648 <p>The RELOAD (<em>Control-R</em>) command will reload and
649 re-render the file that you are currently viewing. The REFRESH
650 (<em>Control-L</em> or <em>Control-W</em>) command will refresh
651 or wipe the screen to remove or correct any errors that may be
652 caused by operating system or other messages.</p>
653
654 <p>The NOCACHE (&ldquo;<samp>x</samp>&rdquo; or
655 &ldquo;<samp>X</samp>&rdquo;) command can be used in lieu of
656 ACTIVATE (<em>Return</em> or <em>right-arrow</em>) to request an
657 uncached copy and new rendition for the current link, or
658 resubmission of a FORM, if a cache from a previous request or
659 submission exits. The request or submission will include
660 <em>Pragma: no-cache</em> and <em>Cache-Control: no-cache</em> in
661 its headers. Note that FORMs with POST content will be
662 resubmitted regardless of whether the NOCACHE or ACTIVATE command
663 is used (see <a href="#Forms"><em>Lynx and HTML
664 Forms</em></a>).</p>
665
666 <p>[<a href="#ToC-ReDo">ToC</a>]</p>
667
668 <h2 id="id-Search"><a name="Search" id="Search">Lynx searching
669 commands</a></h2>
670
671 <p>Two commands activate searching in Lynx:
672 &ldquo;<samp>/</samp>&rdquo; and
673 &ldquo;<samp>s</samp>&rdquo;.</p>
674
675 <p>While viewing a normal document use the
676 &ldquo;<samp>/</samp>&rdquo; command to find a word or phrase
677 within the current document. The search type will depend on the
678 search option setting in the <a href=
679 "#InteractiveOptions">Options Menu</a>. The search options are
680 case sensitive and case insensitive. These searches are entirely
681 local to Lynx.</p>
682
683 <p>Some documents are designated <em>index documents</em> by
684 virtue of an ISINDEX element in their HEAD section. These
685 documents can be used to retrieve additional information based on
686 searches using words or phrases submitted to an index server. The
687 Lynx statusline will indicate that you are viewing such a
688 document, and if so, the &ldquo;<samp>s</samp>&rdquo; key will
689 invoke a statusline prompt to enter a query string. The prompt
690 can be specified via a PROMPT attribute in the ISINDEX element.
691 Otherwise, Lynx will use an internally configured prompt. The
692 address for submitting the search can be specified via an HREF or
693 ACTION attribute. Otherwise, Lynx will use the current document's
694 URL and append your query string as a <em>?searchpart</em> (see
695 <a href="lynx_url_support.html">Supported URLs</a>).</p>
696
697 <p>All search words or strings which you have entered during a
698 Lynx session are saved in a circular buffer, and can be retrieved
699 for re-use by pressing the <em>up-arrow</em> or
700 <em>down-arrow</em> keys at the prompt for a search word or
701 string. Also, you can use the &ldquo;<samp>n</samp>&rdquo;ext
702 command to repeat a search with the last-entered search word or
703 phrase, starting from the current position in the document. The
704 word or phrase matches will be highlighted throughout the
705 document, but such highlighting will not persist for new
706 documents, or if the current document is reloaded. The search
707 cycles to the top of the document if the word or phrase is not
708 located below your current position.</p>
709
710 <p>Although <a href="#Forms">HTML Forms</a> have largely replaced
711 index documents for searches via http servers, they are still
712 useful for performing searches directly via WAIS or Gopher
713 servers in conjunction with the internal gateways for such
714 servers. For example, an HTML index document can act as a
715 <em>cover page</em> describing a WAIS database and how to
716 formulate query strings for searching it, and include an element
717 such as:</p>
718
719 <pre>
720 <em>&lt;ISINDEX PROMPT="Enter WAIS query:"
721 HREF="wais://net.bio.net/biologists-addresses"&gt;</em>
722 </pre>
723 <p>for submitting a search of the Biologist's Addresses database
724 directly to the net.bio.net WAIS server.</p>
725
726 <p>[<a href="#ToC-Search">ToC</a>]</p>
727
728 <h2 id="id-InteractiveOptions"><a name="InteractiveOptions" id=
729 "InteractiveOptions">Lynx Options Menu</a></h2>
730
731 <p>The Lynx <em>Options Menu</em> may be accessed by pressing the
732 &ldquo;<samp>o</samp>&rdquo; key. It allows you to change options
733 at runtime, if you need to. Most changes are read from &amp;
734 saved to your .lynxrc file; those which are not are marked (!) in
735 the form-based menu (as below). Many other options are stored in
736 the <a href="#lynx.cfg">lynx.cfg</a> file.</p>
737
738 <p>Lynx supports two styles of Options Menu:</p>
739
740 <ul>
741 <li><a name="item-form_based_options" href=
742 "#explain-form_based_options" id=
743 "item-form_based_options">form-based</a></li>
744
745 <li><a name="item-key_based_options" href=
746 "#explain-key_based_options" id=
747 "item-key_based_options">key-based</a></li>
748 </ul>
749
750 <p id="explain-form_based_options">The form-based menu shown
751 below is an HTML file generated at runtime, in which the user
752 fills in choices as in any ordinary HTML form.</p>
753
754 <pre>
755
756 <a href="#item-form_based_options" name=
757 "example-form_based_options" id=
758 "example-form_based_options">Options Menu (Lynx Version 2.9.3)</a>
759
760 Accept Changes - Reset Changes - Left Arrow cancels changes - HELP!
761
762 Save options to disk: [ ]
763 (options marked with (!) will not be saved)
764
765 General Preferences
766 User mode : <a href=
767 "#optinfo-user_mode">[Advanced____]</a>
768 Editor : <a href=
769 "#optinfo-editor">vile______________________________________</a>
770 Type of Search : <a href=
771 "#optinfo-type_of_search">[Case insensitive]</a>
772
773 Security and Privacy
774 Cookies : <a href=
775 "#optinfo-cookies">[ask user__]</a>
776 Invalid-Cookie Prompting (!) : <a href=
777 "#optinfo-invalid_cookie_prompting">[prompt normally___]</a>
778 SSL Prompting (!) : <a href=
779 "#optinfo-ssl_prompting">[prompt normally___]</a>
780
781 Keyboard Input
782 Keypad mode : <a href=
783 "#optinfo-keypad_mode">[Numbers act as arrows_____________]</a>
784 Emacs keys : <a href=
785 "#optinfo-emacs_keys">[OFF]</a>
786 VI keys : <a href=
787 "#optinfo-vi_keys">[OFF]</a>
788 Line edit style : <a href=
789 "#optinfo-line_edit_style">[Bash-like Bindings]</a>
790
791 Display and Character Set
792 Use locale-based character set : <a href=
793 "#optinfo-locale_based_charset">[ON_]</a>
794 Use HTML5 charset replacements(!): <a href=
795 "#optinfo-use_html5_charset">[OFF]</a>
796 Display character set : <a href=
797 "#optinfo-display_charset">[UNICODE (UTF-8)________________]</a>
798 Assumed document character set(!): <a href=
799 "#optinfo-assumed_document_charset">[iso-8859-1______]</a>
800 Internationalized domain names(!): <a href=
801 "#optinfo-idna_mode">[IDNA TR46______]</a>
802 Raw 8-bit : <a href=
803 "#optinfo-raw_8_bit">[OFF]</a>
804 X Display : <a href=
805 "#optinfo-x_display">localhost:0.0_____________________________</a>
806
807 Document Appearance
808 Show color : <a href=
809 "#optinfo-show_color">[ON____]</a>
810 Color style (!) : [lynx.lss___________]
811 Default colors (!) : [ON_]
812 Show cursor : <a href=
813 "#optinfo-show_cursor">[OFF]</a>
814 Underline links (!) : <a href=
815 "#optinfo-underline_links">[OFF]</a>
816 Show scrollbar : <a href=
817 "#optinfo-show_scrollbar">[ON_]</a>
818 Popups for select fields : <a href=
819 "#optinfo-popups_for_select">[ON_]</a>
820 HTML error recovery : <a href=
821 "#optinfo-html_error_recovery">[strict (SortaSGML mode)]</a>
822 Bad HTML messages (!) : <a href=
823 "#optinfo-bad_html_messages">[Warn, point to trace-file]</a>
824 Show images : <a href=
825 "#optinfo-show_images">[ignore___]</a>
826 Verbose images : <a href=
827 "#optinfo-verbose_images">[OFF__________]</a>
828 Collapse BR tags (!) : <a href=
829 "#optinfo-collapse_br_tags">[OFF_____]</a>
830 Trim blank lines (!) : <a href=
831 "#optinfo-trim_blank_lines">[trim-lines]</a>
832
833 Headers Transferred to Remote Servers
834 Personal mail address : <a href=
835 "#optinfo-personal_mail_address">__________________________________________</a>
836 Personal name for mail : <a href=
837 "#optinfo-personal_name_for_mail">__________________________________________</a>
838 Password for anonymous ftp : <a href=
839 "#optinfo-password_for_anon_ftp">__________________________________________</a>
840 Preferred media type (!) : <a href=
841 "#optinfo-preferred_media_type">[Accept lynx's internal types]</a>
842 Preferred encoding (!) : <a href=
843 "#optinfo-preferred_encoding">[All_____]</a>
844 Preferred document character set : <a href=
845 "#optinfo-preferred_doc_charset">_________________________________</a>
846 Preferred document language : <a href=
847 "#optinfo-preferred_doc_language">en_______________________________</a>
848 HTTP protocol (!) : <a href=
849 "#optinfo-http_protocol">[HTTP 1.0]</a>
850 Send User-Agent header (!) : <a href=
851 "#optinfo-send_user_agent">[X]</a>
852 User-Agent header (!) : <a href=
853 "#optinfo-user_agent">Lynx/2.9.3 libwww-FM/2.14 SSL-MM/1.4.</a>
854
855 Listing and Accessing Files
856 Use Passive FTP (!) : <a href=
857 "#optinfo-use_passive_ftp">[ON_]</a>
858 FTP sort criteria : <a href=
859 "#optinfo-ftp_sort_criteria">[By Date]</a>
860 Local directory sort criteria : <a href=
861 "#optinfo-local_directory_sort_criteria">[Directories first]</a>
862 Local directory sort order : <a href=
863 "#optinfo-local_directory_sort_order">[By Date_]</a>
864 Show dot files : <a href=
865 "#optinfo-show_dot_files">[OFF]</a>
866 Pause when showing message (!) : <a href=
867 "#optinfo-pause_when_showing_message">[ON_]</a>
868 Show transfer rate : <a href=
869 "#optinfo-show_transfer_rate">[Show KiB/sec (2-digits), ETA__]</a>
870
871 Special Files and Screens
872 Multi-bookmarks : <a href=
873 "#optinfo-multi_bookmarks">[ADVANCED]</a>
874 Review/edit Bookmarks files : Goto multi-bookmark menu
875 Auto Session (!) : <a href=
876 "#optinfo-auto_session">[OFF]</a>
877 Session file (!) : <a href=
878 "#optinfo-session_file">__________________________________________</a>
879 Visited Pages : <a href=
880 "#optinfo-visited_pages">[By Last Visit Reversed_]</a>
881
882 View the file lynx.cfg.
883
884 Accept Changes - Reset Changes - Left Arrow cancels changes
885 </pre>
886 <p id="explain-key_based_options">The key-based menu depends on
887 key-strokes to identify options which the user wants to change.
888 It is compiled into Lynx and is accessed by setting FORMS_OPTIONS
889 to TRUE in <code>lynx.cfg</code>.</p>
890
891 <pre>
892
893 <a href="#item-key_based_options" name=
894 "example-key_based_options" id=
895 "example-key_based_options">Options Menu (Lynx Version 2.9.3)</a>
896
897 <a href=
898 "#optinfo-editor">(E)</a>ditor : emacs
899 <a href=
900 "#optinfo-x_display">(D)</a>ISPLAY variable : aixtest.cc.ukans.edu:0.0
901 mu<a href=
902 "#optinfo-multi_bookmarks">(L)</a>ti-bookmarks: OFF <a href=
903 "#optinfo-bookmark_file">B)</a>ookmark file: lynx_bookmarks.html
904 <a href=
905 "#optinfo-ftp_sort_criteria">(F)</a>TP sort criteria : By Filename
906 <a href=
907 "#optinfo-personal_mail_address">(P)</a>ersonal mail address : [email protected]
908 <a href=
909 "#optinfo-type_of_search">(S)</a>earching type : CASE INSENSITIVE
910 preferred document lan<a href=
911 "#optinfo-preferred_doc_language">(G)</a>uage: en
912 preferred document c<a href=
913 "#optinfo-preferred_doc_charset">(H)</a>arset : NONE
914 display <a href=
915 "#optinfo-display_charset">(C)</a>haracter set : Western (ISO-8859-1)
916 raw 8-bit or CJK m<a href=
917 "#optinfo-raw_8_bit">(O)</a>de : ON show color <a href=
918 "#optinfo-show_color">(&amp;)</a> : OFF
919 <a href="#optinfo-vi_keys">(V)</a>I keys: OFF e<a href=
920 "#optinfo-emacs_keys">(M)</a>acs keys: OFF sho<a href=
921 "#optinfo-show_dot_files">(W)</a> dot files: OFF
922 popups for selec<a href=
923 "#optinfo-popups_for_select">(T)</a> fields : ON show cursor <a href="#optinfo-show_cursor">(@)</a> : OFF
924 <a href=
925 "#optinfo-keypad_mode">(K)</a>eypad mode : Numbers act as arrows
926 li<a href=
927 "#optinfo-line_edit_style">(N)</a>e edit style : Default Binding
928 l<a href=
929 "#optinfo-local_directory_sort_criteria">(I)</a>st directory style : Mixed style
930 <a href=
931 "#optinfo-user_mode">(U)</a>ser mode : Advanced verbose images <a href="#optinfo-verbose_images">(!)</a> : ON
932 user <a href=
933 "#optinfo-user_agent">(A)</a>gent : [User-Agent header]
934 local e<a href=
935 "#optinfo-execution_links">(X)</a>ecution links : FOR LOCAL FILES ONLY
936 </pre>
937 <p>An option can be changed by entering the capital letter or
938 character in parentheses for the option you wish to change (e.g.,
939 &ldquo;<samp>E</samp>&rdquo; for Editor or
940 &ldquo;<samp>@</samp>&rdquo; for show cursor). For fields where
941 text must be entered, simply enter the text by typing on the
942 keyboard. The <a href="keystrokes/edit_help.html">Line Editor</a>
943 can be used to correct mistakes, and <em>Control-U</em> can be
944 used to erase the line. When you are done entering a change press
945 the <em>Return</em> key to get back to the <em>Command?</em>
946 prompt.</p>
947
948 <p>For fields where you must choose one of two choices, press any
949 key to toggle the choices and press the <em>Return</em> key to
950 finish the change.</p>
951
952 <p>For fields where you potentially have more than two choices,
953 popup windows may be evoked which function homologously to those
954 for select fields in <a href="#Forms">HTML Forms</a>. The popup
955 windows will be invoked only if you have popups for select fields
956 set to ON (see below). Otherwise, your cursor will be positioned
957 at the current choice, and you can press any key to cycle through
958 the choices, then press the <em>Return</em> key to finish the
959 change.</p>
960
961 <p>When you are done changing options use the
962 &ldquo;<samp>r</samp>&rdquo; command to return to Lynx or the
963 &ldquo;<samp>&gt;</samp>&rdquo; command to save the options to a
964 <em>.lynxrc</em> file and return to Lynx.</p>
965
966 <p>The following table describes the options available on the
967 <em>Options Menu</em>:</p>
968
969 <dl>
970 <dt><a name="optinfo-assumed_document_charset" id=
971 "optinfo-assumed_document_charset">Assumed document character
972 set</a>
973 </dt>
974
975 <dd>
976 <p>This option changes the handling of documents which do not
977 explicitly specify a charset. Normally Lynx assumes that
978 8-bit characters in those documents are encoded according to
979 iso-8859-1 (the official default for the HTTP protocol).
980 Unfortunately, many non-English web pages "forget" to include
981 proper charset info; this option helps you to browse those
982 broken pages if you know by some means what the charset
983 is.</p>
984
985 <p>When the value given here or by an -assume_charset command
986 line flag is in effect, Lynx will treat documents as if they
987 were encoded accordingly. This option is active when
988 &ldquo;Raw 8-bit or CJK Mode&rdquo; is OFF.</p>
989 </dd>
990
991 <dt><a name="optinfo-auto_session" id=
992 "optinfo-auto_session">Auto Session</a>
993 </dt>
994
995 <dd>
996 <p>Lynx can save and restore useful information about your
997 browsing history. Use this setting to enable or disable the
998 feature.</p>
999 </dd>
1000
1001 <dt><a name="optinfo-bad_html_messages" id=
1002 "optinfo-bad_html_messages">Bad HTML messages</a>
1003 </dt>
1004
1005 <dd>
1006 <p>Suppress or redirect Lynx's messages about "Bad HTML":</p>
1007
1008 <dl>
1009 <dt>Ignore</dt>
1010
1011 <dd>
1012 <p>do not warn; no details are written to the
1013 trace-file.</p>
1014 </dd>
1015
1016 <dt>Add to trace-file</dt>
1017
1018 <dd>
1019 <p>add the detailed warning message to the
1020 trace-file.</p>
1021 </dd>
1022
1023 <dt>Add to LYNXMESSAGES</dt>
1024
1025 <dd>
1026 <p>add the detailed warning message to the message page
1027 at "LYNXMESSAGES:".</p>
1028 </dd>
1029
1030 <dt>Warn, point to trace-file</dt>
1031
1032 <dd>
1033 <p>show a warning message on the status line; the
1034 complete message is written to the trace-file.</p>
1035 </dd>
1036 </dl>
1037 </dd>
1038
1039 <dt><a name="optinfo-bookmark_file" id=
1040 "optinfo-bookmark_file">Bookmark file</a>
1041 </dt>
1042
1043 <dd>
1044 <p>When multi-bookmarks is OFF, this is the filename and
1045 location of your default personal bookmark file. Enter
1046 &ldquo;<samp>B</samp>&rdquo; to modify the filename and/or
1047 location via the <a href="keystrokes/edit_help.html">Line
1048 Editor</a>. Bookmark files allow frequently traveled links to
1049 be stored in personal easy to access files.</p>
1050
1051 <p>Using the &ldquo;<samp>a</samp>&rdquo;dd bookmark link
1052 command (see <a href="#Bookmarks">Lynx bookmarks</a>) you may
1053 save any link that does not have associated POST content into
1054 a bookmark file. All bookmark files must be in or under your
1055 account's home directory. If the location specified does not
1056 begin with a dot-slash (./), its presence will still be
1057 assumed, and referenced to the home directory.</p>
1058
1059 <p>When multi-bookmarks is STANDARD or ADVANCED, entering
1060 &ldquo;<samp>B</samp>&rdquo; will invoke a menu of up to 26
1061 bookmark files (associated with the letters of the English
1062 alphabet), for editing their filenames and locations
1063 (<em>filepath</em>), and descriptions.</p>
1064
1065 <p>Lynx will create bookmark files, if they do not already
1066 exist, when you first &ldquo;<samp>a</samp>&rdquo;dd a
1067 bookmark link to them. However, if you've specified a
1068 subdirectory (e.g., ./BM/lynx_bookmarks.html), that
1069 subdirectory must already exist. Note that on VMS you should
1070 use the URL syntax for the filepath (e.g., <em>not</em>
1071 [.BM]lynx_bookmarks.html).</p>
1072 </dd>
1073
1074 <dt><a name="optinfo-collapse_br_tags" id=
1075 "optinfo-collapse_br_tags">Collapse BR tags</a>
1076 </dt>
1077
1078 <dd>
1079 <p>If <em>Collapse BR tags</em> is turned off, Lynx will not
1080 collapse serial <code>BR</code> tags. If turned on, i.e.,
1081 &ldquo;collapse&rdquo;, two or more concurrent
1082 <code>BR</code>s will be collapsed into a single line break.
1083 Note that the valid way to insert extra blank lines in HTML
1084 is via a <code>PRE</code> block with only newlines in the
1085 block.</p>
1086 </dd>
1087
1088 <dt><a name="optinfo-cookies" id="optinfo-cookies">Cookies</a>
1089 </dt>
1090
1091 <dd>
1092 <p>This option allows you to tell how to handle cookies:
1093 <em>ignore</em>, prompt (<em>ask user</em>) or <em>accept
1094 all</em>.</p>
1095 </dd>
1096
1097 <dt><a name="optinfo-display_charset" id=
1098 "optinfo-display_charset">Display Character set</a>
1099 </dt>
1100
1101 <dd>
1102 <p>This option allows you to set up the default character set
1103 for your specific terminal. The display character set
1104 provides a mapping from the character encodings of viewed
1105 documents and from HTML entities into viewable characters. It
1106 should be set according to your terminal's character set so
1107 that characters other than 7-bit ASCII can be displayed
1108 correctly, using approximations if necessary. You must have
1109 the selected character set installed on your terminal. (Since
1110 Lynx supports a wide range of platforms it may be useful to
1111 note that cpXXX codepages used within IBM PC computers, and
1112 windows-xxxx within native MS-Windows apps.)</p>
1113 </dd>
1114
1115 <dt><a name="optinfo-editor" id="optinfo-editor">Editor</a>
1116 </dt>
1117
1118 <dd>
1119 <p>The editor to be invoked when editing browsable files,
1120 when sending mail or comments, when preparing a news article
1121 for posting, and for external TEXTAREA editing. The full
1122 pathname of the editor command should be specified when
1123 possible.</p>
1124
1125 <p>If a full pathname is given, this helps Lynx provide for
1126 detecting if options were also provided in this field. In
1127 this case, it will also quote the pathname, allowing for
1128 embedded blanks and other special characters that might
1129 confuse the shell which starts the editor program.</p>
1130 </dd>
1131
1132 <dt><a name="optinfo-emacs_keys" id="optinfo-emacs_keys">Emacs
1133 keys</a>
1134 </dt>
1135
1136 <dd>
1137 <p>If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B
1138 keys will be mapped to up-arrow, down-arrow, right-arrow, and
1139 left-arrow, respectively. Otherwise, they remain mapped to
1140 their configured bindings (normally UP_TWO lines, DOWN_TWO
1141 lines, NEXT_PAGE, and PREV_PAGE, respectively).</p>
1142
1143 <p>Note: this has no direct effect on the line-editor's key
1144 bindings.</p>
1145 </dd>
1146
1147 <dt><a name="optinfo-execution_links" id=
1148 "optinfo-execution_links">Execution links</a>
1149 </dt>
1150
1151 <dd>
1152 <p>This deals with execution of local scripts or links. Local
1153 execution is activated when Lynx is first set up. If it has
1154 not been activated you will not see this option in the
1155 <em>Options Menu</em>.</p>
1156
1157 <p>When a local execution script is encountered Lynx checks
1158 the users options to see whether the script can be executed.
1159 Users have the following options:</p>
1160
1161 <dl>
1162 <dt>Always off</dt>
1163
1164 <dd>
1165 <p>Local execution scripts will never be executed</p>
1166 </dd>
1167
1168 <dt>For Local files only</dt>
1169
1170 <dd>
1171 <p>Local execution scripts will only be executed if the
1172 script to be executed resides on the local machine, and
1173 is referenced by a URL that begins with
1174 <em>file://localhost</em></p>
1175 </dd>
1176
1177 <dt>Always on</dt>
1178
1179 <dd>
1180 <p>All local execution scripts will be executed</p>
1181 </dd>
1182 </dl>
1183 </dd>
1184
1185 <dd>
1186 <p>If the users options permit the script to be executed Lynx
1187 will spawn a shell and run the script. If the script cannot
1188 be executed Lynx will show the script within the Lynx window
1189 and inform the user that the script is not allowed to be
1190 executed and will ask the user to check his/her options.</p>
1191 </dd>
1192
1193 <dt><a name="optinfo-ftp_sort_criteria" id=
1194 "optinfo-ftp_sort_criteria">FTP sort criteria</a>
1195 </dt>
1196
1197 <dd>
1198 <p>This option allows you to specify how files will be sorted
1199 within FTP listings. The current options include "<code>By
1200 Filename</code>", "<code>By Size</code>", "<code>By
1201 Type</code>", and "<code>By Date</code>".</p>
1202 </dd>
1203
1204 <dt><a name="optinfo-html_error_recovery" id=
1205 "optinfo-html_error_recovery">HTML error recovery</a>
1206 </dt>
1207
1208 <dd>
1209 <p>Select the <a href=
1210 "keystrokes/option_help.html#tagsoup">recovery mode</a> used
1211 by Lynx.</p>
1212 </dd>
1213
1214 <dt><a name="optinfo-http_protocol" id=
1215 "optinfo-http_protocol">HTTP protocol</a>
1216 </dt>
1217
1218 <dd>
1219 <p>Normally Lynx negotiates HTTP/1.0, because it does not
1220 support chunked transfer (a requirement for all HTTP/1.1
1221 clients), although it supports several other features of
1222 HTTP/1.1. You may encounter a server which does not support
1223 HTTP/1.0 which can be used by switching to the later
1224 protocol.</p>
1225 </dd>
1226
1227 <dt><a name="optinfo-idna_mode" id=
1228 "optinfo-idna_mode">Internationalized domain names</a>
1229 </dt>
1230
1231 <dd>
1232 Convert internationalized domain names to and from ASCII.
1233 <dl>
1234 <dt>IDNA 2003</dt>
1235
1236 <dd>Convert using the older &ldquo;transitional&rdquo;
1237 scheme.</dd>
1238
1239 <dt>IDNA 2008</dt>
1240
1241 <dd>Convert using the newer &ldquo;non-transitional&rdquo;
1242 scheme.</dd>
1243
1244 <dt>IDNA TR46</dt>
1245
1246 <dd>Use IDNA 2008 with the amendments from Unicode <a href=
1247 "http://www.unicode.org/reports/tr46">Technical Report
1248 46</a>.</dd>
1249
1250 <dt>IDNA Compatible</dt>
1251
1252 <dd>First try converting using IDNA 2008, and if
1253 unsuccessful, try IDNA 2003.</dd>
1254 </dl>
1255 </dd>
1256
1257 <dt><a name="optinfo-invalid_cookie_prompting" id=
1258 "optinfo-invalid_cookie_prompting">Invalid-Cookie Prompting</a>
1259 </dt>
1260
1261 <dd>
1262 <p>This allows you to tell how to handle invalid cookies:
1263 <em>prompt normally</em> to prompt for each cookie, <em>force
1264 yes-response</em> to reply "yes" to each prompt, <em>force
1265 no-response</em> to reply "no" to each prompt.</p>
1266 </dd>
1267
1268 <dt><a name="optinfo-keypad_mode" id=
1269 "optinfo-keypad_mode">Keypad mode</a>
1270 </dt>
1271
1272 <dd>
1273 <p>This option gives the choice among navigating with the
1274 arrow keys, or having every link numbered so that the links
1275 may be selected or made current by numbers as well as using
1276 the arrow keys, or having every link as well as every form
1277 field numbered so that they can be selected or sought by
1278 numbers. See the<br>
1279 &nbsp;&nbsp;<a href="keystrokes/follow_help.html">Follow link
1280 (or page) number:</a> and<br>
1281 &nbsp;&nbsp;<a href=
1282 "keystrokes/follow_help.html#select-option">Select option (or
1283 page) number:</a><br>
1284 help for more information.</p>
1285 </dd>
1286
1287 <dt><a name="optinfo-line_edit_style" id=
1288 "optinfo-line_edit_style">Line edit style</a>
1289 </dt>
1290
1291 <dd>
1292 <p>This option allows you to set alternative key bindings for
1293 the built-in line editor, if alternative line-edit bindings
1294 have been compiled in. Otherwise, Lynx uses the <a href=
1295 "keystrokes/edit_help.html">Default Binding</a>.</p>
1296 </dd>
1297
1298 <dt><a name="optinfo-local_directory_sort_criteria" id=
1299 "optinfo-local_directory_sort_criteria">Local directory sort
1300 criteria</a>
1301 </dt>
1302
1303 <dd>
1304 <p>This applies to directory editing. Files and directories
1305 can be presented in the following ways:</p>
1306
1307 <dl>
1308 <dt>Mixed style</dt>
1309
1310 <dd>
1311 <p>Files and directories are listed together in
1312 alphabetical order.</p>
1313 </dd>
1314
1315 <dt>Directories first</dt>
1316
1317 <dd>
1318 <p>Files and directories are separated into two
1319 alphabetical lists. Directories are listed first.</p>
1320 </dd>
1321
1322 <dt>Files first</dt>
1323
1324 <dd>
1325 <p>Files and directories are separated into two
1326 alphabetical lists. Files are listed first.</p>
1327 </dd>
1328 </dl>
1329 </dd>
1330
1331 <dt><a name="optinfo-local_directory_sort_order" id=
1332 "optinfo-local_directory_sort_order">Local directory sort
1333 order</a>
1334 </dt>
1335
1336 <dd>
1337 <p>The Options Form also allows you to sort by the file
1338 attributes.</p>
1339
1340 <dl>
1341 <dt>By name</dt>
1342
1343 <dd>
1344 <p>by filename (the default)</p>
1345 </dd>
1346
1347 <dt>By size</dt>
1348
1349 <dd>
1350 <p>by file size, in descending order</p>
1351 </dd>
1352
1353 <dt>By date</dt>
1354
1355 <dd>
1356 <p>by file modification time, in descending order</p>
1357 </dd>
1358
1359 <dt>By mode</dt>
1360
1361 <dd>
1362 <p>by file protection</p>
1363 </dd>
1364
1365 <dt>By type</dt>
1366
1367 <dd>
1368 <p>by filename suffix, e.g., the text beginning with
1369 &ldquo;.&rdquo;</p>
1370 </dd>
1371
1372 <dt>By user</dt>
1373
1374 <dd>
1375 <p>by file owner's user-id</p>
1376 </dd>
1377
1378 <dt>By group</dt>
1379
1380 <dd>
1381 <p>by file owner's group-id</p>
1382 </dd>
1383 </dl>
1384 </dd>
1385
1386 <dt><a name="optinfo-multi_bookmarks" id=
1387 "optinfo-multi_bookmarks">Multi-bookmarks</a>
1388 </dt>
1389
1390 <dd>
1391 <p>Lynx supports a default bookmark file, and up to 26 total
1392 bookmark files (see below). When multi-bookmarks is OFF, the
1393 default bookmark file is used for the
1394 &ldquo;<samp>v</samp>&rdquo;iew bookmarks and
1395 &ldquo;<samp>a</samp>&rdquo;dd bookmark link commands. If
1396 multi-bookmark support is available in your account, the
1397 setting can be changed to STANDARD or ADVANCED. In STANDARD
1398 mode, a menu of available bookmarks always is invoked when
1399 you seek to view a bookmark file or add a link, and you
1400 select the bookmark file by its letter token (see
1401 <em>Bookmark file</em>, below) in that menu. In ADVANCED
1402 mode, you instead are prompted for the letter of the desired
1403 bookmark file, but can enter &ldquo;<samp>=</samp>&rdquo; to
1404 invoke the STANDARD selection menu, or <em>RETURN</em> for
1405 the default bookmark file.</p>
1406 </dd>
1407
1408 <dt><a name="optinfo-password_for_anon_ftp" id=
1409 "optinfo-password_for_anon_ftp">Password for anonymous ftp</a>
1410 </dt>
1411
1412 <dd>
1413 <p>If this is blank, Lynx will use your personal mail address
1414 as the anonymous ftp password. Though that is the convention,
1415 some users prefer to use some other string which provides
1416 less information. If the given value lacks a "@", Lynx also
1417 will use your computer's hostname as part of the password. If
1418 both this field and the personal mail address are blank, Lynx
1419 will use your $USER environment variable, or "WWWuser" if
1420 even the environment variable is unset.</p>
1421 </dd>
1422
1423 <dt><a name="optinfo-pause_when_showing_message" id=
1424 "optinfo-pause_when_showing_message">Pause when showing
1425 message</a>
1426 </dt>
1427
1428 <dd>
1429 <p>If set to "off", this overrides the INFOSECS setting in
1430 lynx.cfg, to eliminate pauses when displaying informational
1431 messages, like the "-nopause" command line option.</p>
1432 </dd>
1433
1434 <dt><a name="optinfo-personal_mail_address" id=
1435 "optinfo-personal_mail_address">Personal mail address</a>
1436 </dt>
1437
1438 <dd>
1439 <p>This mail address will be used to help you send files to
1440 yourself and will be included as the From: address in any
1441 mail or comments that you send. It will also be sent as the
1442 From: field in HTTP or HTTPS requests if inclusion of that
1443 header has been enabled via the NO_FROM_HEADER definition in
1444 <a href="#lynx.cfg">lynx.cfg</a> (the compilation default is
1445 not to send the header), or via the <em>-from</em> command
1446 line toggle.</p>
1447 </dd>
1448
1449 <dt><a name="optinfo-personal_name_for_mail" id=
1450 "optinfo-personal_name_for_mail">Personal mail name</a>
1451 </dt>
1452
1453 <dd>
1454 <p>This mail name will be included as the "X-Personal_Name"
1455 field in any mail or comments that you send if that header
1456 has not been disabled via the NO_ANONYMOUS_EMAIL definition
1457 in <a href="#lynx.cfg">lynx.cfg</a>.</p>
1458 </dd>
1459
1460 <dt><a name="optinfo-popups_for_select" id=
1461 "optinfo-popups_for_select">Popups for select fields</a>
1462 </dt>
1463
1464 <dd>
1465 <p>Lynx normally uses a popup window for the OPTIONs in form
1466 SELECT fields when the field does not have the MULTIPLE
1467 attribute specified, and thus only one OPTION can be
1468 selected. The use of popup windows can be disabled by
1469 changing this setting to OFF, in which case the OPTIONs will
1470 be rendered as a list of radio buttons. Note that if the
1471 SELECT field does have the MULTIPLE attribute specified, the
1472 OPTIONs always are rendered as a list of checkboxes.</p>
1473 </dd>
1474
1475 <dt><a name="optinfo-preferred_doc_language" id=
1476 "optinfo-preferred_doc_language">Preferred document
1477 language</a>
1478 </dt>
1479
1480 <dd>
1481 <p>The language you prefer if multi-language files are
1482 available from servers. Use RFC 1766 abbreviations, e.g., en
1483 for English, fr for French, etc. Can be a comma-separated
1484 list, which may be interpreted by servers as descending order
1485 of preferences. You can also make your order of preference
1486 explicit by using q factors as defined by the HTTP protocol,
1487 for servers which understand it, for example:
1488 da,&nbsp;en-gb;q=0.8,&nbsp;en;q=0.7</p>
1489 </dd>
1490
1491 <dt><a name="optinfo-preferred_doc_charset" id=
1492 "optinfo-preferred_doc_charset">Preferred document charset</a>
1493 </dt>
1494
1495 <dd>
1496 <p>The character set you prefer if sets in addition to
1497 ISO-8859-1 and US-ASCII are available from servers. Use MIME
1498 notation (e.g., ISO-8859-2) and do not include ISO-8859-1 or
1499 US-ASCII, since those values are always assumed by default.
1500 Can be a comma-separated list, which may be interpreted by
1501 servers as descending order of preferences. You can also make
1502 your order of preference explicit by using q factors as
1503 defined by the HTTP protocol, for servers which understand
1504 it, for example: iso-8859-5,&nbsp;utf-8;q=0.8</p>
1505 </dd>
1506
1507 <dt><a name="optinfo-preferred_encoding" id=
1508 "optinfo-preferred_encoding">Preferred encoding</a>
1509 </dt>
1510
1511 <dd>
1512 <p>When doing a GET, lynx tells what types of compressed data
1513 it can decompress (the "Accept-Encoding:" string). This is
1514 determined by compiled-in support for decompression or
1515 external decompression programs. Use this option to select
1516 none, one or all of the supported decompression types.</p>
1517 </dd>
1518
1519 <dt><a name="optinfo-preferred_media_type" id=
1520 "optinfo-preferred_media_type">Preferred media type</a>
1521 </dt>
1522
1523 <dd>
1524 <p>When doing a GET, lynx lists the MIME types which it knows
1525 how to present (the "Accept:" string). Depending on your
1526 system configuration, the mime.types or other data given by
1527 the GLOBAL_EXTENSION_MAP may include many entries that lynx
1528 really does not handle. Use this option to select one of the
1529 built-in subsets of the MIME types that lynx could list in
1530 the Accept.</p>
1531
1532 <dl>
1533 <dt>Accept lynx's internal types</dt>
1534
1535 <dd>
1536 <p>list only the types that are compiled into lynx.</p>
1537 </dd>
1538
1539 <dt>Also accept lynx.cfg's types</dt>
1540
1541 <dd>
1542 <p>lists types defined in lynx.cfg, e.g., the VIEWER and
1543 Cern RULE or RULESFILE settings.</p>
1544 </dd>
1545
1546 <dt>Also accept user's types</dt>
1547
1548 <dd>
1549 <p>lists types from the PERSONAL_EXTENSION_MAP setting in
1550 lynx.cfg</p>
1551 </dd>
1552
1553 <dt>Also accept system's types</dt>
1554
1555 <dd>
1556 <p>lists types from the GLOBAL_EXTENSION_MAP setting in
1557 lynx.cfg</p>
1558 </dd>
1559
1560 <dt>Accept all types</dt>
1561
1562 <dd>
1563 <p>adds the types that are in lynx's built-in tables for
1564 external programs that may be used to present a
1565 document.</p>
1566 </dd>
1567 </dl>
1568 </dd>
1569
1570 <dt><a name="optinfo-raw_8_bit" id="optinfo-raw_8_bit">Raw
1571 8-bit or CJK Mode</a>
1572 </dt>
1573
1574 <dd>
1575 <p>Tells Lynx whether 8-bit characters are assumed to
1576 correspond with the display character set and therefore are
1577 processed without translation via the chartrans conversion
1578 tables:</p>
1579
1580 <ul>
1581 <li>Should be ON by default when the display character set
1582 is one of the Asian (CJK) sets and the 8-bit characters are
1583 Kanji multibytes.</li>
1584
1585 <li>Should be OFF for the other display character sets, but
1586 can be turned ON when the document's charset is unknown
1587 (e.g., is not ISO-8859-1 and no charset parameter was
1588 specified in a reply header from an HTTP server to indicate
1589 what it is) but you know by some means that you have the
1590 matching display character set selected.</li>
1591
1592 <li>Should be OFF when an Asian (CJK) set is selected but
1593 the document is ISO-8859-1 or another &ldquo;assumed
1594 document character set&rdquo;.</li>
1595 </ul>
1596
1597 <p>The setting also can be toggled via the RAW_TOGGLE
1598 command, normally mapped to &ldquo;<samp>@</samp>&rdquo;, and
1599 at startup via the <em>-raw</em> switch.</p>
1600 </dd>
1601
1602 <dt><a name="optinfo-send_user_agent" id=
1603 "optinfo-send_user_agent">Send User-Agent header</a>
1604 </dt>
1605
1606 <dd>
1607 <p>Controls whether the user-agent string will be sent.</p>
1608 </dd>
1609
1610 <dt><a name="optinfo-session_file" id=
1611 "optinfo-session_file">Session file</a>
1612 </dt>
1613
1614 <dd>
1615 <p>Define the file name where lynx will store user sessions.
1616 This setting is used only when <em>Auto Session</em> is
1617 enabled.</p>
1618 </dd>
1619
1620 <dt><a name="optinfo-show_color" id="optinfo-show_color">Show
1621 color</a>
1622 </dt>
1623
1624 <dd>
1625 <p>This option will be present if color support is available.
1626 If set to ON or ALWAYS, color mode will be forced on if
1627 possible. If (n)curses color support is available but cannot
1628 be used for the current terminal type, selecting ON is
1629 rejected with a message. If set to OFF or NEVER, color mode
1630 will be turned off.</p>
1631
1632 <p>ALWAYS and NEVER are not offered in anonymous accounts. If
1633 saved to a <em>.lynxrc</em> file in non-anonymous accounts,
1634 ALWAYS will cause Lynx to set color mode on at startup if
1635 supported. If Lynx is built with the slang library, this is
1636 equivalent to having included the <em>-color</em> command
1637 line switch or having the <em>COLORTERM</em> environment
1638 variable set. If color support is provided by curses or
1639 ncurses, this is equivalent to the default behavior of using
1640 color when the terminal type supports it. If (n)curses color
1641 support is available but cannot be used for the current
1642 terminal type, the preference can still be saved but will
1643 have no effect.</p>
1644
1645 <p>A saved value of NEVER will cause Lynx to assume a
1646 monochrome terminal at startup. It is similar to the
1647 <em>-nocolor</em> switch, but (when the slang library is
1648 used) can be overridden with the <em>-color</em> switch.</p>
1649
1650 <p>If the setting is OFF or ON when the current options are
1651 saved to a <em>.lynxrc</em> file, the default startup
1652 behavior is retained, such that color mode will be turned on
1653 at startup only if the terminal info indicates that you have
1654 a color-capable terminal, or (when the slang library is used)
1655 if forced on via the <em>-color</em> switch or
1656 <em>COLORTERM</em> variable. This default behavior always is
1657 used in anonymous accounts, or if the <em>option_save</em>
1658 restriction is set explicitly. If for any reason the startup
1659 color mode is incorrect for your terminal, set it
1660 appropriately on or off via this option.</p>
1661 </dd>
1662
1663 <dt><a name="optinfo-show_cursor" id="optinfo-show_cursor">Show
1664 cursor</a>
1665 </dt>
1666
1667 <dd>
1668 <p>Lynx normally hides the cursor by positioning it to the
1669 right and if possible the very bottom of the screen, so that
1670 the current link or OPTION is indicated solely by its
1671 highlighting or color. If show cursor is set to ON, the
1672 cursor will be positioned at the left of the current link or
1673 OPTION. This is helpful when Lynx is being used with a speech
1674 or braille interface. It also is useful for sighted users
1675 when the terminal cannot distinguish the character attributes
1676 used to distinguish the current link or OPTION from the
1677 others in the screen display.</p>
1678 </dd>
1679
1680 <dt><a name="optinfo-show_dot_files" id=
1681 "optinfo-show_dot_files">Show dot files</a>
1682 </dt>
1683
1684 <dd>
1685 <p>If display/creation of hidden (dot) files/directories is
1686 enabled, you can turn the feature on or off via this
1687 setting.</p>
1688 </dd>
1689
1690 <dt><a name="optinfo-show_images" id="optinfo-show_images">Show
1691 images</a>
1692 </dt>
1693
1694 <dd>
1695 <p>This allows you to select the way in which Lynx shows
1696 image links. These are the available selections:</p>
1697
1698 <ul>
1699 <li><em>ignore</em> to suppress the links altogether,</li>
1700
1701 <li><em>as labels</em> to show the descriptive text for the
1702 link</li>
1703
1704 <li><em>as links</em>, which allows you to use an external
1705 viewer</li>
1706 </ul>
1707 <br>
1708 </dd>
1709
1710 <dt><a name="optinfo-show_scrollbar" id=
1711 "optinfo-show_scrollbar">Show scrollbar</a>
1712 </dt>
1713
1714 <dd>
1715 <p>This allows you to enable (show) or disable (hide) the
1716 scrollbar on the right-margin of the display. This feature is
1717 available with ncurses or slang libraries.</p>
1718 </dd>
1719
1720 <dt><a name="optinfo-show_transfer_rate" id=
1721 "optinfo-show_transfer_rate">Show transfer rate</a>
1722 </dt>
1723
1724 <dd>
1725 <p>This allows you to select the way in which Lynx shows its
1726 progress in downloading large pages. It displays its progress
1727 in the status line. These are the available selections:</p>
1728
1729 <ul>
1730 <li>Do not show rate</li>
1731
1732 <li>Local directory sort order</li>
1733
1734 <li>Show dot files</li>
1735
1736 <li>Execution links</li>
1737
1738 <li>Pause when showing message</li>
1739
1740 <li>Show transfer rate</li>
1741 </ul>
1742 <br>
1743 </dd>
1744
1745 <dt><a name="optinfo-ssl_prompting" id=
1746 "optinfo-ssl_prompting">SSL Prompting</a>
1747 </dt>
1748
1749 <dd>
1750 <p>This allows you to tell how to handle errors detected in
1751 SSL connections <em>prompt normally</em> to prompt for each
1752 cookie, <em>force yes-response</em> to reply "yes" to each
1753 prompt, <em>force no-response</em> to reply "no" to each
1754 prompt.</p>
1755 </dd>
1756
1757 <dt><a name="optinfo-trim_blank_lines" id=
1758 "optinfo-trim_blank_lines">Trim blank lines</a>
1759 </dt>
1760
1761 <dd>
1762 <p>If <em>Trim blank lines</em> is turned off, Lynx will not
1763 trim trailing blank lines from the document. Also, Lynx will
1764 not collapse <code>BR</code>-tags onto the previous line when
1765 it happens to be empty as part of the <em>Collapse BR
1766 tags</em> feature.</p>
1767 </dd>
1768
1769 <dt><a name="optinfo-type_of_search" id=
1770 "optinfo-type_of_search">Type of Search</a>
1771 </dt>
1772
1773 <dd>
1774 <p>Searching type has two possible values: CASE INSENSITIVE
1775 (default) and CASE SENSITIVE. The searching type effects
1776 inter-document searches only, and determines whether searches
1777 for words within documents will be done in a case-sensitive
1778 or case-insensitive manner.</p>
1779 </dd>
1780
1781 <dt><a name="optinfo-use_html5_charset" id=
1782 "optinfo-use_html5_charset">Use HTML5 charset replacements</a>
1783 </dt>
1784
1785 <dd>
1786 <p>This option allows lynx to treat pages with ISO-8859-1
1787 (Latin1) or ASCII encoding as if they were Windows 1252. That
1788 allows a few punctuation characters to be shown.</p>
1789 </dd>
1790
1791 <dt><a name="optinfo-locale_based_charset" id=
1792 "optinfo-locale_based_charset">Use locale-based character
1793 set</a>
1794 </dt>
1795
1796 <dd>
1797 <p>This option allows you to request lynx to obtain a MIME
1798 name from the operating system which corresponds to your
1799 locale setting. If successful, it overrides the normal
1800 setting of the display character set.</p>
1801 </dd>
1802
1803 <dt><a name="optinfo-underline_links" id=
1804 "optinfo-underline_links">Underline links</a>
1805 </dt>
1806
1807 <dd>
1808 <p>Use underline-attribute rather than bold for links.</p>
1809 </dd>
1810
1811 <dt><a name="optinfo-use_passive_ftp" id=
1812 "optinfo-use_passive_ftp">Use Passive FTP</a>
1813 </dt>
1814
1815 <dd>
1816 <p>This allows you to change whether Lynx uses passive ftp
1817 connections.</p>
1818 </dd>
1819
1820 <dt><a name="optinfo-user_agent" id=
1821 "optinfo-user_agent">User-Agent header</a>
1822 </dt>
1823
1824 <dd>
1825 <p>The header string which Lynx sends to HTTP servers to
1826 indicate the User-Agent is displayed here. Changes may be
1827 disallowed via the <em>-restrictions</em> switch. Otherwise,
1828 the header can be changed temporarily to a string such as
1829 <em>L_y_n_x/2.9.3</em> for access to sites which discriminate
1830 against Lynx based on checks for the presence of "Lynx" in
1831 the header. If the User-Agent header has been changed, it can
1832 be restored to the built-in default value by deleting the
1833 modified string in the Options Menu. Whenever the User-Agent
1834 header is changed, the current document is reloaded, with the
1835 no-cache flags set, on exit from the Options Menu. Changes of
1836 the header are not saved in the RC file.</p>
1837 </dd>
1838
1839 <dd>
1840 <p><em id="noteUA">NOTE:</em> Some sites may regard
1841 misrepresenting the browser as fraudulent deception, or as
1842 gaining unauthorized access, if it is used to circumvent
1843 blocking that was intentionally put in place. Some browser
1844 manufacturers may find the transmission of their product's
1845 name objectionable. If you change the User-Agent string, it
1846 is your responsibility. The Options Menu issues a reminder
1847 whenever the header is changed to one which does not include
1848 "Lynx" or "L_y_n_x".</p>
1849 </dd>
1850
1851 <dt><a name="optinfo-user_mode" id="optinfo-user_mode">User
1852 Mode</a>
1853 </dt>
1854
1855 <dd>
1856 <p>There are four possible choices: Novice, Intermediate,
1857 Advanced, and Minimal.</p>
1858
1859 <dl>
1860 <dt>Novice</dt>
1861
1862 <dd>
1863 <p>In Novice mode two lines of help are displayed at the
1864 bottom of the screen.</p>
1865 </dd>
1866
1867 <dt>Intermediate</dt>
1868
1869 <dd>
1870 <p>Intermediate mode turns off the help lines.</p>
1871 </dd>
1872
1873 <dt>Advanced</dt>
1874
1875 <dd>
1876 <p>Advanced mode displays the URL of the currently
1877 selected link at the bottom of the screen.</p>
1878 </dd>
1879
1880 <dt>Minimal</dt>
1881
1882 <dd>
1883 <p>Minimal mode eliminates the URL on the bottom line,
1884 the forward/backward indicator in the upper left, and
1885 most status-line messages.</p>
1886 </dd>
1887 </dl>
1888 </dd>
1889
1890 <dt><a name="optinfo-verbose_images" id=
1891 "optinfo-verbose_images">Verbose Images</a>
1892 </dt>
1893
1894 <dd>
1895 <p>Controls whether or not Lynx replaces the [LINK], [INLINE]
1896 and [IMAGE] comments (for images without ALT) with filenames
1897 of these images. This is extremely useful because now we can
1898 determine immediately what images are just decorations
1899 (button.gif, line.gif) and what images are important. This
1900 setting can also be toggled on startup via the
1901 <em>-verbose</em> switch.</p>
1902 </dd>
1903
1904 <dt><a name="optinfo-vi_keys" id="optinfo-vi_keys">VI keys</a>
1905 </dt>
1906
1907 <dd>
1908 <p>If set to ON then the lowercase h, j, k, and l keys will
1909 be mapped to left, down, up, and right arrow, respectively.
1910 The uppercase H, J, K, and L keys remain mapped to their
1911 configured bindings (normally HELP, JUMP, KEYMAP, and LIST,
1912 respectively).</p>
1913
1914 <p>Note: this has no effect on the line-editor's key
1915 bindings.</p>
1916 </dd>
1917
1918 <dt><a name="optinfo-visited_pages" id=
1919 "optinfo-visited_pages">Visited Pages</a>
1920 </dt>
1921
1922 <dd>
1923 <p>Enable several different views of the visited links:</p>
1924
1925 <dl>
1926 <dt>By First Visit</dt>
1927
1928 <dt>By First Visit Reversed</dt>
1929
1930 <dt>As Visit Tree</dt>
1931
1932 <dt>By Last Visit</dt>
1933
1934 <dt>By Last Visit Reversed</dt>
1935 </dl>
1936 <br>
1937 </dd>
1938
1939 <dt><a name="optinfo-x_display" id="optinfo-x_display">X
1940 Display</a>
1941 </dt>
1942
1943 <dd>
1944 <p>This option is only relevant to X Window users. The
1945 DISPLAY (Unix) or DECW$DISPLAY (VMS) variable is picked up
1946 automatically from the environment if it has been previously
1947 set.</p>
1948 </dd>
1949 </dl>
1950
1951 <p>[<a href="#ToC-InteractiveOptions">ToC</a>]</p>
1952
1953 <h2 id="id-Mail"><a name="Mail" id="Mail">Comments and mailto:
1954 links</a></h2>
1955
1956 <p>At any time while viewing documents within Lynx, you may use
1957 the &ldquo;<samp>c</samp>&rdquo; command to send a mail message
1958 to the owner of the current document if the author of the
1959 document has specified ownership.</p>
1960
1961 <p>Note to authors: if you want to assign the ownership to your
1962 document, you need to add into HEAD section a LINK element with
1963 appropriate value for the REL (HTML5) or REV (HTML4)
1964 attribute.</p>
1965
1966 <p>One value is recognized for REL: <em>author</em>
1967 (case-insensitive). For example:</p>
1968
1969 <pre>
1970 &lt;HEAD&gt;
1971 &hellip;
1972 &lt;LINK REL="author" HREF="mailto:[email protected]"&gt;
1973 &hellip;
1974 &lt;/HEAD&gt;
1975 </pre>
1976 <p>Two values are recognized for REV: <em>owner</em> and
1977 <em>made</em> (case insensitive). For example,</p>
1978
1979 <pre>
1980 &lt;HEAD&gt;
1981 &hellip;
1982 &lt;LINK REV="made" HREF="mailto:[email protected]"&gt;
1983 &hellip;
1984 &lt;/HEAD&gt;
1985 </pre>
1986 <p>You may also add a TITLE attribute with, for example, the name
1987 of your page) If no ownership is specified then comments are
1988 disabled. Certain links called <a href=
1989 "lynx_url_support.html#mailto_url">mailto:</a> links will also
1990 allow you to send mail to other people. Using the mail features
1991 within Lynx is straightforward.</p>
1992
1993 <p>Once you have decided to send a comment or have selected a
1994 <em>mailto:</em> link a new screen will appear showing you to
1995 whom you are sending the message. Lynx will ask for your name,
1996 your e-mail address, and the subject of the message. If you have
1997 filled in the "personal mail address" field in the <em>Options
1998 Menu</em>, your e-mail address will be filled in automatically.
1999 After entering the above information, if you have an editor
2000 defined in the <em>Options Menu</em> and you are not an anonymous
2001 user then your specified editor will be spawned for you so that
2002 you can enter your message. If you do not have an editor defined
2003 or you are an anonymous user, a simple line mode input scheme
2004 will allow you to enter your message.</p>
2005
2006 <p>To finish sending the message, exit your spawned editor or, if
2007 you are using the simple line mode input scheme, type a
2008 &ldquo;<samp>.</samp>&rdquo; (period) on a line by itself. You
2009 will be asked a final time whether to send the message. If you
2010 press &ldquo;<samp>y</samp>&rdquo;, you will be prompted whether
2011 to append your signature file if one was defined in <a href=
2012 "#lynx.cfg">lynx.cfg</a> and is accessible, and then the message
2013 will be sent, whereas if you press &ldquo;<samp>n</samp>&rdquo;
2014 the message will be deleted. Entering Control-G in response to
2015 any prompts also will cancel the mailing.</p>
2016
2017 <p>[<a href="#ToC-Mail">ToC</a>]</p>
2018
2019 <h2 id="id-News"><a name="News" id="News">USENET News posting</a></h2>
2020
2021 <p>While reading <a href=
2022 "http://www.w3.org/LineMode/User/AboutNewsServers.html">news</a>
2023 articles with Lynx you should see a link that says <em>Reply to:
2024 user@host</em> and, if the nntp server from which you received
2025 the article supports posting from your site, a link that says
2026 <em>Followup to: newsgroup(s)</em></p>
2027
2028 <dl>
2029 <dt>Reply to user@host</dt>
2030
2031 <dd>
2032 <p>user@host will correspond to the mail address of the
2033 person who posted the news article. Selecting the link will
2034 allow you to send a message to the person who wrote the
2035 message you are currently viewing. You will be given the
2036 option of including the original message in your reply.</p>
2037 </dd>
2038
2039 <dt>Followup to newsgroup(s)</dt>
2040
2041 <dd>
2042 <p>Selecting this link will allow you to post back to the
2043 newsgroup that you are currently reading and any newsgroups
2044 to which the message was cross-posted. You will be given the
2045 option of including the original message in your reply. Once
2046 you have typed in your message, you will be asked for
2047 confirmation of whether to proceed with the posting, and
2048 whether to append your signature file if one was defined in
2049 <a href="#lynx.cfg">lynx.cfg</a> and is accessible. See
2050 <a href="lynx_url_support.html">Supported URLs</a> for more
2051 information about the URL schemes for posting or sending
2052 followups (replies) to nntp servers with Lynx. [<a href=
2053 "#ToC-News">ToC</a>]</p>
2054 </dd>
2055 </dl>
2056
2057 <p>See also <a href=
2058 "http://www.w3.org/Protocols/rfc977/rfc977">RFC 977</a>.</p>
2059
2060 <h2 id="id-Bookmarks"><a name="Bookmarks" id="Bookmarks">Lynx
2061 bookmarks</a></h2>
2062
2063 <p>Bookmarks are entries in your <em>bookmark file</em>, which
2064 record the URL of a document you may want to return to easily,
2065 with a name of your choice to identify the document. To use
2066 bookmarks you must first have specified a name for your bookmark
2067 file in <a href="#lynx.cfg">lynx.cfg</a> or via the <em>Options
2068 Menu</em>.</p>
2069
2070 <p>To save a bookmark to the document you wish to place in the
2071 bookmark file press the &ldquo;<samp>a</samp>&rdquo; key and you
2072 will be asked:</p>
2073
2074 <blockquote>
2075 <p>Save D)ocument or L)ink to bookmark file or C)ancel?
2076 (d,l,c):</p>
2077 </blockquote>
2078
2079 <p>Answer &ldquo;<samp>d</samp>&rdquo; to save a link to the
2080 document you are currently viewing or
2081 &ldquo;<samp>l</samp>&rdquo; to save the link that is currently
2082 selected on the page. Selecting &ldquo;<samp>c</samp>&rdquo; will
2083 cancel without saving anything to your bookmark file.</p>
2084
2085 <p>A bookmark file will be created in conjunction with acting on
2086 the &ldquo;<samp>a</samp>&rdquo;dd command if it does not already
2087 exist. Otherwise, the link will be added to the bottom of the
2088 pre-existing bookmark file. You must have created a bookmark file
2089 via the &ldquo;<samp>a</samp>&rdquo;dd command before you can
2090 view it.</p>
2091
2092 <p>Use the &ldquo;<samp>v</samp>&rdquo; command to view the list
2093 of bookmarks you have saved. While viewing the bookmark list you
2094 may select a bookmark as you would any other link.</p>
2095
2096 <p>You can remove a link from the bookmark list by pressing the
2097 &ldquo;<samp>r</samp>&rdquo; key when positioned on that link.
2098 You also can use a standard text editor (e.g., via the
2099 &ldquo;<samp>e</samp>&rdquo;dit command while viewing a bookmark
2100 file, if an external editor has been defined via the <em>Options
2101 menu</em>) to delete or re-order links in the bookmark file, or
2102 to modify a link name by editing the content of the
2103 <em>A</em>nchor element for the link, but you should not change
2104 the format within the line for the link, consisting of an
2105 <em>LI</em> element followed by the <em>A</em>nchor element, nor
2106 cause the line to become wrapped to a second line. You similarly
2107 can change the link destination by editing the double-quoted
2108 value for the <em>HREF</em> attribute in the <em>A</em>nchor
2109 start tag, but you should not otherwise change the spacing within
2110 the start tag, nor add other attributes. You can add a new link
2111 while editing by copying an existing line for a link, to ensure
2112 the proper format, and then modifying its <em>HREF</em> value and
2113 <em>A</em>nchor content, but you should not add any other HTML
2114 markup to the bookmark file. If the format and spacing (other
2115 than the <em>A</em>nchor content or <em>HREF</em> value) within
2116 lines is changed or other HTML markup is added, the
2117 &ldquo;<samp>a</samp>&rdquo;dd and
2118 &ldquo;<samp>r</samp>&rdquo;emove commands may not work
2119 properly.</p>
2120
2121 <p>When multi-bookmarks (see <a href=
2122 "#InteractiveOptions">Options Menu</a>) is OFF, you will always
2123 view or add links to the default bookmark file. When it is
2124 STANDARD, a menu of up to 26 bookmark files will be invoked, and
2125 you select the bookmark file by entering its letter token. When
2126 it is ADVANCED, you will be prompted for the letter token, but
2127 can enter &ldquo;<samp>=</samp>&rdquo; to invoke the STANDARD
2128 selection menu, or <em>RETURN</em> for the default bookmark file.
2129 [<a href="#ToC-Bookmarks">ToC</a>]</p>
2130
2131 <h2 id="id-Jumps"><a name="Jumps" id="Jumps">Jump Command</a></h2>
2132
2133 <p>Similar to the bookmarks file is the jumps file: for an
2134 example, look in the <em>samples</em> subdirectory in the
2135 distribution package. To use the jumps command, create a
2136 <em>jumps file</em> with the same format as the sample file, but
2137 containing your own URLs &amp; short-cut names. Once you have
2138 done that, typing &ldquo;<samp>j</samp>&rdquo; prompts you to
2139 enter a short-cut name, which will take you straight to the URL
2140 associated with the short-cut in the jumps file, much like using
2141 &ldquo;<samp>g</samp>&rdquo;. If you want to check which
2142 short-cuts are available, type &ldquo;<samp>?</samp>&rdquo; at
2143 the jump prompt for the full list.</p>
2144
2145 <p>You can set up a jumps file which makes Lynx prompt for
2146 parameters, e.g., as part of a search. Do this by putting a "%s"
2147 marker in the URL at each point where you want Lynx to fill in
2148 text. When you activate the corresponding jump, Lynx will prompt
2149 you for the parameters, one by one.</p>
2150
2151 <p>All jump short-cuts you have entered are saved in a circular
2152 buffer in the same way as with &ldquo;<samp>g</samp>&rdquo; and
2153 &ldquo;<samp>/</samp>&gt;&rdquo; (search):</p>
2154
2155 <p>previous entries can be retrieved with <em>up-arrow</em> or
2156 <em>down-arrow</em>.</p>
2157
2158 <p>The jumps feature is especially useful for system
2159 administrators who have unsophisticated users to care for, but
2160 ordinary Lynx users who have a number of URLs they regularly
2161 visit while browsing may find using the jumps command speeds
2162 their movements.</p>
2163
2164 <p>For more advice how to set up the jumps command on your system
2165 and how to define short-cut names, read <a href=
2166 "#lynx.cfg">lynx.cfg</a> .</p>
2167
2168 <p>[<a href="#ToC-Jumps">ToC</a>]</p>
2169
2170 <h2 id="id-DirEd"><a name="DirEd" id="DirEd">Directory
2171 Editing</a></h2>
2172
2173 <p>Lynx offers extended DIRED support on Unix (on VMS the more
2174 powerful CSwing program is recommended for character cell
2175 terminals, and can be offered via Lynx as a jump shortcut or
2176 execution link). When a local directory is accessed using a URL
2177 of the form <em>file://localhost/path/</em>, a new set of
2178 commands is available. With DIRED support you can create, edit,
2179 delete, copy, and move files on your local system. The commands
2180 available in DIRED mode are</p>
2181
2182 <dl>
2183 <dt><code>C)reate</code>
2184 </dt>
2185
2186 <dd>
2187 <p>Type &ldquo;<samp>c</samp>&rdquo; to create a new file.
2188 New file will be empty.</p>
2189 </dd>
2190
2191 <dt><code>D)ownload</code>
2192 </dt>
2193
2194 <dd>
2195 <p>Type &ldquo;<samp>d</samp>&rdquo; to download using one of
2196 the pre-defined options.</p>
2197 </dd>
2198
2199 <dt><code>E)dit</code>
2200 </dt>
2201
2202 <dd>
2203 <p>Type &ldquo;<samp>e</samp>&rdquo; to spawn the editor
2204 defined in <em>Options Menu</em> and load a selected file for
2205 editing.</p>
2206 </dd>
2207
2208 <dt><code>F)ull Menu</code>
2209 </dt>
2210
2211 <dd>
2212 <p>Type &ldquo;<samp>f</samp>&rdquo; to show full menu of
2213 options available for selection. Menu may vary according to
2214 type of file selected and compression facilities available.
2215 <!-- List of full menu options --></p>
2216 </dd>
2217
2218 <dt><code>M)odify</code>
2219 </dt>
2220
2221 <dd>
2222 <p>Type &ldquo;<samp>m</samp>&rdquo; to modify the name or
2223 location of file. Then type &ldquo;<samp>n</samp>&rdquo; to
2224 rename the file or &ldquo;<samp>l</samp>&rdquo; to move the
2225 file to a different location.</p>
2226 </dd>
2227
2228 <dt><code>R)emove</code>
2229 </dt>
2230
2231 <dd>
2232 <p>Type &ldquo;<samp>r</samp>&rdquo; to remove the selected
2233 file or directory.</p>
2234 </dd>
2235
2236 <dt><code>T)ag</code>
2237 </dt>
2238
2239 <dd>
2240 <p>Type &ldquo;<samp>t</samp>&rdquo; to tag highlighted file.
2241 Further operations will be performed on tagged files instead
2242 of highlighted ones.</p>
2243 </dd>
2244
2245 <dt><code>U)pload</code>
2246 </dt>
2247
2248 <dd>
2249 <p>Type &ldquo;<samp>u</samp>&rdquo; to upload a file to the
2250 present directory. An uploading method must have been
2251 pre-defined in <a href="#lynx.cfg">lynx.cfg</a> .</p>
2252 </dd>
2253 </dl>
2254
2255 <p>[<a href="#ToC-DirEd">ToC</a>]</p>
2256
2257 <h2 id="id-ColorMouse"><a name="ColorMouse" id="ColorMouse">Using
2258 Color &amp; the Mouse</a></h2>
2259
2260 <p>A limited range of colors &amp; mouse commands are available,
2261 if the user chooses: see <em>lynx.cfg</em> for details. [<a href=
2262 "#ToC-ColorMouse">ToC</a>]</p>
2263
2264 <h2 id="id-MiscKeys"><a name="MiscKeys" id="MiscKeys">Scrolling
2265 and Other useful commands</a></h2>
2266
2267 <p>A summary of all the keystroke commands and their key bindings
2268 can be invoked via the KEYMAP command, normally mapped to
2269 &ldquo;<samp>k</samp>&rdquo; and &ldquo;<samp>K</samp>&rdquo;.
2270 The following describes some of the most commonly used
2271 commands.</p>
2272
2273 <dl>
2274 <dt><strong><em>^A</em></strong>
2275 </dt>
2276
2277 <dd>
2278 <p><em>Control-A</em> jumps you to the beginning of the
2279 current document. It is a synonym for the Keypad
2280 <em>Home</em> key, and can be used also when <em>Links are
2281 numbered</em> mode is on. The <em>Find</em> Function key also
2282 is a synonym, and ideally the latter has been mapped to the
2283 Function key labeled <em>Home</em> if you are using an IBM
2284 Enhanced Keyboard.</p>
2285 </dd>
2286
2287 <dt><strong><em>^E</em></strong>
2288 </dt>
2289
2290 <dd>
2291 <p><em>Control-E</em> jumps you to the end of the current
2292 document. It is a synonym for the Keypad <em>End</em> key,
2293 and can be used also when <em>Links are numbered</em> mode is
2294 on. The <em>Select</em> Function key also is a synonym, and
2295 ideally the latter has been mapped to the Function key
2296 labeled <em>End</em> if you are using an IBM Enhanced
2297 Keyboard.</p>
2298 </dd>
2299
2300 <dt><strong><em>^B</em></strong>
2301 </dt>
2302
2303 <dd>
2304 <p><em>Control-B</em> normally jumps you to the previous page
2305 of the current document, and thus is a synonym for the Keypad
2306 and Function <em>Page-Up</em> keys. However,
2307 <em>Control-B</em> acts as <em>right-arrow</em> when
2308 emacs-like key movement is enabled (see <a href=
2309 "#InteractiveOptions">Lynx Options Menu</a>).</p>
2310 </dd>
2311
2312 <dt><strong><em>^F</em></strong>
2313 </dt>
2314
2315 <dd>
2316 <p><em>Control-F</em> normally jumps you to the next page of
2317 the current document, and thus is a synonym for the Keypad
2318 and Function <em>Page-Down</em> keys. However,
2319 <em>Control-F</em> becomes <em>right-arrow</em> when
2320 emacs-like key movement is enabled.</p>
2321 </dd>
2322
2323 <dt><strong><em>^N</em></strong>
2324 </dt>
2325
2326 <dd>
2327 <p><em>Control-N</em> normally jumps you forward two lines in
2328 the current document. The VT220 <em>Remove</em> Function key
2329 (labeled <em>Delete</em> on IBM Enhanced keyboards, and
2330 distinct from their <em>Backspace</em> key) is a synonym.
2331 <em>Control-N</em> becomes <em>down-arrow</em> when
2332 emacs-like key movement is enabled.</p>
2333 </dd>
2334
2335 <dt><strong><em>^P</em></strong>
2336 </dt>
2337
2338 <dd>
2339 <p><em>Control-P</em> normally jumps you back two lines in
2340 the current document. The <em>Insert</em> Function key is a
2341 synonym. <em>Control-P</em> becomes <em>up-arrow</em> when
2342 emacs-like key movement is enabled.</p>
2343 </dd>
2344
2345 <dt><strong><em>^K</em></strong>
2346 </dt>
2347
2348 <dd>
2349 <p><em>Control-K</em> invokes the <a href=
2350 "keystrokes/cookie_help.html">Cookie Jar Page</a> if it
2351 contains cookies.</p>
2352 </dd>
2353
2354 <dt><strong><em>^T</em></strong>
2355 </dt>
2356
2357 <dd>
2358 <p><em>Control-T</em> toggles Lynx trace mode on and off.
2359 This is useful for diagnosing bad html. If you get a <em>Bad
2360 HTML</em> statusline message when loading a document, enter
2361 <em>Control-T</em> and then <em>Control-R</em> to reload the
2362 document in trace mode. You may then examine the <em>Lynx
2363 Trace Log</em> file with the <samp>;</samp> command if
2364 enabled (see below), watch out especially for lines marked
2365 with a number of asterisks &ldquo;<code>*****</code>&rdquo;.
2366 You also can submit the document for validation via links in
2367 the online help menu. If you are able to diagnose the
2368 problem, send a message about it to the document's
2369 author.</p>
2370 </dd>
2371
2372 <dt><strong><em>^X</em></strong>
2373 </dt>
2374
2375 <dd>
2376 <p><em>Control-X</em> invokes the <a href="#Cache">Cache Jar
2377 Page</a> if it contains cached documents.</p>
2378 </dd>
2379
2380 <dt><strong><samp>E</samp></strong>
2381 </dt>
2382
2383 <dd>
2384 <p>The &ldquo;<samp>E</samp>&rdquo; command allows you to
2385 edit the URL (or ACTION) of the current link and then use
2386 that as a goto URL. Pressing the &ldquo;<samp>E</samp>&rdquo;
2387 command will bring up a prompt asking you to edit the current
2388 link's URL. If you do not modify it, or completely delete it,
2389 or enter Control-G, the command will be cancelled. Otherwise,
2390 the request for the &ldquo;E&rdquo;dited URL will be sent
2391 with method GET, and will be entered into the circular buffer
2392 for goto URLs so that it can be accessed for further
2393 modification via the &ldquo;<samp>g</samp>&rdquo; command.
2394 Note that lower case &ldquo;e&rdquo; invokes the external
2395 editor for the current document.</p>
2396 </dd>
2397
2398 <dt><strong><samp>g</samp></strong>
2399 </dt>
2400
2401 <dd>
2402 <p>The &ldquo;<samp>g</samp>&rdquo; command allows any URL to
2403 be viewed. Pressing the &ldquo;<samp>g</samp>&rdquo; command
2404 will bring up a prompt asking for a URL. Type in the URL that
2405 you wish to view. All previously entered goto URLs are saved
2406 in a circular buffer, and can be accessed at the prompt by
2407 pressing the <em>up-arrow</em> or <em>down-arrow</em>
2408 keys.</p>
2409 </dd>
2410
2411 <dt><strong><samp>G</samp></strong>
2412 </dt>
2413
2414 <dd>
2415 <p>The &ldquo;<samp>G</samp>&rdquo; command allows you to
2416 edit the URL of the current document and then use that as a
2417 goto URL. Pressing the &ldquo;<samp>G</samp>&rdquo; command
2418 will bring up a prompt asking you to edit the current
2419 document's URL. If you do not modify it, or completely delete
2420 it, or enter Control-G, the command will be cancelled. If the
2421 current document has POST content associated with it, an
2422 Alert will be issued. If you do edit that URL, and it does
2423 not simply involve a fragment change (for seeking a position
2424 in the current document), the modified URL will be submitted
2425 with method GET and no POST content. If a modification of the
2426 current document's URL results in a submission, that modified
2427 URL will be entered into the circular buffer for goto URLs,
2428 and can be accessed for further modification via the
2429 &ldquo;<samp>g</samp>&rdquo; command.</p>
2430 </dd>
2431
2432 <dt><strong><samp>z</samp></strong>
2433 </dt>
2434
2435 <dd>
2436 <p>Lynx supports completely interruptible I/O processes.
2437 Press the &ldquo;<samp>z</samp>&rdquo; key at any time during
2438 a connect or transfer process and the process will be halted.
2439 If any data was transferred before the interrupt, it will be
2440 displayed.</p>
2441 </dd>
2442
2443 <dt><strong><samp>)</samp></strong>
2444 </dt>
2445
2446 <dd>
2447 <p>The <samp>)</samp> command jumps you forward half a page
2448 in the current document.</p>
2449 </dd>
2450
2451 <dt><strong><samp>(</samp></strong>
2452 </dt>
2453
2454 <dd>
2455 <p>The <samp>(</samp> command jumps you back half a page in
2456 the current document.</p>
2457 </dd>
2458
2459 <dt><strong><samp>#</samp></strong>
2460 </dt>
2461
2462 <dd>
2463 <p>The &ldquo;<samp>#</samp>&rdquo; command jumps you to the
2464 pseudo Toolbar or Banner if present in the current document.
2465 Use <em>left-arrow</em> to return from there to your previous
2466 position in the document.</p>
2467 </dd>
2468
2469 <dt><strong><samp>!</samp></strong>
2470 </dt>
2471
2472 <dd>
2473 <p>When &ldquo;<samp>!</samp>&rdquo; is pressed your default
2474 shell will be spawned. When you quit or exit the shell you
2475 will return to Lynx (usually <em>exit</em> under Unix and
2476 <em>logout</em> under VMS). This command is usually disabled
2477 for anonymous users. On VMS, &ldquo;<samp>$</samp>&rdquo;
2478 normally is a synonym.</p>
2479 </dd>
2480
2481 <dt><strong><samp>=</samp></strong>
2482 </dt>
2483
2484 <dd>
2485 <p>The &ldquo;<samp>=</samp>&rdquo; command shows information
2486 about the current document and the currently selected link if
2487 there is one. The number of lines in the file, URL, title,
2488 owner, and type are shown.</p>
2489
2490 <p>Normally the information is shown formatted (with margins)
2491 for readability. You can make Lynx show the URL wrapped
2492 without margins, e.g., making it convenient for select/paste,
2493 by doing this:</p>
2494
2495 <ul>
2496 <li>toggle line-wrapping off using
2497 &ldquo;<samp>|</samp>&rdquo;</li>
2498
2499 <li>when line-wrapping is off, use the
2500 &ldquo;<samp>=</samp>&rdquo; command</li>
2501 </ul>
2502 </dd>
2503
2504 <dt><strong><samp>;</samp></strong>
2505 </dt>
2506
2507 <dd>
2508 <p>The <samp>;</samp> command shows the <em>Lynx Trace
2509 Log</em> (<em>Lynx.trace</em> in the home directory) if one
2510 has been started for the current session. If a log has not
2511 been started, any trace messages will be sent to the screen
2512 (and will disturb the normal display) unless the system
2513 supports piping and that was used to redirect stderr messages
2514 to a file. The log is started when Lynx trace mode is turned
2515 on via the <em>-trace</em> command line switch, or via the
2516 <em>Control-T</em> toggle, if Lynx has been compiled to log
2517 the trace and other stderr messages by default. If not,
2518 ability to create a log can be toggled on with the
2519 <em>-tlog</em> switch. Note that this ability is probably
2520 disabled in anonymous or validation accounts.</p>
2521 </dd>
2522
2523 <dt><a name="asterisk-key" id=
2524 "asterisk-key"><strong><samp>*</samp></strong></a>
2525 </dt>
2526
2527 <dd>
2528 <p>The &ldquo;<samp>*</samp>&rdquo; command toggles
2529 image_links mode on and off. When on, links will be created
2530 for all images, including inline images. If you have an image
2531 viewer mapped to the image's MIME type, you can activate such
2532 links to view an inline image. You should normally have this
2533 mode toggled off.</p>
2534 </dd>
2535
2536 <dt><strong><samp>@</samp></strong>
2537 </dt>
2538
2539 <dd>
2540 <p>The &ldquo;<samp>@</samp>&rdquo; command toggles raw 8-bit
2541 or CJK mode on and off. When on, the charset is assumed to
2542 match the selected character set and 8-bit characters are not
2543 reverse translated with respect to the ISO-8859-1 conversion
2544 tables.</p>
2545 </dd>
2546
2547 <dt><a name="lbracket-key" id=
2548 "lbracket-key"><strong><samp>[</samp></strong></a>
2549 </dt>
2550
2551 <dd>
2552 <p>The &ldquo;<samp>[</samp>&rdquo; command toggles
2553 pseudo_inlines mode on and off. When on, inline images which
2554 have no ALT string specified will have an <em>[INLINE]</em>
2555 pseudo-ALT string inserted in the Lynx display. When off,
2556 they will be treated as having ALT="" (i.e., they will be
2557 ignored). If image_links mode is toggled on, the pseudo-ALT
2558 strings will be restored, to serve as links to the inline
2559 images' sources.</p>
2560 </dd>
2561
2562 <dt><strong><samp>]</samp></strong>
2563 </dt>
2564
2565 <dd>
2566 <p>The &ldquo;<samp>]</samp>&rdquo; command is used to send
2567 HEAD requests for the current document or link. It applies
2568 only to documents or links (or form submit buttons) of http
2569 servers. A statusline message will notify you if the context
2570 for this command was inappropriate. The HEAD requests always
2571 are sent to the http server, i.e., Lynx does not retrieve any
2572 previous server replies from its cache. Note that for form
2573 submissions, http servers vary in whether they'll treat HEAD
2574 requests as valid and return the CGI script's headers, or
2575 treat it as invalid and return an error message.</p>
2576 </dd>
2577
2578 <dt><strong><samp>{</samp></strong>
2579 </dt>
2580
2581 <dd>
2582 <p>If the line-wrapping margin is wider than the terminal's
2583 display, scroll left by half of the display's width.</p>
2584
2585 <p>This feature is not available when Lynx is built using the
2586 slang library.</p>
2587 </dd>
2588
2589 <dt><strong><samp>|</samp></strong>
2590 </dt>
2591
2592 <dd>
2593 <p>&ldquo;<samp>|</samp>&rdquo; toggles Lynx line-wrapping
2594 on/off. Normally Lynx fits text onto the screen, wrapping
2595 lines. With this feature, Lynx provides the ability to
2596 eliminate line-wrapping (up to an internal line-limit of 1000
2597 characters). Lynx uses the curses &ldquo;pad&rdquo; feature
2598 to support left/right scrolling. You can scroll left and
2599 right in the screen to view the wide lines.</p>
2600
2601 <p>The popup menu for the command shows the other choices
2602 which extend the wrapping margin:</p>
2603
2604 <blockquote>
2605 <pre>
2606 /----------------------------------\
2607 | Try to fit screen width |
2608 | No line wrap in columns |
2609 | Wrap columns at screen width |
2610 | Wrap columns at 3/4 screen width |
2611 | Wrap columns at 2/3 screen width |
2612 | Wrap columns at 1/2 screen width |
2613 | Wrap columns at 1/3 screen width |
2614 | Wrap columns at 1/4 screen width |
2615 \----------------------------------/
2616 </pre>
2617 </blockquote>
2618
2619 <p>This feature is not available when Lynx is built using the
2620 slang library.</p>
2621 </dd>
2622
2623 <dt><strong><samp>}</samp></strong>
2624 </dt>
2625
2626 <dd>
2627 <p>If the line-wrapping margin is wider than the terminal's
2628 display, scroll right by half of the display's width.</p>
2629
2630 <p>This feature is not available when Lynx is built using the
2631 slang library.</p>
2632 </dd>
2633
2634 <dt><em>numbers</em>
2635 </dt>
2636
2637 <dd>
2638 <p>Lynx offers other, advanced navigation features when
2639 numbers are used to invoke the <a href=
2640 "keystrokes/follow_help.html">Follow Link (or goto link or
2641 page) number:</a> or <a href=
2642 "keystrokes/follow_help.html#select-option">Select Pop-up
2643 Option Number:</a> prompts.</p>
2644 </dd>
2645 </dl>
2646
2647 <p>[<a href="#ToC-MiscKeys">ToC</a>]</p>
2648
2649 <h2 id="id-Forms"><a name="Forms" id="Forms">Lynx and HTML
2650 Forms</a></h2>
2651
2652 <p>This section describes the Lynx Forms Interface. HTML gives
2653 document providers the ability to create on-line forms which may
2654 be filled out when the document is viewed. When a form is
2655 submitted the information on the form can be used to search a
2656 database or complete a survey.</p>
2657
2658 <p>An HTML Form provides for the use of buttons to perform an
2659 action (such as <em>submit</em>), checkboxes, radio buttons or
2660 popups to select options from a list, and fields for entering
2661 text.</p>
2662
2663 <dl>
2664 <dt>Buttons:</dt>
2665
2666 <dd>
2667 <p>Buttons are displayed in the same way that Lynx displays
2668 links in a document. To "push" the button press the
2669 <em>right-arrow</em> or <em>Return</em> key. If it is a form
2670 submission button, you also can use the NOCACHE
2671 (&ldquo;<samp>x</samp>&rdquo;) or DOWNLOAD
2672 (&ldquo;<samp>d</samp>&rdquo;) keystroke commands to "push"
2673 the button (see below).</p>
2674 </dd>
2675
2676 <dt>Checkboxes and Radio buttons</dt>
2677
2678 <dd>
2679 <p>Checkboxes are displayed as square brackets:
2680 <em>[&nbsp;]</em> and radio buttons are displayed as
2681 parenthesis: <em>(&nbsp;)</em>. When a box is checked or a
2682 button selected, an <samp>x</samp> appears in the brackets:
2683 <em>[x]</em> or an asterisk appears within the parenthesis:
2684 <em>(*)</em>. To check a box or select a radio button press
2685 the <em>right-arrow</em> or <em>Return</em> key.</p>
2686 </dd>
2687
2688 <dt>Selection Fields</dt>
2689
2690 <dd>
2691 <p>Selection fields are displayed as brackets with the
2692 default option displayed between them: <em>[default__]</em>.
2693 To select an option press the <em>right-arrow</em> or
2694 <em>Return</em> key. A box with a border of asterisks (or
2695 line-drawing characters) will pop up with the list of
2696 possible options listed within the box. Use the
2697 <em>up-arrow</em>, <em>down-arrow</em>, <em>page-up</em>,
2698 <em>page-down</em>, and other navigation keys to move the
2699 cursor among options, and the <em>right-arrow</em> or
2700 <em>Return</em> key to select an option. You also can use the
2701 &ldquo;<samp>/</samp>&rdquo; and
2702 &ldquo;<samp>n</samp>&rdquo;ext <a href=
2703 "#Search">searching</a> commands for navigating to options
2704 which contain particular strings. <em>NOTE</em> that the
2705 popup menu feature can be disabled via compilation and/or
2706 configuration options, or via the <a href=
2707 "#InteractiveOptions">Options Menu</a>, in which case the
2708 selection field options will be converted to a list of radio
2709 buttons. The default setting for use of popups or radio
2710 button lists can be toggled via the <em>-popup</em> command
2711 line switch.</p>
2712 </dd>
2713
2714 <dt>Text Entry Fields</dt>
2715
2716 <dd>
2717 <p>Text entry (INPUT) fields are displayed as a row of
2718 underscores the length of the entry field: <em>_______</em>.
2719 You may enter text directly by typing at the keyboard. Use
2720 the <a href="keystrokes/edit_help.html">Line Editor</a> keys
2721 to correct errors. If you try to input more text than the
2722 field can hold, the line editor will not accept the
2723 additional characters. If you fill a text field the cursor
2724 will not move off the field but remain at the last field
2725 position. Use the <em>up-arrow</em>, and <em>down-arrow</em>,
2726 <em>TAB</em> or <em>Return</em> keys to move up, or down from
2727 the text entry field. NOTE, however, that <em>Return</em>
2728 also will <a href="#submit">submit</a> the form if the text
2729 entry field is the only non-hidden field in the form. If
2730 <a name="tna" id="tna">"Textfields Need Activation"</a> mode
2731 is turned on (with the <kbd>-tna</kbd> command-line option or
2732 in <a href="#lynx.cfg">lynx.cfg</a>), then text entry fields
2733 do not become active immediately upon being selected, as
2734 normally. Keystrokes have their normal command meaning unless
2735 the Line Editor gets activated with <em>Return</em> or
2736 <em>Right Arrow</em>. This mode can be used to avoid "getting
2737 stuck" in input fields, especially by users who rarely fill
2738 out forms.</p>
2739
2740 <p><a name="CtrlVNote" id="CtrlVNote">NOTE:</a> If you have a
2741 text input field selected you will not have access to most of
2742 the Lynx keystroke commands, because they are interpreted by
2743 the <a href="keystrokes/edit_help.html">Line Editor</a> as
2744 either text entries or editing commands. Select a button or
2745 box when you want to use Lynx keystrokes; or prefix your
2746 keystroke with <em>^V</em> to temporarily escape from line
2747 editing.</p>
2748
2749 <p>Some flavors of UNIX, shells &amp; terminal settings
2750 require that you enter <em>^V^Ve</em> in order to start the
2751 external editor, as they also use <em>^V</em> as default
2752 command-line quote key (called &ldquo;lnext&rdquo; in stty
2753 man pages and &ldquo;stty -a&rdquo; output); to avoid this,
2754 you can put &ldquo;stty lnext undef&rdquo; in your .cshrc
2755 file (or .profile or .bashrc, depending on what shell you
2756 use), or invoke Lynx with a wrapper script, e.g.</p>
2757
2758 <p><code>&nbsp;&nbsp;#!/bin/sh<br>
2759 &nbsp;&nbsp;stty lnext undef<br>
2760 &nbsp;&nbsp;$HOME/bin/lynx "$@"<br>
2761 &nbsp;&nbsp;stty lnext ^V<br>
2762 &nbsp;&nbsp;exit</code>
2763 </p>
2764
2765 <p>NB when NOT in the Line Editor, <em>^V</em> is by default
2766 bound to the command to switch between SortaSGML and TagSoup
2767 HTML parsing (i.e., SWITCH_DTD). To avoid confusion, either
2768 of these separate functions could be changed (mapped away)
2769 with a KEYMAP directive in <em>lynx.cfg</em>. For
2770 example,</p>
2771
2772 <p>&nbsp;&nbsp;KEYMAP:^V:DO_NOTHING<br>
2773 &nbsp;&nbsp;KEYMAP:#:SWITCH_DTD</p>
2774
2775 <p>would map SWITCH_DTD away from <em>^V</em> to
2776 <samp>#</samp>, while leaving its default Line Editor
2777 function as a command escape in place. On the other hand,</p>
2778
2779 <p>&nbsp;&nbsp;KEYMAP:^V::NOP:1<br>
2780 &nbsp;&nbsp;KEYMAP:^_::LKCMD:1</p>
2781
2782 <p>would move <em>^V</em>'s Line Editor binding as command
2783 escape to <em>^_</em> for the first Line Edit style, letting
2784 <em>^V</em> still act as SWITCH_DTD outside of text input
2785 fields.</p>
2786 </dd>
2787
2788 <dt>TEXTAREA Fields</dt>
2789
2790 <dd>
2791 <p>TEXTAREA fields are for most purposes handled as if they
2792 were a series of text entry (INPUT) fields for which
2793 successive lines imply a newline at the end of the preceding
2794 line. You enter text on each line to construct the overall
2795 message. Any blank lines at the bottom of the TEXTAREA field
2796 will be eliminated from the submission. The
2797 <em>up-arrow</em>, and <em>down-arrow</em> or <em>Return</em>
2798 keys move you to the preceding, or next line of the overall
2799 message, as for INPUT fields. The <em>TAB</em> key will move
2800 you down beyond the bottom of the TEXTAREA field, and
2801 <em>Back Tab</em> (if available, e.g., as Shift-Tab, and
2802 correctly mapped in the terminal description) will move
2803 backward to a link or field before the TEXTAREA.</p>
2804 </dd>
2805
2806 <dt>Editing TEXTAREA Fields and Special TEXTAREA Functions</dt>
2807
2808 <dd>
2809 <p>TEXTAREA fields can be edited using an external editor.
2810 The statusline should tell you when this is possible and what
2811 key to use, it might for example say</p>
2812
2813 <pre>
2814 <strong>(Textarea) Enter text. </strong>[ ..... ]<strong> (^Xe for editor).</strong>
2815 </pre>
2816 <p>An external editor has to be defined, for example in the
2817 <a href="#InteractiveOptions">Options Menu</a>, before you
2818 can start using this function.</p>
2819
2820 <p>A key to invoke external TEXTAREA editing is normally
2821 provided by the <a href=
2822 "keystrokes/edit_help.html">Line-Editor Key</a> Bindings. A
2823 KEYMAP directive in <em>lynx.cfg</em> can also be used to
2824 make a different key invoke external editing; it will then
2825 normally be necessary to prefix that key with <em>^V</em> to
2826 "escape" from line-editing. Two variants exist,<br>
2827 &nbsp;&nbsp;KEYMAP:e:EDITTEXTAREA<br>
2828 or<br>
2829 &nbsp;&nbsp;KEYMAP:e:DWIMEDIT<br>
2830 (the first is only functional for TEXTAREA editing, while the
2831 second allows to use the same key for normal <a href=
2832 "#FileEdit">file editing</a> <em>as long as both functions do
2833 not conflict</em>).</p>
2834
2835 <p>Please see the <a href="#CtrlVNote">note above</a> for
2836 details about <em>^V</em> behavior.</p>
2837 You can also use two other special TEXTAREA functions. Again,
2838 these are already bound to key sequences in the <a href=
2839 "keystrokes/edit_help.html#TASpecial">Line-Editor
2840 Bindings</a>, by default <em>^Xg</em> and <em>^Xi</em>. You
2841 can use different keys by adding KEYMAP bindings to your
2842 <em>lynx.cfg</em> file, e.g.
2843 <p>&nbsp;&nbsp;KEYMAP:$:GROWTEXTAREA<br>
2844 &nbsp;&nbsp;KEYMAP:#:INSERTFILE</p>
2845
2846 <p>With these bindings, (in a TEXTAREA only) <em>^V$</em>
2847 would add 5 lines to the TEXTAREA and <em>^V#</em> would
2848 prompt for the name of an existing file to be inserted into
2849 the TEXTAREA (above the cursorline). An automatic variation
2850 of GROWTEXTAREA is normally compiled in, so that hitting
2851 <em>Enter</em> with the cursor on the last line adds a new
2852 line to the TEXTAREA, with the cursor on it.</p>
2853
2854 <p>If you have some single keys (or control keys) to spare
2855 that you do not need for their normal purposes, you can
2856 dedicate those keys to invoke the special functions (without
2857 requiring a prefix key). For example, to use the <em>^E</em>
2858 key for the DWIMEDIT action, and the <em>Insert</em> key for
2859 the INSERTFILE action, use<br>
2860 &nbsp;&nbsp;KEYMAP:^E:DWIMEDIT:PASS<br>
2861 &nbsp;&nbsp;KEYMAP:0x10C:INSERTFILE:PASS<br>
2862 (see lynx.cfg for other keystroke codes to use).</p>
2863
2864 <p>Note that the default bindings that use <em>^X</em> as a
2865 prefix key <em>may</em> also work by substituting the
2866 <kbd>Escape</kbd> key for ^X. If your keyboard has a modifier
2867 (Meta) key that gets transmitted as an ESC prefix, for
2868 example <kbd>Alt</kbd>, you can then even use <em>Alt-e</em>
2869 instead of <em>^Xe</em>, <em>Alt-g</em> instead of
2870 <em>^Xg</em>, and so on. But this does not work reliably
2871 everywhere (it depends on the way Lynx is compiled, including
2872 which libraries are used, and behavior of the connection and
2873 terminal type).</p>
2874 </dd>
2875 </dl>
2876
2877 <p>In general, you can move around the form using the standard
2878 Lynx navigation keys. The <em>up-arrow</em> and
2879 <em>down-arrow</em> keys, respectively, select the previous or
2880 next field, box, or button. The <em>TAB</em> key selects the next
2881 field, box, or button.</p>
2882
2883 <p>To <a name="submit" id="submit"><em>submit</em></a> the form
2884 press <em>right-arrow</em> or <em>Return</em> when positioned on
2885 the form's submit button. If you've submitted the form previously
2886 during the Lynx session, have not changed any of the form
2887 content, and the METHOD was <em>GET</em>, Lynx will retrieve from
2888 its cache what was returned from the previous submission. If you
2889 wish to resubmit that form to the server with the same content as
2890 previously, use the NOCACHE command
2891 (&ldquo;<samp>x</samp>&rdquo;) when positioned on the submit
2892 button. The <em>right-arrow</em> and <em>Return</em> keys also
2893 will invoke a no-cache resubmission if the reply from a form
2894 submission included a META element with a no-cache Pragma or
2895 Cache-Control directive:</p>
2896
2897 <pre>
2898 <em>&lt;META HTTP-EQUIV="Pragma" CONTENT="no-cache"&gt;</em>
2899 <em>&lt;META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"&gt;</em>
2900 </pre>
2901 <p>or the server sent a "Pragma" or "Cache-Control" MIME header
2902 with a no-cache directive.</p>
2903
2904 <p>You also can use the DOWNLOAD (&ldquo;<samp>d</samp>&rdquo;)
2905 keystroke command when positioned on a form submit button if you
2906 wish to download the server's reply to the submission instead of
2907 having Lynx render and display it.</p>
2908
2909 <p>Forms which have <em>POST</em> as the METHOD, or a <a href=
2910 "lynx_url_support.html#mailto_url">mailto:</a> URL as the ACTION,
2911 are always resubmitted, even if the content has not changed, when
2912 you activate the <em>submit</em> button. Lynx normally will not
2913 resubmit a form which has <em>POST</em> as the METHOD if the
2914 document returned by the form has links which you activated, and
2915 then you go back via the PREV_DOC (<em>left-arrow</em>) command
2916 or via the <a href="keystrokes/history_help.html">History
2917 Page</a>. Lynx can be compiled so that it resubmits the form in
2918 those cases as well, and the default can be changed via <a href=
2919 "#lynx.cfg">lynx.cfg</a>, and toggled via the
2920 <em>-resubmit_posts</em> command line switch.</p>
2921
2922 <p>If the form has one <em>text entry</em> field and no other
2923 fields except, possibly, hidden INPUT fields not included in the
2924 display, then that field also serves as a <em>submit</em> button,
2925 and pressing <em>right-arrow</em> or <em>Return</em> on that
2926 field will invoke submission of the form. Be sure to use
2927 <em>up-arrow</em>, <em>down-arrow</em> or <em>TAB</em> to move
2928 off the text entry field, in such cases, if it is not your
2929 intention to submit the form (or to retrieve what was returned
2930 from an earlier submission if the content was not changed and the
2931 METHOD was <em>GET</em>).</p>
2932
2933 <p>Forms can have multiple <em>submit</em> buttons, if they have
2934 been assigned NAMEs in the markup. In such cases, information
2935 about which one of the buttons was used to submit the form is
2936 included in the form content.</p>
2937
2938 <p>Inlined images can be used as submit buttons in forms: If such
2939 buttons are assigned NAMEs in the markup, for graphic clients
2940 they can also serve as <a href="#USEMAP">image maps</a>, and the
2941 x,y coordinates of the graphic client's cursor position in the
2942 image when it was <em>clicked</em> are included in the form
2943 content. Since Lynx cannot inline the image, and the user could
2944 not have moved a cursor from the origin for the image, if no
2945 alternatives are made available in the markup Lynx sends a 0,0
2946 coordinate pair in the form content.</p>
2947
2948 <p>Document authors who use images as submit buttons, but have at
2949 least some concern for text clients and sight-challenged
2950 Webizens, should include VALUEs for the buttons in such markup.
2951 Lynx will then display the string assigned to the VALUE, as it
2952 would for a normal submit button.</p>
2953
2954 <ul>
2955 <li>
2956 <p>Some document authors incorrectly use an ALT instead of
2957 VALUE attribute for this purpose. Lynx "cooperates" by
2958 treating ALT as a synonym for VALUE when present in an INPUT
2959 tag with TYPE="image".</p>
2960 </li>
2961
2962 <li>
2963 <p>If neither a VALUE nor an ALT attribute is present, Lynx
2964 displays "[IMAGE]-Submit" as the string for such buttons.</p>
2965 </li>
2966
2967 <li>
2968 <p>If clickable images is set, the "[IMAGE]" portion of the
2969 string is a link for the image, and the "Submit" portion is
2970 the button for submitting the form.</p>
2971
2972 <p>Otherwise, the entire string is treated as a submit
2973 button. If a VALUE or ALT attribute is present and clickable
2974 images is set, Lynx prepends "[IMAGE]" as a link for the
2975 image, followed by &ldquo;-&rdquo; and then the attribute's
2976 value as the displayed string for the submit button.</p>
2977 </li>
2978 </ul>
2979
2980 <p>Early versions of Lynx would send a name=value pair instead of
2981 a 0,0 coordinate pair if a TYPE="image" submit button was
2982 NAME-ed, had a VALUE attribute in the INPUT tag, and was used to
2983 submit the form. The script which analyzes the form content thus
2984 could be made aware whether the submission was by a user with a
2985 graphic client and had image loading turned on, or by a user who
2986 did not see the image nor make a conscious choice within it.
2987 However, requests that this be included in HTML specifications
2988 consistently have fallen on deaf ears, and thus Lynx now "fakes"
2989 a 0,0 coordinate pair whether or not a VALUE or ALT attribute is
2990 present in the INPUT tag. Ideally, the script which analyzes the
2991 submitted content will treat the 0,0 coordinate pair as an
2992 indicator that the user did not see the image and make a
2993 conscious choice within it.</p>
2994
2995 <p>Forms can have <em>hidden</em> INPUT fields, which are not
2996 displayed, but have NAMEs and VALUEs included in the content.
2997 These often are used to keep track of information across a series
2998 of related form submissions, but have the potential for including
2999 information about the user that might be considered to represent
3000 an invasion of privacy. NOTE, in this regard, that Lynx has
3001 implemented the <a href="http://www.w3.org/Markup/html3/">HTML
3002 3.0</a> <em>DISABLED</em> attribute for <em>all</em> of its form
3003 fields. These can be used to keep track of information across
3004 submissions, and to cast it unmodifiable in the current form, but
3005 keep the user aware that it will be included in the
3006 submission.</p>
3007
3008 <p>Forms most commonly are submitted to http servers with the
3009 content encoded as
3010 <em>ENCTYPE="application/x-www-form-urlencoded"</em> for analysis
3011 by a script, and Lynx treats that as the default if no ENCTYPE is
3012 specified in the FORM start tag. However, you can specify a
3013 <a href="lynx_url_support.html#mailto_url">mailto</a> URL as the
3014 form's ACTION to have the form content sent, instead, to an email
3015 address. In such cases, you may wish to specify
3016 <em>ENCTYPE="text/plain"</em> in the form markup, so that the
3017 content will not be encoded, but remain readable as plain
3018 text.</p>
3019
3020 <p>Lynx also supports
3021 <em>ENCTYPE="application/sgml-form-urlencoded"</em> for which all
3022 reserved characters in the content will be hex escaped, as with
3023 <em>application/x-www-form-urlencoded</em>, but semicolons
3024 (&ldquo;<samp>;</samp>&rdquo;) instead of ampersands
3025 (&ldquo;<samp>&amp;</samp>&rdquo;) will be used as the separator
3026 for name=value pairs in the form content. The use of semicolons
3027 is preferred for forms with the <em>GET</em> METHOD, because the
3028 <em>GET</em> METHOD causes the encoded form content to be
3029 appended as a <em>?searchpart</em> for the form's ACTION, and if
3030 such URLs are used in <em>text/html</em> documents or bookmark
3031 files without conversion of the ampersands to SGML character
3032 references (<em>&amp;amp;</em> or <em>&amp;#38;</em>), their
3033 being followed by form field NAMEs which might correspond to SGML
3034 entities could lead to corruption of the intended URL.</p>
3035
3036 <p>NOTE, in this regard, that Lynx converts ampersands to
3037 <em>&amp;amp;</em> when creating bookmarks, and thus the bookmark
3038 links will not be vulnerable to such corruptions. Also NOTE that
3039 Lynx allows you to save links in your bookmark file for documents
3040 returned by forms with the <em>GET</em> METHOD, and which thus
3041 have the content appended as a <em>?searchpart</em>, but not if
3042 the METHOD was <em>POST</em>, because the content would be lost
3043 and the link thus would be invalid.</p>
3044
3045 <p>Lynx supports <em>ENCTYPE="multipart/form-data"</em> for
3046 sending form content with name=value pairs encoded as multipart
3047 sections with individual MIME headers and boundaries. However,
3048 Lynx does not yet support INPUTs with <em>TYPE="file"</em> or
3049 <em>TYPE="range"</em> and will set the <em>DISABLED</em>
3050 attribute for all of the form's fields if any INPUTs with either
3051 of those two TYPEs are present, so that the form cannot be
3052 submitted. Otherwise, Lynx will submit the form with the
3053 multipart ENCTYPE.</p>
3054
3055 <p>A
3056 <em>Content-Disposition:&nbsp;file;&nbsp;filename=name.suffix</em>
3057 header can be used by CGI scripts to set the suggested filename
3058 offered by Lynx for &ldquo;<samp>d</samp>&rdquo;ownload and
3059 &ldquo;<samp>p</samp>&rdquo;rint menu options to save or mail the
3060 body returned by the script following submission of a FORM.
3061 Otherwise, Lynx uses the last symbolic element in the path for
3062 the FORM's ACTION, which is normally the script, itself, or a
3063 PATH_INFO field, and thus might be misleading. This also can be
3064 done via a META element in any document:</p>
3065
3066 <pre>
3067 <em>&lt;META HTTP-EQUIV="Content-Disposition"
3068 CONTENT="file; filename=name.suffix"&gt;</em>
3069 </pre>
3070 <p>[<a href="#ToC-Forms">ToC</a>]</p>
3071
3072 <h2 id="id-Images"><a name="Images" id="Images">Lynx and HTML
3073 Images</a></h2>
3074
3075 <p>As a text browser, Lynx does not display images as such -- you
3076 need to define a viewer in <em>lynx.cfg</em>: see there -- , but
3077 users can choose a number of ways of showing their presence.</p>
3078
3079 <p>There are 3 choices in <em>lynx.cfg</em>, with 2 corresponding
3080 keys:</p>
3081
3082 <pre>
3083 MAKE_LINKS_FOR_ALL_IMAGES * IMAGE_TOGGLE
3084 MAKE_PSEUDO_ALTS_FOR_INLINES [ INLINE_TOGGLE
3085 VERBOSE_IMAGES no corresponding key
3086 </pre>
3087 <p>You can also use the <em>Options Menu</em>, as outlined
3088 below:</p>
3089
3090 <pre>
3091 key lynx.cfg FM KM .lynxrc variable in source
3092
3093 * MAKE_LINKS_ Y N N clickable_images
3094 [ MAKE_PSEUDO_ Y N N pseudo_inline_alts
3095 VERBOSE_ Y Y Y verbose_img
3096
3097 FM = Form-based Menu ; KM = Key-based Menu ;
3098 in .lynxrc , VERBOSE_IMAGES is called &ldquo;verbose_images&rdquo;:
3099 the other two cannot be saved between sessions.
3100 </pre>
3101 <p>In the Form-based Menu, the 3-way &ldquo;Show images&rdquo;
3102 selection combines the effects of the &ldquo;*&rdquo; &amp;
3103 &ldquo;[&rdquo; keys, as follows:</p>
3104
3105 <pre>
3106 Ignore clickable_images = FALSE, pseudo_inline_alts = FALSE
3107 As labels clickable_images = FALSE, pseudo_inline_alts = TRUE
3108 As links clickable_images = TRUE, pseudo_inline_alts = unchanged
3109 </pre>
3110 <h2 id="id-Tables"><a name="Tables" id="Tables">Lynx and HTML
3111 Tables</a></h2>
3112
3113 <p>HTML includes markup for creating <em>tables</em> structured
3114 as arrays of cells aligned by columns and rows on the displayed
3115 page.</p>
3116
3117 <p>Lynx recognizes the TABLE element and all of its associated
3118 elements as described in <a href=
3119 "http://www.faqs.org/rfcs/rfc1942.html">RFC 1942</a> and will
3120 process any ID attributes in the start tags for handling as
3121 NAME-ed anchors, but does not create actual <em>tables</em>.
3122 Instead, it treats the TR start tag as a collapsible BR (line
3123 break), and inserts a collapsible space before the content of
3124 each TH and TD start tag. This generally makes all of the content
3125 of the <em>table</em> readable, preserves most of the intra-cell
3126 organization, and makes all of the links in the <em>table</em>
3127 accessible, but any information critically dependent on the
3128 column and row alignments intended for the <em>table</em> will be
3129 missed.</p>
3130
3131 <p>If inherently tabular data must be presented with Lynx, one
3132 can use PRE formatted content, or, if the <em>table</em> includes
3133 markup not allowed for PRE content, construct the <em>table</em>
3134 using <a href="#Tabs">HTML Tabs</a>. An example <em>table</em>
3135 using <em>TAB</em> elements is included in the test subdirectory
3136 of the Lynx distribution.</p>
3137
3138 <div id="TRST">
3139 <p>Starting with version 2.8.3, Lynx renders some tables in
3140 tabular form. This tabular representation for <em>simple</em>
3141 tables (<dfn>TRST</dfn>) does not attempt to implement full
3142 support for any table model. Limitations are:</p>
3143
3144 <ul>
3145 <li>All data constituting a table row generally has to fit
3146 within the display width without inserting line breaks.</li>
3147
3148 <li>Cell contents have to be simple. In general, only inline
3149 markup is acceptable, no <code>&lt;P&gt;</code>,
3150 <code>&lt;BR&gt;</code> etc. (although
3151 <code>&lt;BR&gt;</code> may be ignored at the beginning of
3152 the first cell or at the end of the last cell of a row).</li>
3153
3154 <li>When tables are nested, only the innermost level is a
3155 candidate for tabular representation.</li>
3156
3157 <li>Most attributes are ignored, including borders,
3158 <code>WIDTH</code>, vertical alignment.</li>
3159 </ul>
3160
3161 <p>Horizontal alignments (<code>LEFT</code>,
3162 <code>CENTER</code>, <code>RIGHT</code>), <code>COLSPAN</code>,
3163 and <code>ROWSPAN</code> are interpreted according to HTML
3164 4.01. (<code>ROWSPAN</code> can only reserve empty space in
3165 subsequent rows, because of the limitations above.) When TRST
3166 fails because a table is not "simple" enough, the
3167 representation falls back to the minimal handling described
3168 earlier. Many (but, unfortunately, by no means all) tables that
3169 represent inherently tabular material will thus be shown with
3170 correct tabular formatting. Where table markup is used only for
3171 layout purposes (containing whole blocks of text and list
3172 within table cells) and not essential for understanding the
3173 textual contents, it remains basically ignored. Some more
3174 information on details is available in the file
3175 <kbd>README.TRST</kbd> of the source distribution.</p>
3176 </div>
3177
3178 <p>For tabular display of more complex tables, Lynx users can
3179 make use of external scripts or programs. The normal Lynx
3180 distribution currently does not provide such scripts, but they
3181 can be written locally or downloaded from several sources. It is
3182 suggested to use one of Lynx's facilities for invoking external
3183 programs (see <kbd>DOWNLOADER</kbd>, <kbd>PRINTER</kbd>,
3184 <kbd>EXTERNAL</kbd>, <kbd>TRUSTED_LYNXCGI</kbd> in <a href=
3185 "#lynx.cfg">lynx.cfg</a> and <a href=
3186 "lynx_url_support.html#cgi_url"><code>lynxcgi:</code></a> in
3187 <em>Supported URLs</em> for information on various ways for
3188 setting this up).</p>
3189
3190 <p>[<a href="#ToC-Tables">ToC</a>]</p>
3191
3192 <h2 id="id-Tabs"><a name="Tabs" id="Tabs">Lynx and HTML Tabs</a></h2>
3193
3194 <p>Lynx implements the <a href=
3195 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> TAB
3196 element only when LEFT alignment is in effect. If the alignment
3197 is CENTER or RIGHT (JUSTIFY is not yet implemented in Lynx, and
3198 is treated as a synonym for LEFT), or if the TAB element
3199 indicates a position to the left of the current position on the
3200 screen, it is treated as a collapsible space. For purposes of
3201 implementing TAB, Lynx treats <em>en</em> units as half a
3202 character cell width when specified by the INDENT attribute, and
3203 rounds up for odd values (e.g., a value of either 5 or 6 will be
3204 treated as three spaces, each the width of a character cell). See
3205 the example <em>table</em> using TAB elements in the test
3206 subdirectory of the Lynx distribution as a model for using this
3207 functionality.</p>
3208
3209 <p>Note that this <em>Users Guide</em> and the <a href=
3210 "lynx_url_support.html">Supported URLs</a> page include TAB
3211 markup in a manner which <em>degrades gracefully</em> for WWW
3212 browsers which do not support it. Toggle to display of <a href=
3213 "#LocalSource">source</a> and <a href="#Search">search</a> for
3214 <em>&lt;tab</em> to examine the use of TAB markup in these
3215 documents.</p>
3216
3217 <p>[<a href="#ToC-Tabs">ToC</a>]</p>
3218
3219 <h2 id="id-Frames"><a name="Frames" id="Frames">Lynx and HTML
3220 Frames</a></h2>
3221
3222 <p>Some implementations of HTML include markup, primarily
3223 designed for graphic clients, that is intended to create an array
3224 of simultaneously displayed, independently scrolling windows.
3225 Such windows have been termed <em>frames</em>.</p>
3226
3227 <p>Lynx recognizes the Netscape and Microsoft Explorer FRAME,
3228 FRAMESET, and NOFRAMES elements, but is not capable of windowing
3229 to create the intended positioning of <em>frames</em>. Instead,
3230 Lynx creates labeled links to the <em>frame</em> sources,
3231 typically positioned in the upper left corner of the display, and
3232 renders the NOFRAMES section. If the document provider has
3233 disregard for text clients and sight-challenged Webizens, and
3234 thus does not include substantive content in the NOFRAMES section
3235 or a link in it to a document suitable for text clients, you can
3236 usually guess from the labeling of the <em>frame</em> links which
3237 one has the substantive material (if there is any), or you can
3238 try each of those links to see if anything worthwhile is
3239 returned.</p>
3240
3241 <p>[<a href="#ToC-Frames">ToC</a>]</p>
3242
3243 <p>Some sites -- in ignorance of Lynx capabilities -- may tell
3244 you (for example) "to view this page you need Netscape
3245 Navigator". You can simply ignore such warnings and access the
3246 frames via the Lynx-generated links as above.</p>
3247
3248 <h2 id="id-Banners"><a name="Banners" id="Banners">Lynx and HTML
3249 Banners</a></h2>
3250
3251 <p>Some implementations of HTML markup include provisions for
3252 creating a non-scrolling window to be positioned at the top of
3253 each page, containing links with brief, descriptive link names,
3254 analogous to a Windows toolbar. Such windows have been termed
3255 <em>banners</em>.</p>
3256
3257 <p>Lynx recognizes and processes all of the <a href=
3258 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> REL
3259 attribute tokens in LINK elements for creating a <em>banner</em>,
3260 and a number of others which have subsequently been proposed.
3261 These <em>banner</em> tokens are</p>
3262
3263 <blockquote>
3264 <p><em>Home</em>, <em>ToC</em>, <em>Contents</em>,
3265 <em>Index</em>, <em>Glossary</em>, <em>Copyright</em>,
3266 <em>Up</em>, <em>Next</em>, <em>Previous</em>, <em>Prev</em>,
3267 <em>Help</em>, <em>Search</em>, <em>Top</em>, <em>Origin</em>,
3268 <em>Navigator</em>, <em>Child</em>, <em>Disclaimer</em>,
3269 <em>Sibling</em>, <em>Parent</em>, <em>Author</em>,
3270 <em>Editor</em>, <em>Publisher</em>, <em>Trademark</em>,
3271 <em>Meta</em>, <em>URC</em>, <em>Hotlist</em>, <em>Begin</em>,
3272 <em>First</em>, <em>End</em>, <em>Last</em>, <em>Pointer</em>,
3273 <em>Translation</em>, <em>Definition</em>, <em>Chapter</em>,
3274 <em>Section</em>, <em>Subsection</em>, <em>Alternate</em>,
3275 <em>Documentation</em>, <em>Biblioentry</em>,
3276 <em>Bibliography</em>, <em>Start</em>, <em>Appendix</em>,
3277 <em>Bookmark</em> and <em>Banner</em>.</p>
3278 </blockquote>
3279
3280 <p>Any LINK elements with those tokens as the REL attribute
3281 value, and an HREF attribute value in the LINK, will invoke
3282 creation of a <em>banner</em> at the top of the first page, with
3283 the element's HREF as the link, and the token as the default link
3284 name. If a TITLE attribute is included in the LINK, its value
3285 will be used as the link name instead of the default.
3286 <em>Bookmark</em> and <em>Banner</em> are intended to be
3287 accompanied by a TITLE attribute, which in effect makes the
3288 namespace for REL <em>banner</em> tokens infinite.</p>
3289
3290 <p>If the special token <em>Help</em> is used as the REL value
3291 and no HREF is included in the LINK, Lynx will use its own
3292 <em>HELPFILE</em> URL for that link. For the special token
3293 <em>Home</em> without an HREF, Lynx will use the default
3294 <em>STARTFILE</em> (i.e., derived from the configuration files or
3295 the WWW_HOME environment variable, <em>not</em> the command line
3296 <em>startfile</em> if one was used). However, if a
3297 <em>-homepage=URL</em> was specified on the command line, its URL
3298 will be used as the HREF. For the special token <em>Index</em>
3299 without an HREF, Lynx will use the <em>DEFAULT_INDEX_FILE</em>
3300 derived from the configuration files, or if an
3301 <em>-index=URL</em> was specified on the command line, its URL
3302 will be used as the HREF.</p>
3303
3304 <p>Lynx does not waste screen real estate maintaining the
3305 <em>banner</em> at the top of every page, but the Lynx TOOLBAR
3306 keystroke command (&ldquo;<samp>#</samp>&rdquo;) will, any time
3307 it is pressed, position you on the <em>banner</em> so that any of
3308 its links can be activated, and pressing the <em>left-arrow</em>
3309 when in the <em>banner</em> will return you to where you were in
3310 the current document. The toolbar is indicated by a
3311 &ldquo;<samp>#</samp>&rdquo; preceding its first link when
3312 present on the screen, that is, when the first page of the
3313 document is being displayed. The availability of a toolbar is
3314 indicated by a &ldquo;<samp>#</samp>&rdquo; at the top, left-hand
3315 corner of the screen when the second or subsequent pages of the
3316 document are being displayed.</p>
3317
3318 <p>Lynx also recognizes the <a href=
3319 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a>
3320 BANNER container element, and will create a <em>banner</em> based
3321 on its content if one has not already been created based on LINK
3322 elements. Lynx treats the Microsoft MARQUEE element as a synonym
3323 for BANNER (i.e., presenting its markup as a static
3324 <em>banner</em>, without any horizontal scrolling of its
3325 content). Lynx does not prefix the BANNER or MARQUEE content with
3326 a &ldquo;<samp>#</samp>&rdquo; because the content need not be
3327 only a series of links with brief, descriptive link names, but
3328 does add a &ldquo;<samp>#</samp>&rdquo; at the top, left-hand
3329 corner of the screen when the content is not being displayed, to
3330 indicate its accessibility via the TOOLBAR keystroke command.</p>
3331
3332 <p>[<a href="#ToC-Banners">ToC</a>]</p>
3333
3334 <h2 id="id-Footnotes"><a name="Footnotes" id="Footnotes">Lynx and
3335 HTML Footnotes</a></h2>
3336
3337 <p>Lynx implements the <a href=
3338 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FN
3339 element similarly to a named <em>A</em>nchor within the current
3340 document, and assumes that the footnotes will be positioned at
3341 the bottom of the document. However, in contrast to named
3342 <em>A</em>nchors, the FN container element is treated as a block
3343 (i.e., as if a new paragraph were indicated whether or not that
3344 is indicated in its content) with greater than normal left and
3345 right margins, and the block will begin with a <em>FOOTNOTE:</em>
3346 label. For example, if the document contains:</p>
3347
3348 <pre>
3349 See the <em>&lt;A HREF="#fn1"&gt;</em><a href=
3350 "#an1">footnote</a><em>&lt;/A&gt;</em>.
3351 </pre>
3352 <p>activating that link will take you to the labeled rendering
3353 of:</p>
3354
3355 <pre>
3356 <em>&lt;FN ID="fn1"&gt;</em>&lt;p&gt;<a name="an1" id=
3357 "an1">Lynx does not use popups for FN blocks.</a>&lt;/p&gt;<em>&lt;/FN&gt;</em>
3358 </pre>
3359 <p>i.e., position it at the top of the page. Then, upon reading
3360 the footnote, you can return to your previous position in the
3361 document by pressing the <em>left-arrow</em> key. The content of
3362 an FN element can be any HTML markup that is valid in the BODY of
3363 the document.</p>
3364
3365 <p>[<a href="#ToC-Footnotes">ToC</a>]</p>
3366
3367 <h2 id="id-Notes"><a name="Notes" id="Notes">Lynx and HTML
3368 Notes</a></h2>
3369
3370 <p>Lynx implements the <a href=
3371 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> NOTE
3372 element (<em>Admonishment</em>) as a labeled block, i.e., as if a
3373 new paragraph were indicated whether or not paragraphing markup
3374 is included in its content, with greater than normal left and
3375 right margins, and with the type of note indicated by an
3376 emphasized label based on the value of its CLASS or ROLE
3377 attribute. If no CLASS or ROLE attribute is included, the default
3378 label <em>NOTE:</em> will be used. Lynx recognizes the values
3379 <em>caution</em> and <em>warning</em>, for which, respectively,
3380 the labels <em>CAUTION:</em> or <em>WARNING:</em> will be used.
3381 The NOTE element can have an ID attribute, which will be treated
3382 as a named <em>A</em>nchor, as for <a href="#Footnotes">HTML
3383 Footnotes</a>, but the NOTE block need not be placed at the
3384 bottom of the document. The content of a NOTE block can be any
3385 HTML markup that is valid in the BODY of the document. This is an
3386 example:</p>
3387
3388 <pre>
3389 <em>&lt;NOTE CLASS="warning" ID="too-bad"&gt;
3390 &lt;p&gt;The W3C vendors did not retain NOTE in the HTML 3.2 draft.&lt;/p&gt;
3391 &lt;/NOTE&gt;</em>
3392 </pre>
3393 <p>It will <em>degrade gracefully</em> for WWW browsers which do
3394 not support NOTE, except for recognition of the ID attribute as a
3395 named <em>A</em>nchor.</p>
3396
3397 <p>[<a href="#ToC-Notes">ToC</a>]</p>
3398
3399 <h2 id="id-Lists"><a name="Lists" id="Lists">Lynx and HTML
3400 Lists</a></h2>
3401
3402 <p>Lynx implements the <a href=
3403 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> list
3404 elements UL (<em>Unordered List</em>), OL (<em>Ordered
3405 List</em>), and DL (<em>Definition List</em>), and their
3406 associated attributes, and elements (LH, LI, DT, and DD) for the
3407 most part as described in that specification. The lists can be
3408 nested, yielding progressively greater indentation, up to six
3409 levels. The <a href=
3410 "http://www.w3.org/MarkUp/html-spec/html-spec_toc.html">HTML
3411 2.0</a> MENU and DIR elements <em>both</em> are treated as
3412 synonyms for UL with the PLAIN attribute (no <em>bullets</em>,
3413 see below). Note, thus, that neither DIR nor MENU yields a series
3414 of columns with 24-character spacing. A single nesting index is
3415 maintained, so that different types of List elements can be used
3416 for different levels within the nest. Also, the <a href=
3417 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG,
3418 CAPTION and CREDIT elements are treated as valid within list
3419 blocks. They will be rendered with indentation appropriate for
3420 the current nesting depth, and the CAPTION or CREDIT elements
3421 will have a <em>CAPTION:</em> or <em>CREDIT:</em> label beginning
3422 the first line of their content. The content of any APPLET or
3423 OBJECT elements in the lists also will be indented appropriately
3424 for the current nesting depth, but those will not invoke line
3425 breaks unless indicated by their content, and it should not
3426 include markup which is inappropriate within the list.</p>
3427
3428 <p>Lynx also supports the TYPE attribute for OL elements, which
3429 can have values of <em>1</em> for Arabic numbers, <em>I</em> or
3430 <em>i</em> for uppercase or lowercase Roman numerals, or
3431 <em>A</em> or <em>a</em> for uppercase or lowercase letters, that
3432 increment for successive LI elements in the list block. The
3433 CONTINUE attribute can be used to continue the ordering from the
3434 preceding list block when the nesting depth is changed.</p>
3435
3436 <p>Lynx treats the OL attributes START and SEQNUM as synonyms for
3437 specifying the ordering value for the first LI element in the
3438 block. The values should be specified as Arabic numbers, but will
3439 be displayed as Arabic, Roman, or alphabetical depending on the
3440 TYPE for the block. The values can range from <em>-29997</em> to
3441 the system's maximum positive integer for Arabic numbers. For
3442 Roman numerals, they can range from <em>1</em> (<em>I</em> or
3443 <em>i</em>) to <em>3000</em> (<em>MMM</em> or <em>mmm.</em>). For
3444 alphabetical orders, the values can range from <em>1</em>
3445 (<em>A</em> or <em>a</em>) to <em>18278</em> (<em>ZZZ</em> or
3446 <em>zzz</em>). If the CONTINUE attribute is used, you do not need
3447 to specify a START or SEQNUM attribute to extend the ordering
3448 from a previous block, and you can include a TYPE attribute to
3449 change among Arabic, Roman, or alphabetical ordering styles, or
3450 their casing, without disrupting the sequence. If you do not
3451 include a START, SEQNUM or CONTINUE attribute, the first LI
3452 element of each OL block will default to <em>1</em>, and if you
3453 do not include a TYPE attribute, Lynx defaults to Arabic
3454 numbers.</p>
3455
3456 <p>For UL blocks without the PLAIN attribute, Lynx uses
3457 <em>*</em>, <em>+</em>, <em>o</em>, <em>#</em>, <em>@</em> and
3458 <em>-</em> as <em>bullets</em> to indicate, progressively, the
3459 depth within the six nesting levels.</p>
3460
3461 <p>Lynx treats UL, OL, DIR, and MENU blocks as having the COMPACT
3462 attribute by default, i.e., single spaces between LH and LI
3463 elements within those blocks. For DL blocks, double spacing will
3464 be used to separate the DT and DD elements unless the COMPACT
3465 attribute has been specified.</p>
3466
3467 <p>[<a href="#ToC-Lists">ToC</a>]</p>
3468
3469 <h2 id="id-Quotes"><a name="Quotes" id="Quotes">Lynx and HTML
3470 Quotes</a></h2>
3471
3472 <p>The <a href=
3473 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> and
3474 later specifications provide for two classes of quotation in HTML
3475 documents. Block quotes, designated by the BLOCKQUOTE element (or
3476 its abbreviated synonym BQ in HTML 3.0), have implied paragraph
3477 breaks preceding and following the start and end tags for the
3478 block. Character level quotes, designated by the Q element, in
3479 contrast are simply directives in the markup to insert an
3480 appropriate quotation mark.</p>
3481
3482 <p>Lynx renders block quotes with a greater than normal left and
3483 right indentation. Lynx does not support italics, and normally
3484 substitutes underlining, but does not underline block quotes so
3485 as not to obscure any explicit emphasis elements within the
3486 quotation. The BLOCKQUOTE or BQ block can include a CREDIT
3487 container element, whose content will be rendered as an implied
3488 new paragraph with a <em>CREDIT:</em> label at the beginning of
3489 its first line.</p>
3490
3491 <p>Lynx respects nested Q start and end tags, and will use ASCII
3492 double-quotes (<samp>"</samp>) versus grave accent
3493 (<samp>`</samp>) and apostrophe (<samp>'</samp>), respectively,
3494 for even versus odd depths in the nest.</p>
3495
3496 <p>Any ID attributes in BLOCKQUOTE, BQ or Q elements can be the
3497 target of a hyperlink in the form URL#id. It is treated just like
3498 the NAME in <em>A</em>nchors.</p>
3499
3500 <p>[<a href="#ToC-Quotes">ToC</a>]</p>
3501
3502 <h2 id="id-Eightbit"><a name="Eightbit" id="Eightbit">Lynx and
3503 HTML Internationalization: 8bit, UNICODE, etc.</a></h2>
3504
3505 <p>Lynx has superior support for HTML 4.0/I18N
3506 internationalization issues. However, to see the characters other
3507 than 7bit properly you <em>should</em> set your <a href=
3508 "keystrokes/option_help.html#DC">display character set</a> from
3509 Option Menu and save its value, this is a Frequently Asked
3510 Question. Fine-tuning is also available from <a href=
3511 "#lynx.cfg">lynx.cfg</a></p>
3512
3513 <p>[<a href="#ToC-Eightbit">ToC</a>]</p>
3514
3515 <h2 id="id-USEMAP"><a name="USEMAP" id="USEMAP">Lynx and
3516 Client-Side-Image-Maps</a></h2>
3517
3518 <p>HTML includes markup, designed primarily for graphic clients,
3519 that treats inlined images as maps, such that areas of the image
3520 within which a mouse cursor was positioned when the mouse was
3521 <em>clicked</em> can correspond to URLs which should be
3522 retrieved. The original implementations were based on the client
3523 sending an http server the x,y coordinates associated with the
3524 <em>click</em>, for handling by a script invoked by the server,
3525 and have been termed <em>server-side-image-maps</em>. Lynx has no
3526 rational way of coping with such a procedure, and thus simply
3527 sends a 0,0 coordinate pair, which some server scripts treat as
3528 an instruction to return a document suitable for a text
3529 client.</p>
3530
3531 <p>Newer HTML markup provides bases for the client to determine
3532 the URLs associated with areas in the image map, and/or for a
3533 text client to process alternative markup and allow the user to
3534 make choices based on textual information. These have been termed
3535 <em>client-side-image-maps</em>.</p>
3536
3537 <p>Lynx recognizes and processes the MAP container element and
3538 its AREA elements, and will create a menu of links for the HREF
3539 of each AREA when the link created for the IMG element with a
3540 USEMAP attribute is activated. The menu uses the ALT attributes
3541 of the AREA elements as the link names, or, if the document's
3542 author has disregard for text clients and sight-challenged
3543 Webizens, and thus did not include ALT attributes, Lynx uses the
3544 resolved URLs pointed to by the HREF attributes as the link
3545 names. Lynx uses the TITLE attribute of the IMG element, or the
3546 TITLE attribute of the MAP, if either was present in the markup,
3547 as the title and main header of the menu. Otherwise, it uses the
3548 ALT attribute of the IMG element. If neither TITLE nor ALT
3549 attributes were present in the markup, Lynx creates and uses a
3550 <em>[USEMAP]</em> pseudo-ALT. The MAPs need not be in the same
3551 document as the IMG elements. If not in the same document, Lynx
3552 will fetch the document which contains the referenced MAP, and
3553 locate it based on its NAME or ID attribute. All MAPs encountered
3554 in documents during a Lynx session are cached, so that they need
3555 not be retrieved repeatedly when referenced in different
3556 documents.</p>
3557
3558 <p>If the IMG element also indicates a
3559 <em>server-side-image-map</em> via an ISMAP attribute, Lynx
3560 normally will create a link for that as well, using an
3561 <em>[ISMAP]</em> pseudo-ALT (followed by a hyphen to indicate its
3562 association with the <em>client-side-image-map</em>) rather than
3563 ignoring it, and will submit a 0,0 coordinate pair if that link
3564 is activated. Although, the <em>client-side-image-map</em> may be
3565 more useful for a client such as Lynx, because all of the URLs
3566 associated with the image map can be accessed, and their nature
3567 indicated via ALT attributes, Lynx-friendly sites can map 0,0
3568 such that the server returns a for-text-client document
3569 homologous to the content of FIG elements (see below). Inclusion
3570 of such a link for submissions to the server can be disabled by
3571 default via the configuration file (<a href=
3572 "#lynx.cfg">lynx.cfg</a>), and the default can be toggled via the
3573 <em>-ismap</em> command line switch.</p>
3574
3575 <p>Lynx also recognizes the <a href=
3576 "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG
3577 and OVERLAY elements, and will handle them as intended for text
3578 clients. These are the ideal way to handle
3579 <em>client-side-image-maps</em>, because the FIG content provides
3580 complete alternative markup, rather than relying on the client to
3581 construct a relatively meager list of links with link names based
3582 on ALT strings.</p>
3583
3584 <p>The presently experimental OBJECT element encompasses much of
3585 the functionality of the FIG element for
3586 <em>client-side-image-maps</em>. Lynx will render and display the
3587 content of OBJECT elements which have the SHAPES attribute
3588 equivalently to its handling of FIG. Lynx also handles OBJECT
3589 elements with the USEMAP and/or ISMAP attributes equivalently to
3590 its handling of IMG elements with <em>client-side-image-maps</em>
3591 and/or <em>server-side-image-maps</em>.</p>
3592
3593 <p>[<a href="#ToC-USEMAP">ToC</a>]</p>
3594
3595 <h2 id="id-Refresh"><a name="Refresh" id="Refresh">Lynx and
3596 Client-Side-Pull</a></h2>
3597
3598 <p>HTML includes provision for passing instructions to clients
3599 via directives in META elements, and one such instruction, via
3600 the token <em>Refresh</em>, should invoke reloading of the
3601 document, fetched from a server with the same URL or a new URL,
3602 at a specified number of seconds following receipt of the current
3603 document. This procedure has been termed
3604 <em>client-side-pull</em>. An example of such an element is:</p>
3605
3606 <pre>
3607 <em>&lt;META HTTP-EQUIV="Refresh" CONTENT="3; URL=http://host/path"&gt;</em>
3608 </pre>
3609 <p>which instructs a client to fetch the indicated URL in 3
3610 seconds after receiving the current document. If the
3611 <em>URL=</em> field is omitted, the URL defaults to that of the
3612 current document. A <em>no-cache</em> directive is implied when
3613 the <em>Refresh</em> is for the same URL.</p>
3614
3615 <p>Lynx recognizes and processes <em>Refresh</em> directives in
3616 META elements, but puts up a labeled link, typically in the upper
3617 left corner of the display, indicating the number of seconds
3618 intended before a refresh, and the URL for the refresh, instead
3619 of making the request automatically after the indicated number of
3620 seconds. This allows people using a braille interface any amount
3621 of time to examine the current document before activating the
3622 link for the next URL. In general, if the number of seconds
3623 indicated is short, the timing is not critical and you can
3624 activate the link whenever you like. If it is long (e.g., 60
3625 seconds), a server process may be generating new documents or
3626 images at that interval, and you would be wasting bandwidth by
3627 activating the link at a shorter interval.</p>
3628
3629 <p>[<a href="#ToC-Refresh">ToC</a>]</p>
3630
3631 <h2 id="id-Cookies"><a name="Cookies" id="Cookies">Lynx State
3632 Management</a> (Me want <em>cookie</em>!)</h2>
3633
3634 <p>HTTP provides a means to carry state information across
3635 successive connections between a browser and an http server.
3636 Normally, http servers respond to each browser request without
3637 relating that request to previous or subsequent requests. Though
3638 the inclusion of INPUT fields with TYPE="hidden" can be used as a
3639 sort of state management by <a href="#Forms">HTML Forms</a>, a
3640 more general approach involves exchanges of MIME headers between
3641 the server and browser. When replying to a request, the server
3642 can send a <em>Set-Cookie</em> MIME header which contains
3643 information (<em>cookies</em>) relevant to the browser's request,
3644 and in subsequent requests the browser can send a <em>Cookie</em>
3645 MIME header with information derived from previously received
3646 cookies.</p>
3647
3648 <p>State Management via cookie exchanges originally was
3649 implemented by Netscape, and such cookies are now designated as
3650 <em>Version 0</em>. A more elaborate format for cookies,
3651 designated as <em>Version 1</em>, was standardized by the IETF
3652 (Internet Engineering Task Force) as <a href=
3653 "https://www.ietf.org/rfc/rfc2109.txt">RFC&nbsp;2109</a>. Lynx
3654 supports both <em>Version 0</em> and <em>Version 1</em> cookie
3655 exchanges. This support can be disabled by default via the
3656 SET_COOKIES symbol in the compilation (<em>userdefs.h</em>)
3657 and/or run time (<a href="#lynx.cfg">lynx.cfg</a>) configuration
3658 files, and that default setting can be toggled via the
3659 <em>-cookies</em> command line switch. The SET_COOKIES symbol can
3660 be further modified by the ACCEPT_ALL_COOKIES mode. If
3661 ACCEPT_ALL_COOKIES is TRUE, and SET_COOKIES is TRUE, Lynx will
3662 accept all cookies. Additionally, the cookies that are
3663 automatically accepted or rejected by Lynx can be further
3664 modified with the COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS
3665 options in your .lynxrc file, each of which is a comma-separated
3666 list of domains to perform the desired action. The domain listed
3667 in these options must be identical to the domain the cookie comes
3668 from, there is no wildcard matching. If a domain is specific in
3669 both COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS, rejection
3670 will take precedence.</p>
3671
3672 <p>When cookie support is enabled, <em>Set-Cookie</em> MIME
3673 headers received from an http server invoke confirmation prompts
3674 with possible replies of &ldquo;<samp>Y</samp>&rdquo;es or
3675 &ldquo;<samp>N</samp>&rdquo;o for acceptance of the cookie,
3676 &ldquo;<samp>A</samp>&rdquo;lways to accept the cookie and to
3677 allow all subsequent cookies from that <em>domain</em> (server's
3678 Fully Qualified Domain Name, or site-identifying portion of the
3679 FQDN) without further confirmation prompts, or
3680 ne&ldquo;<strong>V</strong>&rdquo;er to never allow cookies from
3681 that <em>domain</em> to be accepted (silently ignore its
3682 <em>Set-Cookie</em> MIME headers). All unexpired cookies are held
3683 in a hypothetical <em>Cookie Jar</em> which can be examined via
3684 the COOKIE_JAR keystroke command, normally mapped to
3685 <em>Ctrl-K</em>, for invoking the <a href=
3686 "keystrokes/cookie_help.html">Cookie Jar Page</a>. If Lynx has
3687 been compiled with the --enable-persistent-cookies flag, then
3688 unexpired cookies will be stored between sessions in the filename
3689 set with the COOKIE_FILE option in your .lynxrc.</p>
3690
3691 <p>A common use of cookies by http servers is simply to track the
3692 documents visited by individual users. Though this can be useful
3693 to the site's WebMaster for evaluating and improving the
3694 organization of links in the various documents of the site, if
3695 the user has configured Lynx to include a <em>From</em> MIME
3696 header with the user's email address in http requests, or has
3697 passed personal information to the server via a form submission,
3698 the tracking might be used to draw inferences, possibly
3699 incorrect, about that user, and may be considered by some as an
3700 invasion of privacy.</p>
3701
3702 <p>An example of worthwhile State Management via cookies is the
3703 setting of personal preferences, typically via a form submission
3704 to the site, which will then apply to all documents visited at
3705 that site.</p>
3706
3707 <p>If you accept cookies when accessing a site, but are given no
3708 indication about how they will be used in subsequent requests to
3709 that site, nor can infer how they will be used, you can
3710 <em>Gobble</em> (delete) the cookies and/or change the
3711 &ldquo;allow&rdquo; setting for its <em>domain</em> via the
3712 <a href="keystrokes/cookie_help.html">Cookie Jar Page</a>.</p>
3713
3714 <p>[<a href="#ToC-Cookies">ToC</a>]</p>
3715
3716 <h2 id="id-Cache"><a name="Cache" id="Cache">Cached Documents</a></h2>
3717
3718 <p>A list of documents which are in lynx's internal cache is
3719 accessible through hypothetical <em>Cache Jar</em> which can be
3720 examined via the CACHE_JAR keystroke command, normally mapped to
3721 <em>Ctrl-X</em>.</p>
3722
3723 <p>Entries in the <em>Cache Jar</em> are ordered from oldest (at
3724 the top) to newest. The user can easily access any document which
3725 is in the cache, especially those which may be soon removed due
3726 to configurable limits on the maximum number of cached documents,
3727 as well as the maximum amount of memory used by the cache.</p>
3728
3729 <p>The structure of <em>Cache Jar</em> is simple:</p>
3730
3731 <ul>
3732 <li>Each entry starts with its ordinal number (within the
3733 session), recently added documents in cache have a smaller
3734 number than documents which are added before, and are
3735 positioned at the end of <em>Cache Jar</em></li>
3736
3737 <li>Following its ordinal number is the document title, which
3738 is also a link. On activating this link, the user is prompted
3739 if they want to delete the document from <em>Cache Jar</em>.
3740 The document's address (also a link) follows the title. It is
3741 distinguished by a <code>URL:</code> label preceding the link.
3742 Activating this link, lynx displays the corresponding cached
3743 document.</li>
3744
3745 <li>Below each cached document URL lynx shows the document
3746 properties which include:
3747 <ul>
3748 <li>Lines,</li>
3749
3750 <li>Size,</li>
3751
3752 <li>File-Cache,</li>
3753
3754 <li>Content-Type,</li>
3755
3756 <li>Content-Language,</li>
3757
3758 <li>Content-Encoding,</li>
3759
3760 <li>Content-Location,</li>
3761
3762 <li>Subject,</li>
3763
3764 <li>Owner,</li>
3765
3766 <li>Date,</li>
3767
3768 <li>Expires,</li>
3769
3770 <li>Last-Modified,</li>
3771
3772 <li>ETag,</li>
3773
3774 <li>Server, and</li>
3775
3776 <li>Source-Cache-File.</li>
3777 </ul>
3778 </li>
3779 </ul>
3780
3781 <p>This feature can be enabled by default using the USE_CACHEJAR
3782 symbol in the compilation (<code>userdefs.h</code>), as well as
3783 enabled in lynx.cfg</p>
3784
3785 <p>[<a href="#ToC-Cache">ToC</a>]</p>
3786
3787 <h2 id="id-Sessions"><a name="Sessions" id=
3788 "Sessions"><em>Sessions</em></a></h2>
3789
3790 <p>Lynx's current state (all information about the user's current
3791 activity with lynx) is called a session. Sessions are useful in
3792 particular if you are in the middle of exploring something on the
3793 web and you were forced to stop abruptly, losing any trace of
3794 your current work.</p>
3795
3796 <p>A session can be automatically restored as lynx starts after a
3797 clean exit. The session data is saved if lynx is invoked with the
3798 <em>-session=FILENAME</em> switch. The <em>FILENAME</em> is the
3799 name of the file where the session will be stored.</p>
3800
3801 <p>There are also switches for only restoring:
3802 <em>-sessionin=FILENAME</em> and for only saving:
3803 <em>-sessionout=FILENAME</em> sessions:</p>
3804
3805 <p>If you do not want to specify these options at each lynx
3806 startup, there is an option in <em>lynx.cfg</em> to enable
3807 automatic saving/restoring of session. To keep lynx startup/exit
3808 reasonably fast there is also an option in <em>lynx.cfg</em>
3809 specifying how much information about the current lynx session
3810 will be stored in file.</p>
3811
3812 <p>The syntax of the session file is simple. You can use a text
3813 editor to modify, add new entries, or remove URLs you no longer
3814 want.</p>
3815
3816 <p>[<a href="#ToC-Sessions">ToC</a>]</p>
3817
3818 <h2 id="id-Invoking"><a name="Invoking" id="Invoking">The Lynx
3819 command line</a></h2>
3820
3821 <p>A summary of the Lynx command line options (switches) is
3822 returned to stdout if Lynx is invoked with the <em>-help</em>
3823 switch. A description of the options also should be available via
3824 the system man (Unix) pages or help (VMS) libraries. On Win32,
3825 typing lynx -help in a DOS window should display similarly. The
3826 basic syntax of the Lynx command line can be represented as one
3827 of the following:</p>
3828
3829 <dl>
3830 <dt><code>Command</code>
3831 </dt>
3832
3833 <dd><code>lynx [options]</code>
3834 </dd>
3835
3836 <dd><code>lynx [options] startfile</code>
3837 </dd>
3838 </dl>
3839
3840 <p>where</p>
3841
3842 <dl>
3843 <dt><code>startfile</code>
3844 </dt>
3845
3846 <dd>
3847 <p>is the file or URL that Lynx will load at start-up.</p>
3848
3849 <ul>
3850 <li>If startfile is not specified, Lynx will use a default
3851 starting file and base directory determined during
3852 installation.</li>
3853
3854 <li>If a specified file is local (i.e., not a URL) Lynx
3855 displays that file and uses the directory in which that
3856 file resides as the base directory.</li>
3857
3858 <li>If a URL is specified, the file will be retrieved, and
3859 only the server base directory will be relevant to further
3860 accesses.</li>
3861
3862 <li>If more than one local file or remote URL is listed on
3863 the command line, Lynx will open only the last
3864 interactively. All of the names (local files and remote
3865 URLs) are added to the G)oto history.</li>
3866 </ul>
3867 </dd>
3868
3869 <dt><code>options</code>
3870 </dt>
3871
3872 <dd>
3873 <p>Lynx uses only long option names. Option names can begin
3874 with double dash as well, underscores and dashes can be
3875 intermixed in option names (in the reference below options
3876 are with one dash before them and with underscores).</p>
3877
3878 <p>Lynx provides many command-line options. Some options
3879 require a value (string, number or keyword). These are noted
3880 in the reference below. The other options set boolean values
3881 in the program. There are three types of boolean options:
3882 set, unset and toggle. If no option value is given, these
3883 have the obvious meaning: set (to true), unset (to false), or
3884 toggle (between true/false). For any of these, an explicit
3885 value can be given in different forms to allow for operating
3886 system constraints, e.g.,</p>
3887
3888 <blockquote>
3889 <pre>
3890 -center:off
3891 -center=off
3892 -center-
3893 </pre>
3894 </blockquote>
3895
3896 <p>Lynx recognizes "1", "+", "on" and "true" for true values,
3897 and "0", "-", "off" and "false" for false values. Other
3898 option-values are ignored.</p>
3899
3900 <p>The default boolean, number and string option values that
3901 are compiled into lynx are displayed in the help-message
3902 provided by lynx -help. Some of those may differ according to
3903 how lynx was built; see the help message itself for these
3904 values. The -help option is processed before any option,
3905 including those that control reading from the lynx.cfg file.
3906 Therefore runtime configuration values are not reflected in
3907 the help-message.</p>
3908
3909 <p>Capitalized items in the option summary indicate that a
3910 substitution must be made. These are the options:</p>
3911
3912 <dl>
3913 <dt><code><strong>-</strong></code>
3914 </dt>
3915
3916 <dd>
3917 <p>If the argument is only
3918 &ldquo;<code><strong>-</strong></code>&rdquo; (dash),
3919 then Lynx expects to receive the arguments from stdin.
3920 This is to allow for the potentially very long command
3921 line that can be associated with the <em>-get_data</em>
3922 or <em>-post_data</em> arguments (see below). It can also
3923 be used to avoid having sensitive information in the
3924 invoking command line (which would be visible to other
3925 processes on most systems), especially when the
3926 <em>-auth</em> or <em>-pauth</em> options are used. On
3927 VMS, the dash must be encased in double-quotes ("-") and
3928 the keyboard input terminated with <em>Control-Z</em> or
3929 the command file input terminated by a line that begins
3930 with &ldquo;<samp>$</samp>&rdquo;. On Unix, the keyboard
3931 input terminator is <em>Control-D</em>. On Win32,
3932 [???].</p>
3933 </dd>
3934
3935 <dt><code><strong>-accept_all_cookies</strong></code>
3936 </dt>
3937
3938 <dd>
3939 <p>accept all cookies.</p>
3940 </dd>
3941
3942 <dt><code><strong>-anonymous</strong></code>
3943 </dt>
3944
3945 <dd>
3946 <p>apply restrictions appropriate for an anonymous
3947 account, see <em>-restrictions</em> below for some
3948 details.</p>
3949 </dd>
3950
3951 <dt>
3952 <code><strong>-assume_charset=</strong><em>MIMENAME</em></code>
3953 </dt>
3954
3955 <dd>
3956 <p>charset for documents that do not specify it.</p>
3957 </dd>
3958
3959 <dt>
3960 <code><strong>-assume_local_charset=</strong><em>MIMENAME</em></code>
3961 </dt>
3962
3963 <dd>
3964 <p>charset assumed for local files, i.e., files which
3965 lynx creates such as internal pages for the options
3966 menu.</p>
3967 </dd>
3968
3969 <dt>
3970 <code><strong>-assume_unrec_charset=</strong><em>MIMENAME</em></code>
3971 </dt>
3972
3973 <dd>
3974 <p>use this instead of unrecognized charsets.</p>
3975 </dd>
3976
3977 <dt><code><strong>-auth=</strong><em>ID:PW</em></code>
3978 </dt>
3979
3980 <dd>
3981 <p>set authorization <em>identifier</em> and
3982 <em>password</em> for protected documents at startup. Be
3983 sure to protect any script files which use this
3984 switch.</p>
3985 </dd>
3986
3987 <dt><code><strong>-base</strong></code>
3988 </dt>
3989
3990 <dd>
3991 <p>prepend a request URL comment and BASE tag to
3992 text/html outputs for -source dumps.</p>
3993 </dd>
3994
3995 <dt><code><strong>-bibp=</strong><em>URL</em></code>
3996 </dt>
3997
3998 <dd>
3999 <p>specify a local bibp server (default
4000 http://bibhost/).</p>
4001 </dd>
4002
4003 <dt><code><strong>-blink</strong></code>
4004 </dt>
4005
4006 <dd>
4007 <p>forces high intensity background colors for color
4008 mode, if available and supported by the terminal. This
4009 applies to the slang library (for a few terminal
4010 emulators), or to OS/2 EMX with ncurses.</p>
4011 </dd>
4012
4013 <dt><code><strong>-book</strong></code>
4014 </dt>
4015
4016 <dd>
4017 <p>use the bookmark page as the startfile. The default or
4018 command line startfile is still set for the Main screen
4019 command, and will be used if the bookmark page is
4020 unavailable or blank.</p>
4021 </dd>
4022
4023 <dt><code><strong>-buried_news</strong></code>
4024 </dt>
4025
4026 <dd>
4027 <p>toggles scanning of news articles for buried
4028 references, and converts them to news links. Not
4029 recommended because email addresses enclosed in angle
4030 brackets will be converted to false news links, and
4031 uuencoded messages can be trashed.</p>
4032 </dd>
4033
4034 <dt><code><strong>-cache=</strong><em>NUMBER</em></code>
4035 </dt>
4036
4037 <dd>
4038 <p>set the <em>NUMBER</em> of documents cached in memory.
4039 The default is 10.</p>
4040 </dd>
4041
4042 <dt><code><strong>-center</strong></code>
4043 </dt>
4044
4045 <dd>
4046 <p>Toggle center alignment in HTML TABLE.</p>
4047 </dd>
4048
4049 <dt><code><strong>-case</strong></code>
4050 </dt>
4051
4052 <dd>
4053 <p>enable case-sensitive string searching.</p>
4054 </dd>
4055
4056 <dt><code><strong>-cfg=</strong><em>FILENAME</em></code>
4057 </dt>
4058
4059 <dd>
4060 <p>specifies a Lynx configuration file other than the
4061 default <a href="#lynx.cfg">lynx.cfg</a>.</p>
4062 </dd>
4063
4064 <dt><code><strong>-child</strong></code>
4065 </dt>
4066
4067 <dd>
4068 <p>exit on left-arrow in startfile, and disable save to
4069 disk.</p>
4070 </dd>
4071
4072 <dt><code><strong>-child_relaxed</strong></code>
4073 </dt>
4074
4075 <dd>
4076 <p>exit on left-arrow in startfile, but allow save to
4077 disk and associated print/mail options.</p>
4078 </dd>
4079
4080 <dt>
4081 <code><strong>-cmd_log=</strong><em>FILENAME</em></code>
4082 </dt>
4083
4084 <dd>
4085 <p>write keystroke commands and related information to
4086 the specified file.</p>
4087 </dd>
4088
4089 <dt>
4090 <code><strong>-cmd_script=</strong><em>FILENAME</em></code>
4091 </dt>
4092
4093 <dd>
4094 <p>read keystroke commands from the specified file. You
4095 can use the data written using the <em>-cmd_log</em>
4096 option. Lynx will ignore other information which the
4097 command-logging may have written to the log- file. Each
4098 line of the command script contains either a comment
4099 beginning with "#", or a keyword:</p>
4100
4101 <dl>
4102 <dt><code><strong>exit</strong></code>
4103 </dt>
4104
4105 <dd>
4106 <p>causes the script to stop, and forces lynx to exit
4107 immediately.</p>
4108 </dd>
4109
4110 <dt><code><strong>key</strong></code>
4111 </dt>
4112
4113 <dd>
4114 <p>the character value, in printable form. Cursor and
4115 other special keys are given as names, e.g.,
4116 <code><strong>Down Arrow</strong></code>. Printable
4117 7-bit ASCII codes are given as-is, and hexadecimal
4118 values represent other 8-bit codes.</p>
4119 </dd>
4120
4121 <dt><code><strong>set</strong></code>
4122 </dt>
4123
4124 <dd>
4125 <p>followed by a "name=value" allows one to override
4126 values set in the lynx.cfg file.</p>
4127 </dd>
4128 </dl>
4129 </dd>
4130
4131 <dt><code><strong>-color</strong></code>
4132 </dt>
4133
4134 <dd>
4135 <p>forces color mode on. This feature is only available
4136 if Lynx is built using the slang library. The slang
4137 library will send ANSI color sequences without regard to
4138 the type of terminal which is being used.</p>
4139
4140 <p>If color support is instead provided by a
4141 color-capable curses library such as ncurses, Lynx relies
4142 completely on the terminal description to determine
4143 whether color mode is possible, and this flag is not
4144 needed and thus unavailable.</p>
4145
4146 <p>A saved <samp>show_color=always</samp> setting found
4147 in a .lynxrc file at startup has the same effect, but the
4148 setting read from .lynxrc on startup is overridden by
4149 this flag.</p>
4150 </dd>
4151
4152 <dt>
4153 <code><strong>-connect_timeout</strong>=<em>N</em></code>
4154 </dt>
4155
4156 <dd>
4157 <p>Sets the connection timeout, where <em>N</em> is given
4158 in seconds.</p>
4159 </dd>
4160
4161 <dt>
4162 <code><strong>-cookie_file=</strong><em>FILENAME</em></code>
4163 </dt>
4164
4165 <dd>
4166 <p>specifies a file to use to read cookies. If none is
4167 specified, the default value is ~/.lynx_cookies for most
4168 systems, but ~/cookies for MS-DOS.</p>
4169 </dd>
4170
4171 <dt>
4172 <code><strong>-cookie_save_file=</strong><em>FILENAME</em></code>
4173 </dt>
4174
4175 <dd>
4176 <p>specifies a file to use to store cookies. If none is
4177 specified, the value given by
4178 <code><strong>-cookie_file</strong></code> is used.</p>
4179 </dd>
4180
4181 <dt><code><strong>-cookies</strong></code>
4182 </dt>
4183
4184 <dd>
4185 <p>toggles handling of Set-Cookie headers.</p>
4186 </dd>
4187
4188 <dt><code><strong>-core</strong></code>
4189 </dt>
4190
4191 <dd>
4192 <p>toggles forced core dumps on fatal errors. (Unix
4193 only)</p>
4194 </dd>
4195
4196 <dt><code><strong>-crawl</strong></code>
4197 </dt>
4198
4199 <dd>
4200 <p>with <em>-traversal</em>, output each page to a
4201 file.</p>
4202
4203 <p>with <em>-dump</em>, format output as with
4204 <em>-traversal</em>, but to stdout.</p>
4205 </dd>
4206
4207 <dt><code><strong>-curses_pads</strong></code>
4208 </dt>
4209
4210 <dd>
4211 <p>toggles the use of curses "pad" feature which supports
4212 left/right scrolling of the display.</p>
4213 </dd>
4214
4215 <dt><code><strong>-debug_partial</strong></code>
4216 </dt>
4217
4218 <dd>
4219 <p>separate incremental display stages with MessageSecs
4220 delay</p>
4221 </dd>
4222
4223 <dt><code><strong>-display=</strong><em>DISPLAY</em></code>
4224 </dt>
4225
4226 <dd>
4227 <p>set the display variable for X rexe-ced programs.</p>
4228 </dd>
4229
4230 <dt>
4231 <code><strong>-display_charset=</strong><em>MIMEname</em></code>
4232 </dt>
4233
4234 <dd>
4235 <p>set the charset for the terminal output.</p>
4236 </dd>
4237
4238 <dt><code><strong>-dont_wrap_pre</strong></code>
4239 </dt>
4240
4241 <dd>
4242 <p>inhibit wrapping of text in &lt;pre&gt; when -dump'ing
4243 and -crawl'ing, mark wrapped lines in interactive
4244 session.</p>
4245 </dd>
4246
4247 <dt><code><strong>-dump</strong></code>
4248 </dt>
4249
4250 <dd>
4251 <p>dumps the formatted output of the default document or
4252 one specified on the command line to standard out. This
4253 can be used in the following way:</p>
4254
4255 <blockquote>
4256 <p><em>lynx -dump http://www.w3.org/</em>
4257 </p>
4258 </blockquote>
4259 </dd>
4260
4261 <dt><code><strong>-editor=</strong><em>EDITOR</em></code>
4262 </dt>
4263
4264 <dd>
4265 <p>enable external editing using the specified
4266 <em>EDITOR</em>. (vi, ed, emacs, etc.)</p>
4267 </dd>
4268
4269 <dt><code><strong>-emacskeys</strong></code>
4270 </dt>
4271
4272 <dd>
4273 <p>enable emacs-like key movement.</p>
4274 </dd>
4275
4276 <dt><code><strong>-enable_scrollback</strong></code>
4277 </dt>
4278
4279 <dd>
4280 <p>toggles behavior compatible with the scrollback keys
4281 in some communications software (may be incompatible with
4282 some curses packages).</p>
4283 </dd>
4284
4285 <dt>
4286 <code><strong>-error_file=</strong><em>FILENAME</em></code>
4287 </dt>
4288
4289 <dd>
4290 <p>the status code from the HTTP request is placed in
4291 this file.</p>
4292 </dd>
4293
4294 <dt><code><strong>-exec</strong></code>
4295 </dt>
4296
4297 <dd>
4298 <p>enable local program execution (normally not
4299 configured).</p>
4300 </dd>
4301
4302 <dt><code><strong>-fileversions</strong></code>
4303 </dt>
4304
4305 <dd>
4306 <p>include all versions of files in local VMS directory
4307 listings.</p>
4308 </dd>
4309
4310 <dt><code><strong>-find_leaks</strong></code>
4311 </dt>
4312
4313 <dd>
4314 <p>toggles the memory leak checking off. Normally this is
4315 not compiled-into your executable, but when it is, it can
4316 be disabled for a session.</p>
4317 </dd>
4318
4319 <dt><code><strong>-force_empty_hrefless_a</strong></code>
4320 </dt>
4321
4322 <dd>
4323 <p>force HREF-less &ldquo;A&rdquo; elements to be empty
4324 (close them as soon as they are seen).</p>
4325 </dd>
4326
4327 <dt><code><strong>-force_html</strong></code>
4328 </dt>
4329
4330 <dd>
4331 <p>forces the first document to be interpreted as
4332 HTML.</p>
4333 </dd>
4334
4335 <dt><code><strong>-force_secure</strong></code>
4336 </dt>
4337
4338 <dd>
4339 <p>toggles forcing of the secure flag for SSL
4340 cookies.</p>
4341 </dd>
4342
4343 <dt><code><strong>-forms_options</strong></code>
4344 </dt>
4345
4346 <dd>
4347 <p>toggles whether the Options Menu is key-based or
4348 form-based.</p>
4349 </dd>
4350
4351 <dt><code><strong>-from</strong></code>
4352 </dt>
4353
4354 <dd>
4355 <p>toggles transmissions of From headers to HTTP or HTTPS
4356 servers.</p>
4357 </dd>
4358
4359 <dt><code><strong>-ftp</strong></code>
4360 </dt>
4361
4362 <dd>
4363 <p>disable ftp access.</p>
4364 </dd>
4365
4366 <dt><code><strong>-get_data</strong></code>
4367 </dt>
4368
4369 <dd>
4370 <p>properly formatted data for a get form are read in
4371 from stdin and passed to the form. Input is terminated by
4372 a line that starts with &ldquo;---&rdquo;.</p>
4373 </dd>
4374
4375 <dt><code><strong>-head</strong></code>
4376 </dt>
4377
4378 <dd>
4379 <p>send a HEAD request for the mime headers.</p>
4380 </dd>
4381
4382 <dt><code><strong>-help</strong></code>
4383 </dt>
4384
4385 <dd>
4386 <p>print this Lynx command syntax usage message.</p>
4387 </dd>
4388
4389 <dt>
4390 <code><strong>-hiddenlinks=</strong><em>option</em></code>
4391 </dt>
4392
4393 <dd>
4394 <p>control the display of hidden links. Option values
4395 are:</p>
4396
4397 <dl>
4398 <dt><code><strong>merge</strong></code>
4399 </dt>
4400
4401 <dd>
4402 <p>hidden links show up as bracketed numbers and are
4403 numbered together with other links in the sequence of
4404 their occurrence in the document.</p>
4405 </dd>
4406
4407 <dt><code><strong>listonly</strong></code>
4408 </dt>
4409
4410 <dd>
4411 <p>hidden links are shown only on <em>L</em>ist
4412 screens and listings generated by
4413 <code><strong>-dump</strong></code> or from the
4414 <em>P</em>rint menu, but appear separately at the end
4415 of those lists. This is the default behavior.</p>
4416 </dd>
4417
4418 <dt><code><strong>ignore</strong></code>
4419 </dt>
4420
4421 <dd>
4422 <p>hidden links do not appear even in listings.</p>
4423 </dd>
4424 </dl>
4425 </dd>
4426
4427 <dt><code><strong>-historical</strong></code>
4428 </dt>
4429
4430 <dd>
4431 <p>toggles use of &ldquo;&gt;&rdquo; or
4432 &ldquo;--&gt;&rdquo; as a terminator for comments.</p>
4433 </dd>
4434
4435 <dt><code><strong>-homepage=</strong><em>URL</em></code>
4436 </dt>
4437
4438 <dd>
4439 <p>set homepage separate from start page. Will be used if
4440 a fetch of the start page fails or if it is a script
4441 which does not return a document, and as the
4442 <code><em>URL</em></code> for the
4443 &ldquo;<samp>m</samp>&rdquo;ain menu command.</p>
4444 </dd>
4445
4446 <dt><code><strong>-image_links</strong></code>
4447 </dt>
4448
4449 <dd>
4450 <p>toggles inclusion of links for all images.</p>
4451 </dd>
4452
4453 <dt><code><strong>-ismap</strong></code>
4454 </dt>
4455
4456 <dd>
4457 <p>toggles inclusion of ISMAP links when client-side MAPs
4458 are present.</p>
4459 </dd>
4460
4461 <dt><code><strong>-index=</strong><em>URL</em></code>
4462 </dt>
4463
4464 <dd>
4465 <p>set the default index file to the specified
4466 <em>URL</em></p>
4467 </dd>
4468
4469 <dt><code><strong>-justify</strong></code>
4470 </dt>
4471
4472 <dd>
4473 <p>do justification of text.</p>
4474 </dd>
4475
4476 <dt><code><strong>-link=</strong><em>NUMBER</em></code>
4477 </dt>
4478
4479 <dd>
4480 <p>starting count for lnk#.dat files produced by
4481 <em>-crawl</em>.</p>
4482 </dd>
4483
4484 <dt><code><strong>-localhost</strong></code>
4485 </dt>
4486
4487 <dd>
4488 <p>disable URLs that point to remote hosts.</p>
4489 </dd>
4490
4491 <dt><code><strong>-locexec</strong></code>
4492 </dt>
4493
4494 <dd>
4495 <p>enable local program execution from local files only
4496 (if lynx was compiled with local execution enabled).</p>
4497 </dd>
4498
4499 <dt><code><strong>-lss=</strong><em>FILENAME</em></code>
4500 </dt>
4501
4502 <dd>
4503 <p>specify filename containing color-style information.
4504 The default is lynx.lss.</p>
4505 </dd>
4506
4507 <dt><code><strong>-mime_header</strong></code>
4508 </dt>
4509
4510 <dd>
4511 <p>include mime headers and force source dump.</p>
4512 </dd>
4513
4514 <dt><code><strong>-minimal</strong></code>
4515 </dt>
4516
4517 <dd>
4518 <p>toggles minimal versus valid comment parsing. When
4519 minimal, any &ldquo;--&gt;&rdquo; serves as a terminator
4520 for a comment element. When valid, pairs of
4521 &ldquo;--&rdquo; are treated as delimiters for series of
4522 comments within the overall comment element. If
4523 historical is set, that overrides minimal or valid
4524 comment parsing.</p>
4525 </dd>
4526
4527 <dt><code><strong>-nested_tables</strong></code>
4528 </dt>
4529
4530 <dd>
4531 <p>toggles nested-tables logic (for debugging).</p>
4532 </dd>
4533
4534 <dt>
4535 <code><strong>-newschunksize=</strong><em>NUMBER</em></code>
4536 </dt>
4537
4538 <dd>
4539 <p>number of articles in chunked news listings.</p>
4540 </dd>
4541
4542 <dt>
4543 <code><strong>-newsmaxchunk=</strong><em>NUMBER</em></code>
4544 </dt>
4545
4546 <dd>
4547 <p>maximum news articles in listings before chunking.</p>
4548 </dd>
4549
4550 <dt><code><strong>-nobold</strong></code>
4551 </dt>
4552
4553 <dd>
4554 <p>disable bold video-attribute.</p>
4555 </dd>
4556
4557 <dt><code><strong>-nobrowse</strong></code>
4558 </dt>
4559
4560 <dd>
4561 <p>disable directory browsing.</p>
4562 </dd>
4563
4564 <dt><code><strong>-nocc</strong></code>
4565 </dt>
4566
4567 <dd>
4568 <p>disable Cc: prompts for self copies of mailings. Note
4569 that this does not disable any CCs which are incorporated
4570 within a mailto URL or form ACTION.</p>
4571 </dd>
4572
4573 <dt><code><strong>-nocolor</strong></code>
4574 </dt>
4575
4576 <dd>
4577 <p>force color mode off, overriding terminal capabilities
4578 and any <em>-color</em> flags, <em>COLORTERM</em>
4579 variable, and saved .lynxrc settings.</p>
4580 </dd>
4581
4582 <dt><code><strong>-noexec</strong></code>
4583 </dt>
4584
4585 <dd>
4586 <p>disable local program execution. (DEFAULT)</p>
4587 </dd>
4588
4589 <dt><code><strong>-nofilereferer</strong></code>
4590 </dt>
4591
4592 <dd>
4593 <p>disable transmissions of Referer headers for file
4594 URLs.</p>
4595 </dd>
4596
4597 <dt><code><strong>-nolist</strong></code>
4598 </dt>
4599
4600 <dd>
4601 <p>disable the link list feature in dumps.</p>
4602 </dd>
4603
4604 <dt><code><strong>-nolog</strong></code>
4605 </dt>
4606
4607 <dd>
4608 <p>disable mailing of error messages to document
4609 owners.</p>
4610 </dd>
4611
4612 <dt><code><strong>-nomargins</strong></code>
4613 </dt>
4614
4615 <dd>
4616 <p>disable left/right margins in the default style
4617 sheet.</p>
4618 </dd>
4619
4620 <dt><code><strong>-nomore</strong></code>
4621 </dt>
4622
4623 <dd>
4624 <p>disable -more- string in statusline messages.</p>
4625 </dd>
4626
4627 <dt><code><strong>-nonrestarting_sigwinch</strong></code>
4628 </dt>
4629
4630 <dd>
4631 <p>make window size change handler non-restarting. This
4632 flag is not available on all systems, Lynx needs to be
4633 compiled with HAVE_SIGACTION defined. If available, this
4634 flag <em>may</em> cause Lynx to react more immediately to
4635 window changes when run within an xterm.</p>
4636 </dd>
4637
4638 <dt><code><strong>-nopause</strong></code>
4639 </dt>
4640
4641 <dd>
4642 <p>disable forced pauses for statusline messages.</p>
4643 </dd>
4644
4645 <dt><code><strong>-noprint</strong></code>
4646 </dt>
4647
4648 <dd>
4649 <p>disable most print functions.</p>
4650 </dd>
4651
4652 <dt><code><strong>-noredir</strong></code>
4653 </dt>
4654
4655 <dd>
4656 <p>do not follow URL redirections</p>
4657 </dd>
4658
4659 <dt><code><strong>-noreferer</strong></code>
4660 </dt>
4661
4662 <dd>
4663 <p>disable transmissions of Referer headers.</p>
4664 </dd>
4665
4666 <dt><code><strong>-noreverse</strong></code>
4667 </dt>
4668
4669 <dd>
4670 <p>disable reverse video-attribute.</p>
4671 </dd>
4672
4673 <dt><code><strong>-nosocks</strong></code>
4674 </dt>
4675
4676 <dd>
4677 <p>disable SOCKS proxy usage by a SOCKSified Lynx.</p>
4678 </dd>
4679
4680 <dt><code><strong>-nostatus</strong></code>
4681 </dt>
4682
4683 <dd>
4684 <p>disable the retrieval status messages.</p>
4685 </dd>
4686
4687 <dt><code><strong>-notitle</strong></code>
4688 </dt>
4689
4690 <dd>
4691 <p>disable title and blank line from top of page.</p>
4692 </dd>
4693
4694 <dt><code><strong>-nounderline</strong></code>
4695 </dt>
4696
4697 <dd>
4698 <p>disable underline video-attribute.</p>
4699 </dd>
4700
4701 <dt><code><strong>-number_fields</strong></code>
4702 </dt>
4703
4704 <dd>
4705 <p>force numbering of links as well as form input
4706 fields.</p>
4707 </dd>
4708
4709 <dt><code><strong>-number_links</strong></code>
4710 </dt>
4711
4712 <dd>
4713 <p>force numbering of links.</p>
4714 </dd>
4715
4716 <dt><code><strong>-partial</strong></code>
4717 </dt>
4718
4719 <dd>
4720 <p>toggles displaying of partial pages while loading.</p>
4721 </dd>
4722
4723 <dt>
4724 <code><strong>-partial_thres=</strong><em>NUMBER</em></code>
4725 </dt>
4726
4727 <dd>
4728 <p>number of lines to render before repainting display
4729 with partial-display logic.</p>
4730 </dd>
4731
4732 <dt><code><strong>-pauth=</strong><em>ID:PW</em></code>
4733 </dt>
4734
4735 <dd>
4736 <p>set authorization <em>identifier</em> and
4737 <em>password</em> for a protected proxy server at
4738 startup. Be sure to protect any script files which use
4739 this switch.</p>
4740 </dd>
4741
4742 <dt><code><strong>-popup</strong></code>
4743 </dt>
4744
4745 <dd>
4746 <p>toggles handling of single-choice SELECT options via
4747 popup windows or as lists of radio buttons. The default
4748 configuration can be changed in userdefs.h or <a href=
4749 "#lynx.cfg">lynx.cfg</a>. It also can be set and saved
4750 via the &ldquo;o&rdquo;ptions menu. The command line
4751 switch toggles the default.</p>
4752 </dd>
4753
4754 <dt><code><strong>-post_data</strong></code>
4755 </dt>
4756
4757 <dd>
4758 <p>properly formatted data for a post form are read in
4759 from stdin and passed to the form. Input is terminated by
4760 a line that starts with &ldquo;---&rdquo;.</p>
4761 </dd>
4762
4763 <dt><code><strong>-preparsed</strong></code>
4764 </dt>
4765
4766 <dd>
4767 <p>show source preparsed and reformatted when used with
4768 -source or in source view (&ldquo;<samp>\</samp>&rdquo;).
4769 May be useful for debugging of broken HTML markup to
4770 visualize the difference between SortaSGML and TagSoup
4771 <a href="keystrokes/option_help.html#tagsoup">recovery
4772 modes</a>, switched by &ldquo;<samp>^V</samp>&rdquo;.</p>
4773 </dd>
4774
4775 <dt><code><strong>-prettysrc</strong></code>
4776 </dt>
4777
4778 <dd>
4779 <p>do syntax highlighting and hyperlink handling in
4780 source view.</p>
4781 </dd>
4782
4783 <dt><code><strong>-print</strong></code>
4784 </dt>
4785
4786 <dd>
4787 <p>enable print functions. (default)</p>
4788 </dd>
4789
4790 <dt><code><strong>-pseudo_inlines</strong></code>
4791 </dt>
4792
4793 <dd>
4794 <p>toggles pseudo-ALTs for inline images with no ALT
4795 string.</p>
4796 </dd>
4797
4798 <dt><code><strong>-raw</strong></code>
4799 </dt>
4800
4801 <dd>
4802 <p>toggles default setting of 8-bit character
4803 translations or CJK mode for the startup character
4804 set.</p>
4805 </dd>
4806
4807 <dt><code><strong>-realm</strong></code>
4808 </dt>
4809
4810 <dd>
4811 <p>restricts access to URLs in the starting realm.</p>
4812 </dd>
4813
4814 <dt><code><strong>-reload</strong></code>
4815 </dt>
4816
4817 <dd>
4818 <p>flushes the cache on a proxy server (only the first
4819 document affected).</p>
4820 </dd>
4821
4822 <dt><code><strong>-restrictions</strong></code>
4823 </dt>
4824
4825 <dd>
4826 <p>allows a list of services to be disabled selectively
4827 and takes the following form:</p>
4828 </dd>
4829
4830 <dd>
4831 <p><em>lynx
4832 -restrictions=[option][,option][,option]...</em>
4833 </p>
4834 </dd>
4835
4836 <dd>
4837 <p>The list of recognized options is printed if none are
4838 specified.</p>
4839
4840 <dl>
4841 <dt><strong><samp>?</samp></strong>
4842 </dt>
4843
4844 <dd>
4845 <p>if used alone, lists restrictions in effect.</p>
4846 </dd>
4847
4848 <dt><strong><samp>all</samp></strong>
4849 </dt>
4850
4851 <dd>
4852 <p>restricts all options listed below.</p>
4853 </dd>
4854
4855 <dt><strong><samp>bookmark</samp></strong>
4856 </dt>
4857
4858 <dd>
4859 <p>disallow changing the location of the bookmark
4860 file.</p>
4861 </dd>
4862
4863 <dt><strong><samp>bookmark_exec</samp></strong>
4864 </dt>
4865
4866 <dd>
4867 <p>disallow execution links via the bookmark
4868 file.</p>
4869 </dd>
4870
4871 <dt><strong><samp>change_exec_perms</samp></strong>
4872 </dt>
4873
4874 <dd>
4875 <p>disallow changing the eXecute permission on files
4876 (but still allow it for directories) when local file
4877 management is enabled.</p>
4878 </dd>
4879
4880 <dt><strong><samp>chdir</samp></strong>
4881 </dt>
4882
4883 <dd>
4884 <p>disallow command which changes Lynx's working
4885 directory.</p>
4886 </dd>
4887
4888 <dt><strong><samp>default</samp></strong>
4889 </dt>
4890
4891 <dd>
4892 <p>same as command line option <em>-anonymous</em>.
4893 Set default restrictions for anonymous users. All
4894 specific services listed are always restricted,
4895 except for: inside_telnet, outside_telnet,
4896 inside_ftp, outside_ftp, inside_rlogin,
4897 outside_rlogin, inside_news, outside_news,
4898 telnet_port, jump, mail, print, exec, and goto. The
4899 settings for these, as well as additional goto
4900 restrictions for specific URL schemes that are also
4901 applied, are derived from definitions within
4902 userdefs.h.</p>
4903
4904 <p>Note that this is the only option value that may
4905 have the effect of <em>removing</em> some
4906 restrictions, if they have been set by other options,
4907 namely for those services that <em>are</em> allowed
4908 by default according to userdefs.h. However, if the
4909 separate command line option form
4910 (<em>-anonymous</em>) is used, Lynx takes care to set
4911 the default restrictions before handling additional
4912 <em>-restrictions=</em> options (even if they precede
4913 the <em>anonymous</em> option), so that this cannot
4914 happen.</p>
4915 </dd>
4916
4917 <dt><strong><samp>dired_support</samp></strong>
4918 </dt>
4919
4920 <dd>
4921 <p>disallow local file management.</p>
4922 </dd>
4923
4924 <dt><strong><samp>disk_save</samp></strong>
4925 </dt>
4926
4927 <dd>
4928 <p>disallow saving to disk in the download and print
4929 menus.</p>
4930 </dd>
4931
4932 <dt><strong><samp>dotfiles</samp></strong>
4933 </dt>
4934
4935 <dd>
4936 <p>disallow access to, or creation of, hidden (dot)
4937 files.</p>
4938 </dd>
4939
4940 <dt><strong><samp>download</samp></strong>
4941 </dt>
4942
4943 <dd>
4944 <p>disallow some downloaders in the download menu.
4945 This does <em>not</em> imply the disk_save
4946 restriction. It also does not disable the DOWNLOAD
4947 command, and does not prevent "Download or Cancel"
4948 offers when a MIME type cannot otherwise be handled.
4949 Those are only disabled if additionally the disk_save
4950 restriction is in effect <em>and</em> no download
4951 methods are defined in a <a href="#lynx.cfg">Lynx
4952 configuration file</a> that are marked as "always
4953 ENABLED" (or, alternatively, if the -validate switch
4954 is used).</p>
4955 </dd>
4956
4957 <dt><strong><samp>editor</samp></strong>
4958 </dt>
4959
4960 <dd>
4961 <p>disallow external editing.</p>
4962 </dd>
4963
4964 <dt><strong><samp>exec</samp></strong>
4965 </dt>
4966
4967 <dd>
4968 <p>disable execution scripts.</p>
4969 </dd>
4970
4971 <dt><strong><samp>exec_frozen</samp></strong>
4972 </dt>
4973
4974 <dd>
4975 <p>disallow the user from changing the local
4976 execution option.</p>
4977 </dd>
4978
4979 <dt><strong><samp>externals</samp></strong>
4980 </dt>
4981
4982 <dd>
4983 <p>disallow some "EXTERNAL" configuration lines, if
4984 support for passing URLs to external applications
4985 (with the EXTERN_LINK or EXTERN_PAGE command) is
4986 compiled in.</p>
4987 </dd>
4988
4989 <dt><strong><samp>file_url</samp></strong>
4990 </dt>
4991
4992 <dd>
4993 <p>disallow using G)oto, served links or bookmarks
4994 for file: URLs.</p>
4995 </dd>
4996
4997 <dt><strong><samp>goto</samp></strong>
4998 </dt>
4999
5000 <dd>
5001 <p>disable the &ldquo;<samp>g</samp>&rdquo; (goto)
5002 command.</p>
5003 </dd>
5004
5005 <dt><strong><samp>inside_ftp</samp></strong>
5006 </dt>
5007
5008 <dd>
5009 <p>disallow ftps for people coming from inside your
5010 domain.</p>
5011 </dd>
5012
5013 <dt><strong><samp>inside_news</samp></strong>
5014 </dt>
5015
5016 <dd>
5017 <p>disallow USENET news reading and posting for
5018 people coming from inside you domain. This applies to
5019 "news", "nntp", "newspost", and "newsreply" URLs, but
5020 not to "snews", "snewspost", or "snewsreply" in case
5021 they are supported.</p>
5022 </dd>
5023
5024 <dt><strong><samp>inside_rlogin</samp></strong>
5025 </dt>
5026
5027 <dd>
5028 <p>disallow rlogins for people coming from inside
5029 your domain.</p>
5030 </dd>
5031
5032 <dt><strong><samp>inside_telnet</samp></strong>
5033 </dt>
5034
5035 <dd>
5036 <p>disallow telnets for people coming from inside
5037 your domain.</p>
5038 </dd>
5039
5040 <dt><strong><samp>jump</samp></strong>
5041 </dt>
5042
5043 <dd>
5044 <p>disable the &ldquo;<samp>j</samp>&rdquo; (jump)
5045 command.</p>
5046 </dd>
5047
5048 <dt><strong><samp>lynxcgi</samp></strong>
5049 </dt>
5050
5051 <dd>
5052 <p>disallow execution of Lynx CGI URLs.</p>
5053 </dd>
5054
5055 <dt><strong><samp>mail</samp></strong>
5056 </dt>
5057
5058 <dd>
5059 <p>disallow mailing feature.</p>
5060 </dd>
5061
5062 <dt><strong><samp>multibook</samp></strong>
5063 </dt>
5064
5065 <dd>
5066 <p>disallow multiple bookmarks.</p>
5067 </dd>
5068
5069 <dt><strong><samp>news_post</samp></strong>
5070 </dt>
5071
5072 <dd>
5073 <p>disallow USENET News posting,</p>
5074 </dd>
5075
5076 <dt><strong><samp>options_save</samp></strong>
5077 </dt>
5078
5079 <dd>
5080 <p>disallow saving options in .lynxrc.</p>
5081 </dd>
5082
5083 <dt><strong><samp>outside_ftp</samp></strong>
5084 </dt>
5085
5086 <dd>
5087 <p>disallow ftps for people coming from outside your
5088 domain.</p>
5089 </dd>
5090
5091 <dt><strong><samp>outside_news</samp></strong>
5092 </dt>
5093
5094 <dd>
5095 <p>disallow USENET news reading and posting for
5096 people coming from outside your domain. This applies
5097 to "news", "nntp", "newspost", and "newsreply" URLs,
5098 but not to "snews", "snewspost", or "snewsreply" in
5099 case they are supported.</p>
5100 </dd>
5101
5102 <dt><strong><samp>outside_rlogin</samp></strong>
5103 </dt>
5104
5105 <dd>
5106 <p>disallow rlogins for people coming from outside
5107 your domain.</p>
5108 </dd>
5109
5110 <dt><strong><samp>outside_telnet</samp></strong>
5111 </dt>
5112
5113 <dd>
5114 <p>disallow telnets for people coming from outside
5115 your domain.</p>
5116 </dd>
5117
5118 <dt><strong><samp>print</samp></strong>
5119 </dt>
5120
5121 <dd>
5122 <p>disallow most print options.</p>
5123 </dd>
5124
5125 <dt><strong><samp>shell</samp></strong>
5126 </dt>
5127
5128 <dd>
5129 <p>disallow shell escapes.</p>
5130 </dd>
5131
5132 <dt><strong><samp>suspend</samp></strong>
5133 </dt>
5134
5135 <dd>
5136 <p>disallow <em>Control-Z</em> suspends with escape
5137 to shell on Unix.</p>
5138 </dd>
5139
5140 <dt><strong><samp>telnet_port</samp></strong>
5141 </dt>
5142
5143 <dd>
5144 <p>disallow specifying a port in telnet G)oto's.</p>
5145 </dd>
5146
5147 <dt><strong><samp>useragent</samp></strong>
5148 </dt>
5149
5150 <dd>
5151 <p>disallow modifications of the User-Agent
5152 header.</p>
5153 </dd>
5154 </dl>
5155 </dd>
5156
5157 <dt><code><strong>-resubmit_posts</strong></code>
5158 </dt>
5159
5160 <dd>
5161 <p>toggles forced resubmissions (no-cache) of forms with
5162 method POST when the documents they returned are sought
5163 with the PREV_DOC (<em>left-arrow</em>) command or from
5164 the <em>History Page</em>.</p>
5165 </dd>
5166
5167 <dt><code><strong>-rlogin</strong></code>
5168 </dt>
5169
5170 <dd>
5171 <p>disable recognition of rlogin commands.</p>
5172 </dd>
5173
5174 <dt><code><strong>-scrollbar</strong></code>
5175 </dt>
5176
5177 <dd>
5178 <p>toggles showing scrollbar.</p>
5179 </dd>
5180
5181 <dt><code><strong>-scrollbar_arrow</strong></code>
5182 </dt>
5183
5184 <dd>
5185 <p>toggles showing arrows at ends of the scrollbar.</p>
5186 </dd>
5187
5188 <dt><code><strong>-selective</strong></code>
5189 </dt>
5190
5191 <dd>
5192 <p>require .www_browsable files to browse
5193 directories.</p>
5194 </dd>
5195
5196 <dt>
5197 <code><strong>-session=</strong><em>FILENAME</em></code>
5198 </dt>
5199
5200 <dd>
5201 <p>resumes from specified file on startup and saves
5202 session to that file on exit.</p>
5203 </dd>
5204
5205 <dt>
5206 <code><strong>-sessionin=</strong><em>FILENAME</em></code>
5207 </dt>
5208
5209 <dd>
5210 <p>resumes session from specified file.</p>
5211 </dd>
5212
5213 <dt>
5214 <code><strong>-sessionout=</strong><em>FILENAME</em></code>
5215 </dt>
5216
5217 <dd>
5218 <p>saves session to specified file.</p>
5219 </dd>
5220
5221 <dt><code><strong>-short_url</strong></code>
5222 </dt>
5223
5224 <dd>
5225 <p>show very long URLs in the status line with "..." to
5226 represent the portion which cannot be displayed. The
5227 beginning and end of the URL are displayed, rather than
5228 suppressing the end.</p>
5229 </dd>
5230
5231 <dt><code><strong>-show_cursor</strong></code>
5232 </dt>
5233
5234 <dd>
5235 <p>If enabled the cursor will not be hidden in the right
5236 hand corner but will instead be positioned at the start
5237 of the currently selected link. Show cursor is the
5238 default for systems without FANCY_CURSES capabilities.
5239 The default configuration can be changed in userdefs.h or
5240 <a href="#lynx.cfg">lynx.cfg</a>. It also can be set and
5241 saved via the &ldquo;o&rdquo;ptions menu. The command
5242 line switch toggles the default.</p>
5243 </dd>
5244
5245 <dt><code><strong>-show_rate</strong></code>
5246 </dt>
5247
5248 <dd>
5249 <p>If enabled the transfer rate is shown in bytes/second.
5250 If disabled, no transfer rate is shown. Use lynx.cfg or
5251 the options menu to select KiB/second and/or ETA.</p>
5252 </dd>
5253
5254 <dt><code><strong>-soft_dquotes</strong></code>
5255 </dt>
5256
5257 <dd>
5258 <p>toggles emulation of the old Netscape and Mosaic bug
5259 which treated &ldquo;<samp>&gt;</samp>&rdquo; as a
5260 co-terminator for double-quotes and tags.</p>
5261 </dd>
5262
5263 <dt><code><strong>-source</strong></code>
5264 </dt>
5265
5266 <dd>
5267 <p>works the same as dump but outputs HTML source instead
5268 of formatted text. For example</p>
5269
5270 <blockquote>
5271 <pre>
5272 lynx -source . &gt;foo.html
5273 </pre>
5274 </blockquote>
5275
5276 <p>generates HTML source listing the files in the current
5277 directory. Each file is marked by an HREF relative to the
5278 parent directory. Add a trailing slash to make the HREF's
5279 relative to the current directory:</p>
5280
5281 <blockquote>
5282 <pre>
5283 lynx -source ./ &gt;foo.html
5284 </pre>
5285 </blockquote>
5286 </dd>
5287
5288 <dt><code><strong>-stack_dump</strong></code>
5289 </dt>
5290
5291 <dd>
5292 <p>disable SIGINT cleanup handler.</p>
5293 </dd>
5294
5295 <dt><code><strong>-startfile_ok</strong></code>
5296 </dt>
5297
5298 <dd>
5299 <p>allow non-http startfile and homepage with
5300 <em>-validate</em>.</p>
5301 </dd>
5302
5303 <dt><code><strong>-stderr</strong></code>
5304 </dt>
5305
5306 <dd>
5307 <p>When dumping a document using
5308 <code><strong>-dump</strong></code> or
5309 <code><strong>-source</strong></code>, Lynx normally does
5310 not display alert (error) messages that you see on the
5311 screen in the status line. Use the
5312 <code><strong>-stderr</strong></code> option to tell Lynx
5313 to write these messages to the standard error.</p>
5314 </dd>
5315
5316 <dt><code><strong>-stdin</strong></code>
5317 </dt>
5318
5319 <dd>
5320 <p>read the startfile from standard input (UNIX
5321 only).</p>
5322 </dd>
5323
5324 <dt><code><strong>-syslog=</strong><em>text</em></code>
5325 </dt>
5326
5327 <dd>
5328 <p>information for syslog call.</p>
5329 </dd>
5330
5331 <dt><code><strong>-syslog-urls</strong></code>
5332 </dt>
5333
5334 <dd>
5335 <p>log requested URLs with syslog.</p>
5336 </dd>
5337
5338 <dt><code><strong>-tagsoup</strong></code>
5339 </dt>
5340
5341 <dd>
5342 <p>initialize DTD with "TagSoup" tables, <a href=
5343 "keystrokes/option_help.html#tagsoup">more
5344 details</a>.</p>
5345 </dd>
5346
5347 <dt><code><strong>-telnet</strong></code>
5348 </dt>
5349
5350 <dd>
5351 <p>disable recognition of telnet commands.</p>
5352 </dd>
5353
5354 <dt><code><strong>-term=</strong><em>TERM</em></code>
5355 </dt>
5356
5357 <dd>
5358 <p>tell Lynx what terminal type to assume it is talking
5359 to. (This may be useful for remote execution, when, for
5360 example, Lynx connects to a remote TCP/IP port that
5361 starts a script that, in turn, starts another Lynx
5362 process.)</p>
5363 </dd>
5364
5365 <dt><code><strong>-timeout=</strong><em>N</em></code>
5366 </dt>
5367
5368 <dd>
5369 <p>For win32, sets the network read-timeout, where
5370 <em>N</em> is given in seconds.</p>
5371 </dd>
5372
5373 <dt><code><strong>-tlog</strong></code>
5374 </dt>
5375
5376 <dd>
5377 <p>toggles use of a <em>Lynx Trace Log</em> for the
5378 session. The log is named <em>Lynx.trace</em> and is
5379 created in the home directory when Lynx trace mode is
5380 turned on via the <em>-trace</em> command line switch
5381 (see below), or via the TRACE_TOGGLE (<em>Control-T</em>)
5382 keystroke command. Once a log is started for the session,
5383 all trace and other stderr messages are written to the
5384 log. The contents of the log can be examined during the
5385 session via the TRACE_LOG (normally,
5386 &ldquo;<samp>;</samp>&rdquo;) keystroke command. If use
5387 of a Lynx Trace Log is turned off, any trace output will
5388 go to the standard error stream.</p>
5389 </dd>
5390
5391 <dt><code><strong>-tna</strong></code>
5392 </dt>
5393
5394 <dd>
5395 <p>turns on <a href="#tna">"Textfields Need
5396 Activation"</a> mode.</p>
5397 </dd>
5398
5399 <dt><code><strong>-trace</strong></code>
5400 </dt>
5401
5402 <dd>
5403 <p>turns on Lynx trace mode. If a Lynx Trace Log
5404 (<em>Lynx.trace</em> in the home directory) has been
5405 started for the current session, all trace messages are
5406 written to that log, and can be examined during the
5407 session via the TRACE_LOG (normally,
5408 &ldquo;<samp>;</samp>&rdquo;) command. If no Trace Log
5409 file is in use, trace messages go to stderr.</p>
5410 </dd>
5411
5412 <dt>
5413 <code><strong>-trace_mask=</strong><em>value</em></code>
5414 </dt>
5415
5416 <dd>
5417 <p>turn on optional traces, which may result in very
5418 large trace files. Logically OR the values to combine
5419 options:</p>
5420
5421 <dl>
5422 <dt>1</dt>
5423
5424 <dd>
5425 <p>SGML character parsing states</p>
5426 </dd>
5427
5428 <dt>2</dt>
5429
5430 <dd>
5431 <p>color-style</p>
5432 </dd>
5433
5434 <dt>4</dt>
5435
5436 <dd>
5437 <p>TRST (table layout)</p>
5438 </dd>
5439
5440 <dt>8</dt>
5441
5442 <dd>
5443 <p>config (lynx.cfg and .lynxrc contents)</p>
5444 </dd>
5445
5446 <dt>16</dt>
5447
5448 <dd>
5449 <p>binary string copy/append, used in form data
5450 construction.</p>
5451 </dd>
5452 </dl>
5453 </dd>
5454
5455 <dt><code><strong>-traversal</strong></code>
5456 </dt>
5457
5458 <dd>
5459 <p>traverse all http links derived from startfile. When
5460 used with <em>-crawl</em>, each link that begins with the
5461 same string as startfile is output to a file, intended
5462 for indexing. See CRAWL.announce for more
5463 information.</p>
5464 </dd>
5465
5466 <dt><code><strong>-trim_input_fields</strong></code>
5467 </dt>
5468
5469 <dd>
5470 <p>trim input text/textarea fields in forms.</p>
5471 </dd>
5472
5473 <dt><code><strong>-underscore</strong></code>
5474 </dt>
5475
5476 <dd>
5477 <p>toggles use of _underline_ format in dumps.</p>
5478 </dd>
5479
5480 <dt><code><strong>-update_term_title</strong></code>
5481 </dt>
5482
5483 <dd>
5484 <p>enables updating the title in terminal emulators. Use
5485 only if your terminal emulator supports that escape code.
5486 Has no effect when used with -notitle.</p>
5487 </dd>
5488
5489 <dt><code><strong>-use_mouse</strong></code>
5490 </dt>
5491
5492 <dd>
5493 <p>turn on mouse support, if available.</p>
5494 </dd>
5495
5496 <dt>
5497 <code><strong>-useragent=</strong><em>STRING</em></code>
5498 </dt>
5499
5500 <dd>
5501 <p>set different Lynx User-Agent header. Lynx produces a
5502 warning on startup if the <em>STRING</em> does not
5503 contain "Lynx" or "L_y_n_x", see the <a href=
5504 "#noteUA">note</a> in the Options Menu section for
5505 rationale.</p>
5506 </dd>
5507
5508 <dt><code><strong>-validate</strong></code>
5509 </dt>
5510
5511 <dd>
5512 <p>accept only http URLs (meant for validation).</p>
5513 </dd>
5514
5515 <dd>
5516 <p>This flag implies security restrictions generally more
5517 severe than <em>-anonymous</em>: restriction options as
5518 for <em>-restrictions=all</em>, with the notable
5519 exception that goto remains enabled for http and https
5520 URLs; in addition, the PRINT and DOWNLOAD commands are
5521 completely disabled, and use of a Trace Log file is
5522 forced off.</p>
5523 </dd>
5524
5525 <dd>
5526 <p>Any relaxing of restriction that might be implied by
5527 an also present (or implied) <em>-anonymous</em> flag is
5528 overridden, the only way to possibly relax <em>some</em>
5529 of the restrictions to the level applicable for
5530 "anonymous" accounts is with an explicit
5531 <em>-restrictions=default</em>.</p>
5532 </dd>
5533
5534 <dt><code><strong>-verbose</strong></code>
5535 </dt>
5536
5537 <dd>
5538 <p>toggles [LINK], [IMAGE] and [INLINE] comments with
5539 filenames of these images.</p>
5540 </dd>
5541
5542 <dt><code><strong>-version</strong></code>
5543 </dt>
5544
5545 <dd>
5546 <p>print version information.</p>
5547 </dd>
5548
5549 <dt><code><strong>-vikeys</strong></code>
5550 </dt>
5551
5552 <dd>
5553 <p>enable vi-like key movement.</p>
5554 </dd>
5555
5556 <dt><code><strong>-wdebug</strong></code>
5557 </dt>
5558
5559 <dd>
5560 <p>enable Waterloo tcp/ip packet debug (print to watt
5561 debugfile). This applies only to DOS versions compiled
5562 with WATTCP or WATT-32.</p>
5563 </dd>
5564
5565 <dt><code><strong>-width=</strong><em>NUMBER</em></code>
5566 </dt>
5567
5568 <dd>
5569 <p>number of columns for formatting of dumps, default is
5570 80.</p>
5571 </dd>
5572
5573 <dt><code><strong>-with_backspaces</strong></code>
5574 </dt>
5575
5576 <dd>
5577 <p>emit backspaces in output if -dumping or -crawling
5578 (like <code>man</code> does).</p>
5579 </dd>
5580 </dl>
5581 </dd>
5582 </dl>
5583
5584 <p>No options are required, nor is a startfile argument required.
5585 White space can be used in place of equal sign separators
5586 (&ldquo;<samp>=</samp>&rdquo;) appearing in the option list
5587 above. It can not be used in place of the equal signs in forms
5588 like "-option=on" and "-option=off" for simple switches and
5589 toggles, for which "-option" alone (without a value) is
5590 valid.</p>
5591
5592 <p>[<a href="#ToC-Invoking">ToC</a>]</p>
5593
5594 <h2 id="Environments"><a name="Environment" id=
5595 "Environment"><em>Environment variables used by Lynx</em></a></h2>
5596
5597 <p>Lynx uses certain environment variables and sets a few of
5598 them. Please visit a <a href=
5599 "keystrokes/environments.html">separate page</a> for this rather
5600 technical information.</p>
5601
5602 <p>[<a href="#ToC-Environment">ToC</a>]</p>
5603
5604 <h2 id="id-lynx.cfg"><a name="lynx.cfg" id="lynx.cfg">Main
5605 configuration file lynx.cfg</a></h2>
5606
5607 <p>Lynx has several levels of customization: from the Options
5608 Menu (accessible on-line, and possibly stored in your local
5609 .lynxrc file), via command-line switches on startup (mainly for
5610 batch processing). The most important and numerous default
5611 settings are stored in the Lynx configuration file
5612 <em>lynx.cfg</em>.</p>
5613
5614 <p>If you are on a UNIX system you should have appropriate
5615 permissions to make changes there or ask your system
5616 administrator to modify lynx.cfg for your needs. This file
5617 provides default settings for all accounts on your system. It may
5618 be copied to your shell account and included with -cfg command
5619 line switch or via an environment variable LYNX_CFG (if you have
5620 shell access). Starting with version 2.8.1 Lynx has an include
5621 facility so you can load the system-wide configuration file and
5622 easily add one or more settings from your local add-on
5623 configuration file. It is really cool to read lynx.cfg with its
5624 comments for hundreds of options, most of them commented out
5625 because they are built-in defaults. You may visit an index of
5626 options: <a href=
5627 "https://lynx.invisible-island.net/release/lynx_help/cattoc.html">
5628 by category</a> or <a href=
5629 "https://lynx.invisible-island.net/release/lynx_help/alphatoc.html">
5630 by alphabet</a>.</p>
5631
5632 <p>To view your current configuration derived from lynx.cfg and
5633 any included configuration files, press <em>&ldquo;g&rdquo;</em>
5634 and type in &ldquo;<samp>lynxcfg:</samp>&rdquo;. If you are using
5635 the forms-based <em>Options Menu</em>, you may press
5636 <em>&ldquo;o&rdquo;</em> for the Options Menu and follow the
5637 <em>Check your lynx.cfg</em>'s link near the bottom.</p>
5638
5639 <p>However, for those who have a restricted account many Lynx
5640 features may be disabled by the system administrator, you
5641 probably will not see your lynx.cfg.</p>
5642
5643 <p>[<a href="#ToC-lynx.cfg">ToC</a>]</p>
5644
5645 <h2 id="id-Hist"><a name="Hist" id="Hist">Lynx development
5646 history</a></h2>
5647
5648 <p>Lynx grew out of efforts to build a campus-wide information
5649 system at The University of Kansas. The earliest versions of Lynx
5650 provided a user-friendly, distributed hypertext interface for
5651 users connected to multiuser (Unix and VMS) systems via
5652 curses-oriented display devices. A custom hypertext format was
5653 developed to support hypertext links to local files and files on
5654 remote Gopher servers. Using Gopher servers for distributed file
5655 service allowed information providers to publish information from
5656 a wide variety of platforms (including Unix, VMS, VM/CMS and
5657 Macintosh). In addition, Lynx became the most user-friendly
5658 Gopher client, although that was only an ancillary
5659 capability.</p>
5660
5661 <p>This distributed approach let providers retain complete
5662 control over their information, but it made communication between
5663 users and providers somewhat more difficult. Following the lead
5664 of Neal Erdwien, of Kansas State University, the Lynx hypertext
5665 format was extended to include links for including ownership
5666 information with each file. This information made it possible for
5667 users running Lynx clients to send comments and suggestions via
5668 e-mail to the providers.</p>
5669
5670 <p>This early version of Lynx was also augmented to support
5671 hypertext links to programs running on remote systems. It
5672 included the ability to open a Telnet connection, as well as the
5673 ability to start programs via rexec, inetd, or by direct socket
5674 connects. These capabilities were included to allow users to
5675 access databases or custom program interfaces.</p>
5676
5677 <p>A subsequent version of Lynx incorporated the World Wide Web
5678 libraries to allow access to the full list of WWW servers, along
5679 with the option to build hypertext documents in HTML, rather than
5680 the native Lynx format. HTML has become far more widely used, and
5681 the native format has been phased out. With the addition of the
5682 WWW libraries, Lynx became a fully-featured WWW client, limited
5683 only by the display capabilities offered in the curses
5684 environment.</p>
5685
5686 <p>Lynx was designed by Lou Montulli, Charles Rezac and Michael
5687 Grobe of Academic Computing Services at The University of Kansas.
5688 Lynx was implemented by Lou Montulli and maintained by Garrett
5689 Arch Blythe and Craig Lavender.</p>
5690
5691 <p>Members of the <a href="lynx-dev.html">lynx-dev</a> list have
5692 developed and supported Lynx since release of v2.3 in May
5693 1994.<br>
5694 The Lynx2-3FM code set was released as v2.4 in June 1995.<br>
5695 The Lynx2-4FM code set was released as v2.5 in May 1996.<br>
5696 The Lynx2-5FM code set was released as v2.6 in September
5697 1996.<br>
5698 The Lynx2-6FM code set was released as v2.7 in February 1997.<br>
5699 The v2-7FM code set was released as v2.7.1 in April 1997.<br>
5700 The v2-7-1FM code set was released as v2.7.2 in January 1998.<br>
5701 The 2.7.1 development set was released as v2.8 in March 1998.<br>
5702 The 2.8 development set was released as v2.8.1 in October
5703 1998.<br>
5704 The 2.8.1 development set was released as v2.8.2 in June
5705 1999.<br>
5706 The 2.8.2 development set was released as v2.8.3 in April
5707 2000.<br>
5708 The 2.8.3 development set was released as v2.8.4 in July
5709 2001.<br>
5710 The 2.8.4 development set was released as v2.8.5 in February
5711 2004.<br>
5712 The 2.8.5 development set was released as v2.8.6 in October
5713 2006.<br>
5714 The 2.8.6 development set was released as v2.8.7 in July
5715 2009.<br>
5716 The 2.8.7 development set was released as v2.8.8 in February
5717 2014.<br>
5718 The 2.8.8 development set was released as v2.8.9 in July
5719 2018.<br>
5720 The 2.8.9 development set was released as v2.9.0 in January
5721 2024.<br></p>
5722
5723 <p>Lynx has incorporated code from a variety of sources along the
5724 way. The earliest versions of Lynx included code from Earl Fogel
5725 of Computing Services at the University of Saskatchewan, who
5726 implemented HYPERREZ in the Unix environment. Those versions also
5727 incorporated libraries from the Unix Gopher clients developed at
5728 the University of Minnesota, and the later versions of Lynx rely
5729 on the WWW client library code developed by Tim Berners-Lee (and
5730 others) and the WWW community.</p>
5731
5732 <p>Contributors have generally been acknowledged in the CHANGES
5733 file. Earlier CHANGES files can be found in the docs/
5734 subdirectory of this distribution.</p>
5735
5736 <p>Information on obtaining the most current version of Lynx is
5737 available at <a href=
5738 "https://lynx.invisible-island.net/current/index.html">the
5739 current distribution page</a>.</p>
5740
5741 <p>[<a href="#Contents">ToC</a>]</p>
5742 </body>
5743 </html>