All previously entered goto URLs are saved in a circular buffer, and can be accessed at the prompt by pressing the up-arrow or down-arrow keys. If any data was transferred before the interrupt, it will be displayed. Use left-arrow to return from there to your previous position in the document. When you quit or exit the shell you will return to Lynx usually exit under Unix and logout under VMS.
This command is usually disabled for anonymous users. The number of lines in the file, URL, title, owner, and type are shown.
Normally the information is shown formatted with margins for readability. You can make Lynx show the URL wrapped without margins, e. The ; command shows the Lynx Trace Log Lynx. If a log has not been started, any trace messages will be sent to the screen and will disturb the normal display unless the system supports piping and that was used to redirect stderr messages to a file.
The log is started when Lynx trace mode is turned on via the -trace command line switch, or via the Control-T toggle, if Lynx has been compiled to log the trace and other stderr messages by default. If not, ability to create a log can be toggled on with the -tlog switch. Note that this ability is probably disabled in anonymous or validation accounts. When on, links will be created for all images, including inline images. If you have an image viewer mapped to the image's MIME type, you can activate such links to view an inline image.
You should normally have this mode toggled off. When on, the charset is assumed to match the selected character set and 8-bit characters are not reverse translated with respect to the ISO conversion tables. It applies only to documents or links or form submit buttons of http servers.
A statusline message will notify you if the context for this command was inappropriate. The HEAD requests always are sent to the http server, i.
Note that for form submissions, http servers vary in whether they'll treat HEAD requests as valid and return the CGI script's headers, or treat it as invalid and return an error message. If the line-wrapping margin is wider than the terminal's display, scroll left by half of the display's width. Normally Lynx fits text onto the screen, wrapping lines. With this feature, Lynx provides the ability to eliminate line-wrapping up to an internal line-limit of characters.
You can scroll left and right in the screen to view the wide lines. If the line-wrapping margin is wider than the terminal's display, scroll right by half of the display's width.
Lynx offers other, advanced navigation features when numbers are used to invoke the Follow Link or goto link or page number: or Select Pop-up Option Number: prompts. This section describes the Lynx Forms Interface. HTML gives document providers the ability to create on-line forms which may be filled out when the document is viewed. When a form is submitted the information on the form can be used to search a database or complete a survey. An HTML Form provides for the use of buttons to perform an action such as submit , checkboxes, radio buttons or popups to select options from a list, and fields for entering text.
Buttons are displayed in the same way that Lynx displays links in a document. To "push" the button press the right-arrow or Return key. Checkboxes are displayed as square brackets: [ ] and radio buttons are displayed as parenthesis:. To check a box or select a radio button press the right-arrow or Return key. To select an option press the right-arrow or Return key. A box with a border of asterisks or line-drawing characters will pop up with the list of possible options listed within the box.
Use the up-arrow , down-arrow , page-up , page-down , and other navigation keys to move the cursor among options, and the right-arrow or Return key to select an option. The default setting for use of popups or radio button lists can be toggled via the -popup command line switch. You may enter text directly by typing at the keyboard. Use the Line Editor keys to correct errors. If you try to input more text than the field can hold, the line editor will not accept the additional characters.
If you fill a text field the cursor will not move off the field but remain at the last field position. Use the up-arrow , and down-arrow , TAB or Return keys to move up, or down from the text entry field. NOTE, however, that Return also will submit the form if the text entry field is the only non-hidden field in the form. If "Textfields Need Activation" mode is turned on with the -tna command-line option or in lynx. Keystrokes have their normal command meaning unless the Line Editor gets activated with Return or Right Arrow.
This mode can be used to avoid "getting stuck" in input fields, especially by users who rarely fill out forms. NOTE: If you have a text input field selected you will not have access to most of the Lynx keystroke commands, because they are interpreted by the Line Editor as either text entries or editing commands.
On the other hand,. You enter text on each line to construct the overall message. The up-arrow , and down-arrow or Return keys move you to the preceding, or next line of the overall message, as for INPUT fields. The statusline should tell you when this is possible and what key to use, it might for example say.
An external editor has to be defined, for example in the Options Menu , before you can start using this function. If you have some single keys or control keys to spare that you do not need for their normal purposes, you can dedicate those keys to invoke the special functions without requiring a prefix key. But this does not work reliably everywhere it depends on the way Lynx is compiled, including which libraries are used, and behavior of the connection and terminal type.
In general, you can move around the form using the standard Lynx navigation keys. The up-arrow and down-arrow keys, respectively, select the previous or next field, box, or button. The TAB key selects the next field, box, or button. To submit the form press right-arrow or Return when positioned on the form's submit button. If you've submitted the form previously during the Lynx session, have not changed any of the form content, and the METHOD was GET , Lynx will retrieve from its cache what was returned from the previous submission.
The right-arrow and Return keys also will invoke a no-cache resubmission if the reply from a form submission included a META element with a no-cache Pragma or Cache-Control directive:. Lynx can be compiled so that it resubmits the form in those cases as well, and the default can be changed via lynx. If the form has one text entry field and no other fields except, possibly, hidden INPUT fields not included in the display, then that field also serves as a submit button, and pressing right-arrow or Return on that field will invoke submission of the form.
Be sure to use up-arrow , down-arrow or TAB to move off the text entry field, in such cases, if it is not your intention to submit the form or to retrieve what was returned from an earlier submission if the content was not changed and the METHOD was GET.
Forms can have multiple submit buttons, if they have been assigned NAMEs in the markup. In such cases, information about which one of the buttons was used to submit the form is included in the form content. Inlined images can be used as submit buttons in forms: If such buttons are assigned NAMEs in the markup, for graphic clients they can also serve as image maps , and the x,y coordinates of the graphic client's cursor position in the image when it was clicked are included in the form content.
Since Lynx cannot inline the image, and the user could not have moved a cursor from the origin for the image, if no alternatives are made available in the markup Lynx sends a 0,0 coordinate pair in the form content. Document authors who use images as submit buttons, but have at least some concern for text clients and sight-challenged Webizens, should include VALUEs for the buttons in such markup.
If clickable images is set, the "[IMAGE]" portion of the string is a link for the image, and the "Submit" portion is the button for submitting the form.
Otherwise, the entire string is treated as a submit button. The script which analyzes the form content thus could be made aware whether the submission was by a user with a graphic client and had image loading turned on, or by a user who did not see the image nor make a conscious choice within it. Ideally, the script which analyzes the submitted content will treat the 0,0 coordinate pair as an indicator that the user did not see the image and make a conscious choice within it.
These often are used to keep track of information across a series of related form submissions, but have the potential for including information about the user that might be considered to represent an invasion of privacy.
These can be used to keep track of information across submissions, and to cast it unmodifiable in the current form, but keep the user aware that it will be included in the submission. This also can be done via a META element in any document:. As a text browser, Lynx does not display images as such -- you need to define a viewer in lynx.
HTML includes markup for creating tables structured as arrays of cells aligned by columns and rows on the displayed page. This generally makes all of the content of the table readable, preserves most of the intra-cell organization, and makes all of the links in the table accessible, but any information critically dependent on the column and row alignments intended for the table will be missed.
An example table using TAB elements is included in the test subdirectory of the Lynx distribution. Starting with version 2. This tabular representation for simple tables TRST does not attempt to implement full support for any table model. Limitations are:. When TRST fails because a table is not "simple" enough, the representation falls back to the minimal handling described earlier. Many but, unfortunately, by no means all tables that represent inherently tabular material will thus be shown with correct tabular formatting.
Where table markup is used only for layout purposes containing whole blocks of text and list within table cells and not essential for understanding the textual contents, it remains basically ignored. TRST of the source distribution. For tabular display of more complex tables, Lynx users can make use of external scripts or programs. The normal Lynx distribution currently does not provide such scripts, but they can be written locally or downloaded from several sources. Lynx implements the HTML 3.
See the example table using TAB elements in the test subdirectory of the Lynx distribution as a model for using this functionality.
Some implementations of HTML include markup, primarily designed for graphic clients, that is intended to create an array of simultaneously displayed, independently scrolling windows. Such windows have been termed frames. If the document provider has disregard for text clients and sight-challenged Webizens, and thus does not include substantive content in the NOFRAMES section or a link in it to a document suitable for text clients, you can usually guess from the labeling of the frame links which one has the substantive material if there is any , or you can try each of those links to see if anything worthwhile is returned.
Some sites -- in ignorance of Lynx capabilities -- may tell you for example "to view this page you need Netscape Navigator". You can simply ignore such warnings and access the frames via the Lynx-generated links as above. Some implementations of HTML markup include provisions for creating a non-scrolling window to be positioned at the top of each page, containing links with brief, descriptive link names, analogous to a Windows toolbar.
Such windows have been termed banners. Lynx recognizes and processes all of the HTML 3. Lynx also recognizes the HTML 3. However, in contrast to named A nchors, the FN container element is treated as a block i. For example, if the document contains:. Then, upon reading the footnote, you can return to your previous position in the document by pressing the left-arrow key.
This is an example:. The lists can be nested, yielding progressively greater indentation, up to six levels. The HTML 2. A single nesting index is maintained, so that different types of List elements can be used for different levels within the nest.
Also, the HTML 3. The content of any APPLET or OBJECT elements in the lists also will be indented appropriately for the current nesting depth, but those will not invoke line breaks unless indicated by their content, and it should not include markup which is inappropriate within the list.
Lynx also supports the TYPE attribute for OL elements, which can have values of 1 for Arabic numbers, I or i for uppercase or lowercase Roman numerals, or A or a for uppercase or lowercase letters, that increment for successive LI elements in the list block. The values should be specified as Arabic numbers, but will be displayed as Arabic, Roman, or alphabetical depending on the TYPE for the block.
The values can range from to the system's maximum positive integer for Arabic numbers. For alphabetical orders, the values can range from 1 A or a to ZZZ or zzz.
The HTML 3. Character level quotes, designated by the Q element, in contrast are simply directives in the markup to insert an appropriate quotation mark. Lynx renders block quotes with a greater than normal left and right indentation.
Lynx does not support italics, and normally substitutes underlining, but does not underline block quotes so as not to obscure any explicit emphasis elements within the quotation.
Lynx has superior support for HTML 4. However, to see the characters other than 7bit properly you should set your display character set from Option Menu and save its value, this is a Frequently Asked Question. Fine-turning is also available from lynx.
HTML includes markup, designed primarily for graphic clients, that treats inlined images as maps, such that areas of the image within which a mouse cursor was positioned when the mouse was clicked can correspond to URLs which should be retrieved. The original implementations were based on the client sending an http server the x,y coordinates associated with the click , for handling by a script invoked by the server, and have been termed server-side-image-maps. Lynx has no rational way of coping with such a procedure, and thus simply sends a 0,0 coordinate pair, which some server scripts treat as an instruction to return a document suitable for a text client.
These have been termed client-side-image-maps. All MAPs encountered in documents during a Lynx session are cached, so that they need not be retrieved repeatedly when referenced in different documents. If the IMG element also indicates a server-side-image-map via an ISMAP attribute, Lynx normally will create a link for that as well, using an [ISMAP] pseudo-ALT followed by a hyphen to indicate its association with the client-side-image-map rather than ignoring it, and will submit a 0,0 coordinate pair if that link is activated.
Although, the client-side-image-map may be more useful for a client such as Lynx, because all of the URLs associated with the image map can be accessed, and their nature indicated via ALT attributes, Lynx-friendly sites can map 0,0 such that the server returns a for-text-client document homologous to the content of FIG elements see below.
Inclusion of such a link for submissions to the server can be disabled by default via the configuration file lynx. These are the ideal way to handle client-side-image-maps , because the FIG content provides complete alternative markup, rather than relying on the client to construct a relatively meager list of links with link names based on ALT strings.
HTML includes provision for passing instructions to clients via directives in META elements, and one such instruction, via the token Refresh , should invoke reloading of the document, fetched from a server with the same URL or a new URL, at a specified number of seconds following receipt of the current document.
This procedure has been termed client-side-pull. An example of such an element is:. A no-cache directive is implied when the Refresh if for the same URL. Lynx recognizes and processes Refresh directives in META elements, but puts up a labeled link, typically in the upper left corner of the display, indicating the number of seconds intended before a refresh, and the URL for the refresh, instead of making the request automatically after the indicated number of seconds.
This allows people using a braille interface any amount of time to examine the current document before activating the link for the next URL. In general, if the number of seconds indicated is short, the timing is not critical and you can activate the link whenever you like. If it is long e. HTTP provides a means to carry state information across successive connections between a browser and an http server. Normally, http servers respond to each browser request without relating that request to previous or subsequent requests.
When replying to a request, the server can send a Set-Cookie MIME header which contains information cookies relevant to the browser's request, and in subsequent requests the browser can send a Cookie MIME header with information derived from previously received cookies. State Management via cookie exchanges originally was implemented by Netscape, and such cookies are now designated as Version 0. Lynx supports both Version 0 and Version 1 cookie exchanges.
The domain listed in these options must be identical to the domain the cookie comes from, there is no wildcard matching.
A common use of cookies by http servers is simply to track the documents visited by individual users. Though this can be useful to the site's WebMaster for evaluating and improving the organization of links in the various documents of the site, if the user has configured Lynx to include a From MIME header with the user's email address in http requests, or has passed personal information to the server via a form submission, the tracking might be used to draw inferences, possibly incorrect, about that user, and may be considered by some as an invasion of privacy.
An example of worthwhile State Management via cookies is the setting of personal preferences, typically via a form submission to the site, which will then apply to all documents visited at that site.
Entries in the Cache Jar are ordered from oldest at the top to newest. The user can easily access any document which is in the cache, especially those which may be soon removed due to configurable limits on the maximum number of cached documents, as well as the maxmimum amount of memory used by the cache. Lynx's current state all information about the user's current activity with lynx is called a session. Sessions are useful in particular if you are in the middle of exploring something on the web and you were forced to stop abruptly, losing any trace of your current work.
A session can be automatically restored as lynx starts after a clean exit. If you do not want to specify these options at each lynx startup, there is an option in lynx. The syntax of the session file is simple. You can use a text editor to modify, add new entries, or remove URLs you no longer want.
A summary of the Lynx command line options switches is returned to stdout if Lynx is invoked with the -help switch. A description of the options also should be available via the system man Unix pages or help VMS libraries. On Win32, typing lynx -help in a DOS window should display similarly.
The basic syntax of the Lynx command line can be represented as one of the following:. The Lynx Development page gives some background on ongoing development.
Before each patch-release, I usually do a test-build on Windows. That builds several flavors, which I use in testing. Along with that, since , I have made packages for a few of these executables. Although starting with release 2. This is the older color-scheme used by Lynx , from Links and form-fields are colored. It works with HTML5.
Most people find the program works after thoroughly reading the instructions below, though I can't offer installation support - just don't get the time for answering emails these days. Read the words below if you have trouble - there's information I haven't bothered to put in the readme. Lynx is copyrighted by the University of Kansas and is distributed without restrictions on usage or redistribution under the GNU General Public License.
See the readme. In Windows Explorer try selecting the tools option at the top of the window, then select Folder Options. Click the "view" tab, then un-check the box for "hide extensions for known file types". I double clicked on lynx. This happens if cannot connect to the internet, and is often because Lynx.
0コメント