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