📄 userdefs.h
字号:
/********************************
* The DEFAULT_CACHE_SIZE specifies the number of WWW documents to be
* cached in memory at one time.
*
* This so-called cache size (actually, number) may be modified in lynx.cfg
* and or with the command line argument -cache=NUMBER The minimum allowed
* value is 2, for the current document and at least one to fetch, and there
* is no absolute maximum number of cached documents. On Unix, and VMS not
* compiled with VAXC, whenever the number is exceeded the least recently
* displayed document will be removed from memory.
*
* On VMS compiled with VAXC, the DEFAULT_VIRTUAL_MEMORY_SIZE specifies the
* amount (bytes) of virtual memory that can be allocated and not yet be freed
* before previous documents are removed from memory. If the values for both
* the DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE are exceeded, then
* least recently displayed documents will be freed until one or the other
* value is no longer exceeded. The value can be modified in lynx.cfg.
*
* The Unix and VMS but not VAXC implementations use the C library malloc's
* and calloc's for memory allocation, and procedures for taking the actual
* amount of cache into account still need to be developed. They use only
* the DEFAULT_CACHE_SIZE value, and that specifies the absolute maximum
* number of documents to cache (rather than the maximum number only if
* DEFAULT_VIRTUAL_MEMORY_SIZE has been exceeded, as with VAXC/VAX).
*/
#define DEFAULT_CACHE_SIZE 10
#if defined(VMS) && defined(VAXC) && !defined(__DECC)
#define DEFAULT_VIRTUAL_MEMORY_SIZE 512000
#endif /* VMS && VAXC && !__DECC */
/********************************
* If ALWAYS_RESUBMIT_POSTS is set TRUE, Lynx always will resubmit forms
* with method POST, dumping any cache from a previous submission of the
* form, including when the document returned by that form is sought with
* the PREV_DOC command or via the history list. Lynx always resubmits
* forms with method POST when a submit button or a submitting text input
* is activated, but normally retrieves the previously returned document
* if it had links which you activated, and then go back with the PREV_DOC
* command or via the history list.
*
* The default defined here can be changed in lynx.cfg, and can be toggled
* via the -resubmit_posts command line switch.
*/
#define ALWAYS_RESUBMIT_POSTS FALSE
/********************************
* CHARACTER_SET defines the default character set, i.e., that assumed
* to be installed on the user's terminal. It determines which characters
* or strings will be used to represent 8-bit character entities within
* HTML. New character sets may be defined as explained in the README
* files of the src/chrtrans directory in the Lynx source code distribution.
* For Asian (CJK) character sets, it also determines how Kanji code will
* be handled. The default defined here can be changed in lynx.cfg, and
* via the 'o'ptions menu. The 'o'ptions menu setting will be stored in
* the user's RC file whenever those settings are saved, and thereafter
* will be used as the default. Also see lynx.cfg for information about
* the -raw switch and LYK_RAW_TOGGLE command.
*
* Since Lynx now supports a wide range of platforms it may be useful
* to note that cpXXX codepages used by IBM PC compatible computers,
* and windows-xxxx used by native MS-Windows apps.
*
* Recognized character sets include:
*
* string for 'O'ptions Menu MIME name
* =========================== =========
* 7 bit approximations (US-ASCII) us-ascii
* Western (ISO-8859-1) iso-8859-1
* Western (cp850) cp850
* Western (windows-1252) windows-1252
* IBM PC US codepage (cp437) cp437
* DEC Multinational dec-mcs
* Macintosh (8 bit) macintosh
* NeXT character set next
* HP Roman8 hp-roman8
* Chinese euc-cn
* Japanese (EUC-JP) euc-jp
* Japanese (Shift_JIS) shift_jis
* Korean euc-kr
* Taipei (Big5) big5
* Vietnamese (VISCII) viscii
* Eastern European (ISO-8859-2) iso-8859-2
* Eastern European (cp852) cp852
* Eastern European (windows-1250) windows-1250
* Latin 3 (ISO-8859-3) iso-8859-3
* Latin 4 (ISO-8859-4) iso-8859-4
* Baltic Rim (cp775) cp775
* Baltic Rim (windows-1257) windows-1257
* Cyrillic (ISO-8859-5) iso-8859-5
* Cyrillic (cp866) cp866
* Cyrillic (windows-1251) windows-1251
* Cyrillic (KOI8-R) koi8-r
* Arabic (ISO-8859-6) iso-8859-6
* Arabic (cp864) cp864
* Arabic (windows-1256) windows-1256
* Greek (ISO-8859-7) iso-8859-7
* Greek (cp737) cp737
* Greek2 (cp869) cp869
* Greek (windows-1253) windows-1253
* Hebrew (ISO-8859-8) iso-8859-8
* Hebrew (cp862) cp862
* Hebrew (windows-1255) windows-1255
* Turkish (ISO-8859-9) iso-8859-9
* ISO-8859-10 iso-8859-10
* Ukrainian Cyrillic (cp866u) cp866u
* Ukrainian Cyrillic (KOI8-U) koi8-u
* UNICODE (UTF-8) utf-8
* RFC 1345 w/o Intro mnemonic+ascii+0
* RFC 1345 Mnemonic mnemonic
* Transparent x-transparent
*/
#define CHARACTER_SET "iso-8859-1"
/*****************************
* PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en",
* "fr") which will be indicated by Lynx in its Accept-Language headers
* as the preferred language. If available, the document will be
* transmitted in that language. This definition can be overridden via
* lynx.cfg. Users also can change it via the 'o'ptions menu and save
* that preference in their RC file. This may be a comma-separated list
* of languages in decreasing preference.
*/
#define PREFERRED_LANGUAGE "en"
/*****************************
* PREFERRED_CHARSET specifies the character set in MIME notation (e.g.,
* "ISO-8859-2", "ISO-8859-5") which Lynx will indicate you prefer in
* requests to http servers using an Accept-Charsets header.
* This definition can be overridden via lynx.cfg. Users also can change it
* via the 'o'ptions menu and save that preference in their RC file.
* The value should NOT include "ISO-8859-1" or "US-ASCII", since those
* values are always assumed by default.
* If a file in that character set is available, the server will send it.
* If no Accept-Charset header is present, the default is that any
* character set is acceptable. If an Accept-Charset header is present,
* and if the server cannot send a response which is acceptable
* according to the Accept-Charset header, then the server SHOULD send
* an error response with the 406 (not acceptable) status code, though
* the sending of an unacceptable response is also allowed. (RFC2068)
*/
#define PREFERRED_CHARSET ""
/*****************************
* If MULTI_BOOKMARK_SUPPORT is set to MBM_STANDARD or MBM_ADVANCED, and
* BLOCK_MULTI_BOOKMARKS (see below) is FALSE, and sub-bookmarks exist, all
* bookmark operations will first prompt the user to select an active
* sub-bookmark file or the default bookmark file. MBM_OFF is the default so
* that one (the default) bookmark file will be available initially. The
* default set here can be overridden in lynx.cfg. The user can turn on
* multiple bookmark support via the 'o'ptions menu, and can save that choice as
* the startup default via the .lynxrc file. When on, the setting can be
* STANDARD or ADVANCED. If support is set to the latter, and the user mode
* also is ADVANCED, the VIEW_BOOKMARK command will invoke a status line prompt
* at which the user can enter the letter token (A - Z) of the desired bookmark,
* or '=' to get a menu of available bookmark files. The menu always is
* presented in NOVICE or INTERMEDIATE mode, or if the support is set to
* STANDARD. No prompting or menu display occurs if only one (the startup
* default) bookmark file has been defined (define additional ones via the
* 'o'ptions menu). The startup default, however set, can be overridden on the
* command line via the -restrictions=multibook or the -anonymous or -validate
* switches.
*/
#ifndef MULTI_BOOKMARK_SUPPORT
#define MULTI_BOOKMARK_SUPPORT MBM_OFF
#endif /* MULTI_BOOKMARK_SUPPORT */
/*****************************
* If BLOCK_MULTI_BOOKMARKS is set TRUE, multiple bookmark support will
* be forced off, and cannot be toggled on via the 'o'ptions menu. This
* compilation setting can be overridden via lynx.cfg.
*/
#ifndef BLOCK_MULTI_BOOKMARKS
#define BLOCK_MULTI_BOOKMARKS FALSE
#endif /* BLOCK_MULTI_BOOKMARKS */
/********************************
* URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES are strings which will be
* prepended (together with a scheme://) and appended to the first element
* of command line or 'g'oto arguments which are not complete URLs and
* cannot be opened as a local file (file://localhost/string). Both
* can be comma-separated lists. Each prefix must end with a dot, each
* suffix must begin with a dot, and either may contain other dots (e.g.,
* .co.jp). The default lists are defined here, and can be changed
* in lynx.cfg. Each prefix will be used with each suffix, in order,
* until a valid Internet host is created, based on a successful DNS
* lookup (e.g., foo will be tested as www.foo.com and then www.foo.edu
* etc.). The first element can include a :port and/or /path which will
* be restored with the expanded host (e.g., wfbr:8002/dir/lynx will
* become http://www.wfbr.edu:8002/dir/lynx). The prefixes will not be
* used if the first element ends in a dot (or has a dot before the
* :port or /path), and similarly the suffixes will not be used if the
* the first element begins with a dot (e.g., .nyu.edu will become
* http://www.nyu.edu without testing www.nyu.com). Lynx will try to
* guess the scheme based on the first field of the expanded host name,
* and use "http://" as the default (e.g., gopher.wfbr.edu or gopher.wfbr.
* will be made gopher://gopher.wfbr.edu).
*/
#define URL_DOMAIN_PREFIXES "www."
#define URL_DOMAIN_SUFFIXES ".com,.edu,.net,.org"
/********************************
* If LIST_NEWS_NUMBERS is set TRUE, Lynx will use an ordered list
* and include the numbers of articles in news listings, instead of
* using an unordered list.
*
* The default defined here can be changed in lynx.cfg.
*/
#define LIST_NEWS_NUMBERS FALSE
/********************************
* If LIST_NEWS_DATES is set TRUE, Lynx will include the dates of
* articles in news listings. The dates always are included in the
* articles, themselves.
*
* The default defined here can be changed in lynx.cfg.
*/
#define LIST_NEWS_DATES FALSE
/*************************
* Set NEWS_POSTING to FALSE if you do not want to support posting to
* news groups via Lynx. If left TRUE, Lynx will use its news gateway to
* post new messages or followups to news groups, using the URL schemes
* described in the "Supported URL" section of the online 'h'elp. The
* posts will be attempted via the nntp server specified in the URL, or
* if none was specified, via the NNTPSERVER configuration or environment
* variable. Links with these URLs for posting or sending followups are
* created by the news gateway when reading group listings or articles
* from nntp servers if the server indicates that it permits posting.
* The setting here can be changed in lynx.cfg.
*/
#define NEWS_POSTING TRUE
/*************************
* Define LYNX_SIG_FILE to the name of a file containing a signature which
* can be appended to email messages and news postings or followups. The
* user will be prompted whether to append it. It is sought in the home
* directory. If it is in a subdirectory, begin it with a dot-slash
* (e.g., ./lynx/.lynxsig). The definition here can be changed in lynx.cfg.
*/
#define LYNX_SIG_FILE "_lynxsig"
/********************************
* BIBP_GLOBAL_SERVER is the default global server for bibp: links, used
* when a local bibhost or document-specified citehost is unavailable.
*/
#define BIBP_GLOBAL_SERVER "http://usin.org/"
/********************************
* If USE_SELECT_POPUPS is set FALSE, Lynx will present a vertical list
* of radio buttons for the OPTIONs in SELECT blocks which lack the
* MULTIPLE attribute, instead of using a popup menu. Note that if
* the MULTIPLE attribute is present in the SELECT start tag, Lynx
* always will create a vertical list of checkboxes for the OPTIONs.
*
* The default defined here can be changed in lynx.cfg. It can be
* set and saved via the 'o'ptions menu to override the compilation
* and configuration defaults, and the default always can be toggled
* via the -popup command line switch.
*/
#define USE_SELECT_POPUPS TRUE
/********************************
* If COLLAPSE_BR_TAGS is set FALSE, Lynx will not collapse serial
* BR tags. If set TRUE, two or more concurrent BRs will be collapsed
* into a single blank line. Note that the valid way to insert extra
* blank lines in HTML is via a PRE block with only newlines in the
* block.
*
* The default defined here can be changed in lynx.cfg.
*/
#define COLLAPSE_BR_TAGS TRUE
/********************************
* If SET_COOKIES is set FALSE, Lynx will ignore Set-Cookie headers
* in http server replies.
*
* The default defined here can be changed in lynx.cfg, and can be toggled
* via the -cookies command line switch.
*/
#define SET_COOKIES TRUE
/*******************************
* If ACCEPT_ALL_COOKIES is set TRUE, and SET_COOKIES is TRUE, Lynx will
* accept all cookies.
*
* The default defined here can be changed in lynx.cfg, and .lynxrc, or
* toggled via the -accept_all_cookies command line switch.
*/
#define ACCEPT_ALL_COOKIES FALSE
/****************************************************************
* Section 2. Things that you probably want to change or review
*
*/
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -