├── README.md ├── greet ├── lynx.cfg └── tweetbot.py /README.md: -------------------------------------------------------------------------------- 1 | # TweetBot 2 | This is A Simple TweetBot to Make Tweets 3 | 4 | ## Uses 5 | I am sharing this Bot That I used in A Tweet Competition that I Won xD. 6 | 7 | This Bot Can Work in CLI Mode Without Selenium 8 | It automates a command line browser called 'lynx' 9 | 10 | This does not need Twitter API To Work. 11 | You Can Simply Do By Put Your Account Creds. 12 | 13 | This Can be run in Android By Termux 14 | 15 | ## Requirements 16 | This Bot Was Made Keeping Speed And Resource Usage in Mind. 17 | So it uses least of requirements. 18 | 19 | ```apt install lynx python``` 20 | 21 | This uses lynx as a commandline browser.
22 | So You dont even need Any GUI Browser To Make it Work. 23 | 24 | ### How To Run 25 | 26 | ``` 27 | git clone https://github.com/TheSpeedX/TweetBot 28 | cd TweetBot 29 | python tweetbot.py 30 | ``` 31 | 32 | This Prevents You From Being Detected As Bot By Doing Human Like interaction And Random Delays. 33 | 34 | Note This Was Tested to Be Working on 01-10-2019 35 | -------------------------------------------------------------------------------- /greet: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | clear 3 | if [[ -s run ]];then 4 | rm run 5 | else 6 | echo -e "\e[4;31m SpeedX Productions !!! \e[0m" 7 | echo -e "\e[1;34m Presents \e[0m" 8 | echo -e "\e[1;32m TweetBot \e[0m" 9 | echo " " 10 | echo -e "\e[4;33m Tool For Sending Mass Tweets With Anti-Detection System. \e[0m" 11 | echo " " 12 | echo "Press Enter To Continue..." 13 | read a 14 | echo "This App is Running Since "$date >run 15 | echo "TweetBot Was Created By SpeedX... Any Queries Mail ggspeedx29@gmail.com " >>run 16 | fi 17 | if [[ -s update.speedx ]];then 18 | echo " " 19 | echo -e "\e[1;32m All Requirements Found... \e[0m" 20 | else 21 | echo " " 22 | echo -e "\e[1;32m Please Wait While We Install Necessary Requirements... \e[0m" 23 | echo " " 24 | echo " " 25 | apt update 26 | apt upgrade 27 | apt install figlet toilet lynx 28 | echo " " 29 | echo -e "\e[1;32m Requirements Installed Successfully... \e[0m" 30 | echo "This App Was Last Updated On "$date >update.speedx 31 | echo "SuperDorker Was Created By SpeedX... Any Queries Mail ggspeedx29@gmail.com " >>update.speedx 32 | echo "Press Enter To Continue.." 33 | read a1 34 | fi 35 | clear 36 | echo -e "\e[1;32m" 37 | figlet -f slant -c TweetBot 38 | echo -e "\e[1;34m Created By \e[0m" 39 | toilet -f mono12 -F gay SpeedX 40 | echo -e "\e[4;34m This Bot Was Created By SpeedX \e[0m" 41 | echo -e "\e[1;34m For Any Queries Mail Me!!!\e[0m" 42 | echo -e "\e[1;32m Mail: ggspeedx29@gmail.com \e[0m" 43 | echo -e "\e[4;32m Facebook Page: https://www.facebook.com/GyanaTech \e[0m" 44 | echo " " 45 | if [[ -s run ]];then 46 | echo -e "\e[1;33m This TweetBot is Still in Beta Mode\e[0m" 47 | echo -e "\e[1;32m Use it Carefully!!!" 48 | else 49 | echo -e "\e[1;33m Thanks For Using Twitter Bot !!\e[1;31m" 50 | figlet -f slant -c TweetBot 51 | echo "Created By SpeedX !!!!" 52 | toilet -f mono12 -F gay SpeedX 53 | echo -e "\e[1;34m For Any Queries Mail Me!!!\e[0m" 54 | echo -e "\e[1;32m Mail: ggspeedx29@gmail.com \e[0m" 55 | echo -e "\e[4;32m Facebook Page: https://www.facebook.com/GyanaTech \e[0m" 56 | fi 57 | -------------------------------------------------------------------------------- /lynx.cfg: -------------------------------------------------------------------------------- 1 | # $LynxId: lynx.cfg,v 1.302 2018/07/08 15:22:44 tom Exp $ 2 | # lynx.cfg file. 3 | # The default placement for this file is /usr/local/lib/lynx.cfg (Unix) 4 | # or Lynx_Dir:lynx.cfg (VMS) 5 | # 6 | # $Format: "#PRCS LYNX_VERSION \"$ProjectVersion$\""$ 7 | #PRCS LYNX_VERSION "2.8.9rel.1" 8 | # 9 | # $Format: "#PRCS LYNX_DATE \"$ProjectDate$\""$ 10 | #PRCS LYNX_DATE "Sun, 08 Jul 2018 06:46:06 -0400" 11 | # 12 | # Definition pairs (configuration settings) are of the form 13 | # VARIABLE:DEFINITION 14 | # NO spaces are allowed around the colon ":" between the pair items. 15 | # 16 | # If you do not have write access to /usr/local/lib you may change 17 | # the default location of this file in the userdefs.h file and recompile, 18 | # or specify its location on the command line with the "-cfg" 19 | # command line option. 20 | # 21 | # Items may be commented out by putting a '#' as the FIRST char of the line 22 | # (Any line beginning with punctuation is ignored). Leading blanks on each 23 | # line are ignored; trailing blanks may be significant depending on the option. 24 | 25 | # In most cases, a definition can be overridden by another later in the 26 | # file, or in an including configuration file. You can see the effect of 27 | # definitions (and redefinitions) in the trace file Lynx.log by using the 28 | # "-trace" and "-trace-mask" options, e.g., 29 | # lynx -trace -trace-mask=8 30 | 31 | # As a documentation aid, the default values for each setting are shown 32 | # commented-out. By convention, these default value comments have no space 33 | # after the "#", e.g., 34 | # #HTTP_PROTOCOL:1.0 35 | 36 | # An HTML'ized description of all settings (based on comments in this file, 37 | # with alphabetical table of settings and with table of settings by category) 38 | # is available at https://lynx.invisible-island.net/release/breakout/lynx_help/cattoc.html 39 | # 40 | ### The conversion is done via the scripts/cfg2html.pl script. 41 | ### Several directives beginning with '.' are used for this purpose. 42 | 43 | .h1 Auxiliary Facilities 44 | # These settings control the auxiliary navigating facilities of lynx, e.g., 45 | # jumpfiles, bookmarks, default URLs. 46 | 47 | .h2 INCLUDE 48 | # Starting with Lynx 2.8.1, the lynx.cfg file has a crude "include" 49 | # facility. This means that you can take advantage of the global lynx.cfg 50 | # while also supplying your own tweaks. 51 | # 52 | # You can use a command-line argument (-cfg /where/is/lynx.cfg) or an 53 | # environment variable (LYNX_CFG=/where/is/lynx.cfg). 54 | # For instance, put in your .profile or .login: 55 | # 56 | # LYNX_CFG=~/lynx.cfg; export LYNX_CFG # in .profile for sh/ksh/bash/etc. 57 | # setenv LYNX_CFG ~/lynx.cfg # in .login for [t]csh 58 | # 59 | # Then in ~/lynx.cfg: 60 | # 61 | # INCLUDE:/usr/local/lib/lynx.cfg 62 | # ^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system 63 | # and now your own tweaks. If you omit the directory name, e.g., 64 | # 65 | # INCLUDE:lynx.cfg 66 | # 67 | # then lynx first checks if it is in any of the directories listed in the 68 | # environment variable LYNX_CFG_PATH, then tries the directory of the default 69 | # config-file. 70 | # 71 | # You can also suppress all but specific settings that will be read from 72 | # included files. This allows sysadmins to provide users the ability to 73 | # customize lynx with options that normally do not affect security, such as 74 | # COLOR, VIEWER, KEYMAP. 75 | # 76 | # The syntax is 77 | # 78 | # INCLUDE:filename for 79 | # 80 | # sample: 81 | .ex 82 | #INCLUDE:~/lynx.cfg for COLOR VIEWER KEYMAP 83 | # only one space character should surround the word 'for'. On Unix systems ':' 84 | # is also accepted as separator. In that case, the example can be written as 85 | .ex 86 | #INCLUDE:~/lynx.cfg:COLOR VIEWER KEYMAP 87 | # In the example, only the settings COLOR, VIEWER and KEYMAP are accepted by 88 | # lynx. Other settings are ignored. Note: INCLUDE is also treated as a 89 | # setting, so to allow an included file to include other files, put INCLUDE in 90 | # the list of allowed settings. 91 | # 92 | # If you allow an included file to include other files, and if a list of 93 | # allowed settings is specified for that file with the INCLUDE command, nested 94 | # files are only allowed to include the list of settings that is the set AND of 95 | # settings allowed for the included file and settings allowed by nested INCLUDE 96 | # commands. In short, there is no security hole introduced by including a 97 | # user-defined configuration file if the original list of allowed settings is 98 | # secure. 99 | 100 | .h2 STARTFILE 101 | # STARTFILE is the default starting URL if none is specified 102 | # on the command line or via a WWW_HOME environment variable; 103 | # Lynx will refuse to start without a starting URL of some kind. 104 | # STARTFILE can be remote, e.g. http://www.w3.org/default.html , 105 | # or local, e.g. file://localhost/PATH_TO/FILENAME , 106 | # where PATH_TO is replaced with the complete path to FILENAME 107 | # using Unix shell syntax and including the device on VMS. 108 | # 109 | # Normally we expect you will connect to a remote site, e.g., the Lynx starting 110 | # site: 111 | STARTFILE:https://lynx.invisible-island.net/ 112 | # 113 | # As an alternative, you may want to use a local URL. A good choice for this is 114 | # the user's home directory: 115 | .ex 116 | #STARTFILE:file://localhost/~/ 117 | # 118 | # Your choice of STARTFILE should reflect your site's needs, and be a URL that 119 | # you can connect to reliably. Otherwise users will become confused and think 120 | # that they cannot run Lynx. 121 | 122 | .h2 HELPFILE 123 | # HELPFILE must be defined as a URL and must have a 124 | # complete path if local: 125 | # file://localhost/PATH_TO/lynx_help/lynx_help_main.html 126 | # Replace PATH_TO with the path to the lynx_help subdirectory 127 | # for this distribution (use SHELL syntax including the device 128 | # on VMS systems). 129 | # The default HELPFILE is: 130 | .url https://lynx.invisible-island.net/lynx_help/lynx_help_main.html 131 | # This should be changed to the local path. 132 | # This definition will be overridden if the "LYNX_HELPFILE" environment 133 | # variable has been set. 134 | # 135 | HELPFILE:https://lynx.invisible-island.net/lynx_help/lynx_help_main.html 136 | .ex 137 | #HELPFILE:file://localhost/PATH_TO/lynx_help/lynx_help_main.html 138 | 139 | .h2 DEFAULT_INDEX_FILE 140 | # DEFAULT_INDEX_FILE is the default file retrieved when the 141 | # user presses the 'I' key when viewing any document. 142 | # An index to your CWIS can be placed here or a document containing 143 | # pointers to lots of interesting places on the web. 144 | # 145 | DEFAULT_INDEX_FILE:http://scout.wisc.edu/ 146 | 147 | .h1 Interaction 148 | 149 | .h2 GOTOBUFFER 150 | # Set GOTOBUFFER to TRUE if you want to have the previous goto URL, 151 | # if any, offered for reuse or editing when using the 'g'oto command. 152 | # The default is defined in userdefs.h. If left FALSE, the circular 153 | # buffer of previously entered goto URLs can still be invoked via the 154 | # Up-Arrow or Down-Arrow keys after entering the 'g'oto command. 155 | # 156 | #GOTOBUFFER:FALSE 157 | 158 | .h2 JUMP_PROMPT 159 | # JUMP_PROMPT is the default statusline prompt for selecting a jumps file 160 | # shortcut. (see below). 161 | # You can change the prompt here from that defined in userdefs.h. Any 162 | # trailing white space will be trimmed, and a single space is added by Lynx 163 | # following the last non-white character. You must set the default prompt 164 | # before setting the default jumps file (below). If a default jumps file 165 | # was set via userdefs.h, and you change the prompt here, you must set the 166 | # default jumps file again (below) for the change to be implemented. 167 | # 168 | #JUMP_PROMPT:Jump to (use '?' for list): 169 | 170 | .h1 Auxiliary Facilities 171 | 172 | .h2 JUMPFILE 173 | # JUMPFILE is the local file checked for short-cut names for URLs when 174 | # the user presses the 'j' (JUMP) key. The file contains an HTML 175 | # definition list (DL). The definition titles (DT) are used as 176 | # short-cut name; the definition data (DD) are URLs. 177 | # 178 | # There is an example jumps file in the samples subdirectory. 179 | # 180 | # After pressing 'j', the user will be prompted to enter a short-cut 181 | # name for an URL, which Lynx will then follow in a similar manner to 182 | # 'g'oto; alternatively, s/he can enter '?' to view the full JUMPFILE 183 | # list of short-cuts with associated URLs. 184 | # 185 | # If the URL contains one or more "%s" markers, Lynx will prompt the user 186 | # for text to fill in for each marker. If no text is given, the jump is 187 | # cancelled. 188 | # 189 | # If not defined here or in userdefs.h, the JUMP command will invoke the 190 | # NO_JUMPFILE statusline message (see LYMessages_en.h ). 191 | # 192 | # To allow '?' to work, include in the JUMPFILE 193 | # a short-cut to the JUMPFILE itself, e.g. 194 | #
?
This Shortcut List 195 | # 196 | # On VMS, use Unix SHELL syntax (including a lead slash) to define it. 197 | # 198 | # Alternate jumps files can be defined and mapped to keys here. If the 199 | # keys have already been mapped, then those mappings will be replaced, 200 | # but you should leave at least one key mapped to the default jumps 201 | # file. You optionally may include a statusline prompt string for the 202 | # mapping. You must map upper and lowercase keys separately (beware of 203 | # mappings to keys which the user can further remap via the 'o'ptions 204 | # menu). The format is: 205 | # 206 | # JUMPFILE:path:key[:prompt] 207 | # 208 | # where path should begin with a '/' (i.e., not include file://localhost). 209 | # Any white space following a prompt string will be trimmed, and a single 210 | # space will be added by Lynx. 211 | # 212 | # In the following line, include the actual full local path to JUMPFILE, 213 | # but do not include 'file://localhost' in the line. 214 | #JUMPFILE:/FULL_LOCAL_PATH/jumps.html 215 | .ex 216 | #JUMPFILE:/Lynx_Dir/ips.html:i:IP or Interest group (? for list): 217 | 218 | .h2 JUMPBUFFER 219 | # Set JUMPBUFFER to TRUE if you want to have the previous jump target, 220 | # if any, offered for reuse or editing when using the 'J'ump command. 221 | # The default is defined in userdefs.h. If left FALSE, the circular 222 | # buffer of previously entered targets (shortcuts) can still be invoked 223 | # via the Up-Arrow or Down-Arrow keys after entering the 'J'ump command. 224 | # If multiple jumps files are installed, the recalls of shortcuts will 225 | # be specific to each file. If Lynx was built with PERMIT_GOTO_FROM_JUMP 226 | # defined, any random URLs used instead of shortcuts will be stored in the 227 | # goto URL buffer, not in the shortcuts buffer(s), and the single character 228 | # ':' can be used as a target to invoke the goto URL buffer (as if 'g'oto 229 | # followed by Up-Arrow had been entered). 230 | # 231 | #JUMPBUFFER:FALSE 232 | 233 | .h1 Internal Behavior 234 | 235 | .h2 SAVE_SPACE 236 | # If SAVE_SPACE is defined, it will be used as a path prefix for the 237 | # suggested filename in "Save to Disk" operations from the 'p'rint or 238 | # 'd'ownload menus. On VMS, you can use either VMS (e.g., "SYS$LOGIN:") 239 | # or Unix syntax (including '~' for the HOME directory). On Unix, you 240 | # must use Unix syntax. If the symbol is not defined, or is zero-length 241 | # (""), no prefix will be used, and only a filename for saving in the 242 | # current default directory will be suggested. 243 | # This definition will be overridden if a "LYNX_SAVE_SPACE" environment 244 | # variable has been set on Unix, or logical has been defined on VMS. 245 | # 246 | #SAVE_SPACE:~/foo/ 247 | 248 | .h2 REUSE_TEMPFILES 249 | # Lynx uses temporary files for (among other purposes) the content of 250 | # various user interface pages. REUSE_TEMPFILES changes the behavior 251 | # for some of these temp files, among them pages shown for HISTORY, 252 | # VLINKS, OPTIONS, INFO, PRINT, DOWNLOAD commands. 253 | # If set to TRUE, the same file can be used multiple times for the same 254 | # purpose. If set to FALSE, a new filename is generated each time before 255 | # rewriting such a page. With TRUE, repeated invocation of these commands 256 | # is less likely to push previous documents out of the cache of rendered 257 | # texts (see also DEFAULT_CACHE_SIZE). This is especially useful with 258 | # intermittent (dialup) network connections, when it is desirable to 259 | # continue browsing through the cached documents after disconnecting. 260 | # With the default setting of FALSE, there can be more than one incarnation 261 | # of e.g. the VLINKS page cached in memory (but still only the most recently 262 | # generated one is kept as a file), resulting in sometimes less surprising 263 | # behaviour when returning to such a page via HISTORY or PREV_DOC functions 264 | # (most users will not encounter and notice this difference). 265 | # 266 | #REUSE_TEMPFILES:FALSE 267 | 268 | .h2 LYNX_HOST_NAME 269 | # If LYNX_HOST_NAME is defined here or in userdefs.h, it will be 270 | # treated as an alias for the local host name in checks for URLs on 271 | # the local host (e.g., when the -localhost switch is set), and this 272 | # host name, "localhost", and HTHostName (the fully qualified domain 273 | # name of the system on which Lynx is running) will all be passed as 274 | # local. A different definition here will override that in userdefs.h. 275 | # 276 | #LYNX_HOST_NAME:www.cc.ukans.edu 277 | 278 | .h2 LOCALHOST_ALIAS 279 | # localhost aliases 280 | # Any LOCALHOST_ALIAS definitions also will be accepted as local when 281 | # the -localhost switch is set. These need not actually be local, i.e., 282 | # in contrast to LYNX_HOST_NAME, you can define them to trusted hosts at 283 | # other Internet sites. 284 | # 285 | .ex 2 286 | #LOCALHOST_ALIAS:gopher.server.domain 287 | #LOCALHOST_ALIAS:news.server.domain 288 | 289 | .h2 LOCAL_DOMAIN 290 | # LOCAL_DOMAIN is used for a tail match with the ut_host element of 291 | # the utmp or utmpx structure on systems with utmp capabilities, to 292 | # determine if a user is local to your campus or organization when 293 | # handling -restrictions=inside_foo or outside_foo settings for ftp, 294 | # news, telnet/tn3270 and rlogin URLs. An "inside" user is assumed 295 | # if your system does not have utmp capabilities. CHANGE THIS here 296 | # if it was not changed in userdefs.h at compilation time. 297 | # 298 | #LOCAL_DOMAIN:ukans.edu 299 | 300 | .h1 Session support 301 | 302 | .h2 AUTO_SESSION 303 | # If AUTO_SESSION is TRUE lynx will save/restore useful information about 304 | # your browsing history when closing/starting current lynx session if 305 | # no command-line session switches override this setting. 306 | # This setting is useful only if SESSION_FILE is defined here or in the user's 307 | # .lynxrc file. 308 | # 309 | AUTO_SESSION:TRUE 310 | 311 | .h2 SESSION_FILE 312 | # SESSION_FILE defines the file name where lynx will store user sessions. 313 | # This setting is used only when AUTO_SESSION is true. 314 | # Note: the default setting will store/resume each session in a different 315 | # folder under same file name (if that is allowed by operating system) 316 | # when lynx is invoked from different directories. 317 | # (The current working directory may be changed inside lynx) 318 | # 319 | # If you want to use the same session file wherever you invoke Lynx, 320 | # enter the full path below, eg '/home//.lynx_session'. 321 | # 322 | # If you do not want this feature, leave the setting commented. 323 | # Users can still customize SESSION_FILE and AUTO_SESSION via 324 | # their .lynxrc file. 325 | # 326 | SESSION_FILE:lynx_session 327 | 328 | .h2 SESSION_LIMIT 329 | # SESSION_LIMIT defines maximum number of: searched strings, goto URLs, 330 | # visited links and history entries which will be saved in session file. The 331 | # minimum allowed is 1, the maximum is 10000. 332 | # 333 | # For instance, if SESSION_LIMIT is 250, a per-session limit of 250 entries of 334 | # searched strings, goto URLs, visited links and history entries will be saved 335 | # in the session file. 336 | # 337 | # There is no fixed limit on the number of entries which can be restored; 338 | # It is limited only by available memory. 339 | # 340 | #SESSION_LIMIT:250 341 | 342 | .h1 Character Sets 343 | 344 | .h2 CHARACTER_SET 345 | # CHARACTER_SET defines the display character set, i.e., assumed to be 346 | # installed on the user's terminal. It determines which characters or strings 347 | # will be used to represent 8-bit character entities within HTML. New 348 | # character sets may be defined as explained in the README files of the 349 | # src/chrtrans directory in the Lynx source code distribution. For Asian (CJK) 350 | # character sets, it also determines how Kanji code will be handled. The 351 | # default is defined in userdefs.h and can be changed here or via the 352 | # 'o'ptions menu. The 'o'ptions menu setting will be stored in the user's RC 353 | # file whenever those settings are saved, and thereafter will be used as the 354 | # default. For Lynx a "character set" has two names: a MIME name (for 355 | # recognizing properly labeled charset parameters in HTTP headers etc.), and a 356 | # human-readable string for the 'O'ptions Menu (so you may find info about 357 | # language or group of languages besides MIME name). Not all 'human-readable' 358 | # names correspond to exactly one valid MIME charset (example is "Chinese"); 359 | # in that case an appropriate valid (and more specific) MIME name should be 360 | # used where required. Well-known synonyms are also processed in the code. 361 | # 362 | # Raw (CJK) mode 363 | # 364 | # Lynx normally translates characters from a document's charset to display 365 | # charset, using ASSUME_CHARSET value (see below) if the document's charset 366 | # is not specified explicitly. Raw (CJK) mode is OFF for this case. 367 | # When the document charset is specified explicitly, that charset 368 | # overrides any assumption like ASSUME_CHARSET or raw (CJK) mode. 369 | # 370 | # For the Asian (CJK) display character sets, the corresponding charset is 371 | # assumed in documents, i.e., raw (CJK) mode is ON by default. In raw CJK 372 | # mode, 8-bit characters are not reverse translated in relation to the entity 373 | # conversion arrays, i.e., they are assumed to be appropriate for the display 374 | # character set. The mode should be toggled OFF when an Asian (CJK) display 375 | # character set is selected but the document is not CJK and its charset not 376 | # specified explicitly. 377 | # 378 | # Raw (CJK) mode may be toggled by user via '@' (LYK_RAW_TOGGLE) key, 379 | # the -raw command line switch or from the 'o'ptions menu. 380 | # 381 | # Raw (CJK) mode effectively changes the charset assumption about unlabeled 382 | # documents. You can toggle raw mode ON if you believe the document has a 383 | # charset which does correspond to your Display Character Set. On the other 384 | # hand, if you set ASSUME_CHARSET the same as Display Character Set you get raw 385 | # mode ON by default (but you get assume_charset=iso-8859-1 if you try raw mode 386 | # OFF after it). 387 | # 388 | # Note that "raw" does not mean that every byte will be passed to the screen. 389 | # HTML character entities may get expanded and translated, inappropriate 390 | # control characters filtered out, etc. There is a "Transparent" pseudo 391 | # character set for more "rawness". 392 | # 393 | # Since Lynx now supports a wide range of platforms it may be useful to note 394 | # the cpXXX codepages used by IBM PC compatible computers, and windows-xxxx 395 | # used by native MS-Windows apps. We also note that cpXXX pages rarely are 396 | # found on Internet, but are mostly for local needs on DOS. 397 | # 398 | # Recognized character sets include: 399 | # 400 | .nf 401 | # string for 'O'ptions Menu MIME name 402 | # =========================== ========= 403 | # 7 bit approximations (US-ASCII) us-ascii 404 | # Western (ISO-8859-1) iso-8859-1 405 | # Western (ISO-8859-15) iso-8859-15 406 | # Western (cp850) cp850 407 | # Western (windows-1252) windows-1252 408 | # IBM PC US codepage (cp437) cp437 409 | # DEC Multinational dec-mcs 410 | # Macintosh (8 bit) macintosh 411 | # NeXT character set next 412 | # HP Roman8 hp-roman8 413 | # Chinese euc-cn 414 | # Japanese (EUC-JP) euc-jp 415 | # Japanese (Shift_JIS) shift_jis 416 | # Korean euc-kr 417 | # Taipei (Big5) big5 418 | # Vietnamese (VISCII) viscii 419 | # Eastern European (ISO-8859-2) iso-8859-2 420 | # Eastern European (cp852) cp852 421 | # Eastern European (windows-1250) windows-1250 422 | # Latin 3 (ISO-8859-3) iso-8859-3 423 | # Latin 4 (ISO-8859-4) iso-8859-4 424 | # Baltic Rim (ISO-8859-13) iso-8859-13 425 | # Baltic Rim (cp775) cp775 426 | # Baltic Rim (windows-1257) windows-1257 427 | # Celtic (ISO-8859-14) iso-8859-14 428 | # Cyrillic (ISO-8859-5) iso-8859-5 429 | # Cyrillic (cp866) cp866 430 | # Cyrillic (windows-1251) windows-1251 431 | # Cyrillic (KOI8-R) koi8-r 432 | # Arabic (ISO-8859-6) iso-8859-6 433 | # Arabic (cp864) cp864 434 | # Arabic (windows-1256) windows-1256 435 | # Greek (ISO-8859-7) iso-8859-7 436 | # Greek (cp737) cp737 437 | # Greek2 (cp869) cp869 438 | # Greek (windows-1253) windows-1253 439 | # Hebrew (ISO-8859-8) iso-8859-8 440 | # Hebrew (cp862) cp862 441 | # Hebrew (windows-1255) windows-1255 442 | # Turkish (ISO-8859-9) iso-8859-9 443 | # North European (ISO-8859-10) iso-8859-10 444 | # Ukrainian Cyrillic (cp866u) cp866u 445 | # Ukrainian Cyrillic (KOI8-U) koi8-u 446 | # UNICODE (UTF-8) utf-8 447 | # RFC 1345 w/o Intro mnemonic+ascii+0 448 | # RFC 1345 Mnemonic mnemonic 449 | # Transparent x-transparent 450 | .fi 451 | # 452 | # The value should be the MIME name of a character set recognized by 453 | # Lynx (case insensitive). 454 | # Find RFC 1345 at 455 | .url http://tools.ietf.org/html/rfc1345 456 | # 457 | #CHARACTER_SET:iso-8859-1 458 | 459 | .h2 LOCALE_CHARSET 460 | # LOCALE_CHARSET overrides CHARACTER_SET if true, using the current locale to 461 | # lookup a MIME name that corresponds, and use that as the display charset. 462 | # 463 | # It also modifies the default value for ASSUME_CHARSET; it does not override 464 | # that setting. 465 | # 466 | # Note that while nl_langinfo(CODESET) itself is standardized, the return 467 | # values and their relationship to the locale value is not. GNU libiconv 468 | # happens to give useful values, but other implementations are not guaranteed 469 | # to do this. 470 | #LOCALE_CHARSET:FALSE 471 | 472 | .h2 HTML5_CHARSETS 473 | # HTML5_CHARSETS is an alternative to ASSUME_CHARSET and ASSUME_LOCAL_CHARSET. 474 | # Those assume by default that the character set of an HTML document is (as is 475 | # standard in HTML4) ISO-8859-1, in the absence of locale information. 476 | # 477 | # HTML5 introduces a "compatibility" (sic) feature which assumes that the 478 | # default is Windows 1252. In the same way, it equates ISO-8859-4 and Windows 479 | # 1254. Finally, it also makes recommendations which selectively reinterpret 480 | # the locale encoding. 481 | # 482 | # This option currently implements only the equating of ISO-8859-1 and Windows 483 | # 1252. 484 | # 485 | #HTML5_CHARSETS:FALSE 486 | 487 | .h2 ASSUME_CHARSET 488 | # ASSUME_CHARSET changes the handling of documents which do not 489 | # explicitly specify a charset. Normally Lynx assumes that 8-bit 490 | # characters in those documents are encoded according to iso-8859-1 491 | # (the official default for the HTTP protocol). When ASSUME_CHARSET 492 | # is defined here or by an -assume_charset command line flag is in effect, 493 | # Lynx will treat documents as if they were encoded accordingly. 494 | # See above on how this interacts with "raw mode" and the Display 495 | # Character Set. 496 | # ASSUME_CHARSET can also be changed via the 'o'ptions menu but will 497 | # not be saved as permanent value in user's .lynxrc file to avoid more chaos. 498 | # 499 | #ASSUME_CHARSET:iso-8859-1 500 | 501 | .h2 ASSUMED_DOC_CHARSET_CHOICE 502 | .h2 DISPLAY_CHARSET_CHOICE 503 | # It is possible to reduce the number of charset choices in the 'O'ptions menu 504 | # for "display charset" and "assumed document charset" fields via 505 | # DISPLAY_CHARSET_CHOICE and ASSUMED_DOC_CHARSET_CHOICE settings correspondingly. 506 | # Each of these settings can be used several times to define the set of possible 507 | # choices for corresponding field. The syntax for the values is 508 | # 509 | # string | prefix* | * 510 | # 511 | # where 512 | # 513 | # 'string' is either the MIME name of charset or it's full name (listed 514 | # either in the left or in the right column of table of 515 | # recognized charsets), case-insensitive - e.g. 'Koi8-R' or 516 | # 'Cyrillic (KOI8-R)' (both without quotes), 517 | # 518 | # 'prefix' is any string, and such value will select all charsets having 519 | # the name with prefix matching given (case insensitive), i.e., 520 | # for the charsets listed in the table of recognized charsets, 521 | # 522 | .ex 523 | # ASSUMED_DOC_CHARSET_CHOICE:cyrillic* 524 | # will be equal to specifying 525 | .ex 4 526 | # ASSUMED_DOC_CHARSET_CHOICE:cp866 527 | # ASSUMED_DOC_CHARSET_CHOICE:windows-1251 528 | # ASSUMED_DOC_CHARSET_CHOICE:koi8-r 529 | # ASSUMED_DOC_CHARSET_CHOICE:iso-8859-5 530 | # or lines with full names of charsets. 531 | # 532 | # literal string '*' (without quotes) will enable all charset choices 533 | # in corresponding field. This is useful for overriding site 534 | # defaults in private pieces of lynx.cfg included via INCLUDE 535 | # directive. 536 | # 537 | # Default values for both settings are '*', but any occurrence of settings 538 | # with values that denote any charsets will make only listed choices available 539 | # for corresponding field. 540 | #ASSUMED_DOC_CHARSET_CHOICE:* 541 | #DISPLAY_CHARSET_CHOICE:* 542 | 543 | .h2 ASSUME_LOCAL_CHARSET 544 | # ASSUME_LOCAL_CHARSET is like ASSUME_CHARSET but only applies to local 545 | # files. If no setting is given here or by an -assume_local_charset 546 | # command line option, the value for ASSUME_CHARSET or -assume_charset 547 | # is used. It works for both text/plain and text/html files. 548 | # This option will ignore "raw mode" toggling when local files are viewed 549 | # (it is "stronger" than "assume_charset" or the effective change 550 | # of the charset assumption caused by changing "raw mode"), 551 | # so only use when necessary. 552 | # 553 | #ASSUME_LOCAL_CHARSET:iso-8859-1 554 | 555 | .h2 PREPEND_CHARSET_TO_SOURCE 556 | # PREPEND_CHARSET_TO_SOURCE:TRUE tells Lynx to prepend a META CHARSET line 557 | # to text/html source files when they are retrieved for 'd'ownloading 558 | # or passed to 'p'rint functions, so HTTP headers will not be lost. 559 | # This is necessary for resolving charset for local html files, 560 | # while the assume_local_charset is just an assumption. 561 | # For the 'd'ownload option, a META CHARSET will be added only if the HTTP 562 | # charset is present. The compilation default is TRUE. 563 | # It is generally desirable to have charset information for every local 564 | # html file, but META CHARSET string potentially could cause 565 | # compatibility problems with other browsers, see also PREPEND_BASE_TO_SOURCE. 566 | # Note that the prepending is not done for -source dumps. 567 | # 568 | #PREPEND_CHARSET_TO_SOURCE:TRUE 569 | 570 | .h2 NCR_IN_BOOKMARKS 571 | # NCR_IN_BOOKMARKS:TRUE allows you to save 8-bit characters in bookmark titles 572 | # in the unicode format (NCR). This may be useful if you need to switch 573 | # display charsets frequently. This is the case when you use Lynx on different 574 | # platforms, e.g., on UNIX and from a remote PC, and want to keep the bookmarks 575 | # file persistent. 576 | # Another aspect is compatibility: NCR is part of I18N and HTML4.0 577 | # specifications supported starting with Lynx 2.7.2, Netscape 4.0 and MSIE 4.0. 578 | # Older browser versions will fail so keep NCR_IN_BOOKMARKS:FALSE if you 579 | # plan to use them. 580 | # 581 | #NCR_IN_BOOKMARKS:FALSE 582 | 583 | .h2 FORCE_8BIT_TOUPPER 584 | # FORCE_8BIT_TOUPPER overrides locale settings and uses internal 8-bit 585 | # case-conversion mechanism for case-insensitive searches in non-ASCII display 586 | # character sets. It is FALSE by default and should not be changed unless 587 | # you encounter problems with case-insensitive searches. 588 | # 589 | #FORCE_8BIT_TOUPPER:FALSE 590 | 591 | .h2 OUTGOING_MAIL_CHARSET 592 | # While Lynx supports different platforms and display character sets 593 | # we need to limit the charset in outgoing mail to reduce 594 | # trouble for remote recipients who may not recognize our charset. 595 | # You may try US-ASCII as the safest value (7 bit), any other MIME name, 596 | # or leave this field blank (default) to use the display character set. 597 | # Charset translations currently are implemented for mail "subjects= " only. 598 | # 599 | #OUTGOING_MAIL_CHARSET: 600 | 601 | .h2 ASSUME_UNREC_CHARSET 602 | # If Lynx encounters a charset parameter it doesn't recognize, it will 603 | # replace the value given by ASSUME_UNREC_CHARSET (or a corresponding 604 | # -assume_unrec_charset command line option) for it. This can be used 605 | # to deal with charsets unknown to Lynx, if they are "sufficiently 606 | # similar" to one that Lynx does know about, by forcing the same 607 | # treatment. There is no default, and you probably should leave this 608 | # undefined unless necessary. 609 | # 610 | #ASSUME_UNREC_CHARSET:iso-8859-1 611 | 612 | .h2 PREFERRED_LANGUAGE 613 | # PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en", 614 | # "fr") which will be indicated by Lynx in its Accept-Language headers 615 | # as the preferred language. If available, the document will be 616 | # transmitted in that language. Users can override this setting via 617 | # the 'o'ptions menu and save that preference in their RC file. 618 | # This may be a comma-separated list of languages in decreasing preference. 619 | # 620 | #PREFERRED_LANGUAGE:en 621 | 622 | .h2 PREFERRED_CHARSET 623 | # PREFERRED_CHARSET specifies the character set in MIME notation (e.g., 624 | # "ISO-8859-2", "ISO-8859-5") which Lynx will indicate you prefer in 625 | # requests to http servers using an Accept-Charsets header. Users can 626 | # change it via the 'o'ptions menu and save that preference in their RC file. 627 | # The value should NOT include "ISO-8859-1" or "US-ASCII", 628 | # since those values are always assumed by default. 629 | # If a file in that character set is available, the server will send it. 630 | # If no Accept-Charset header is present, the default is that any 631 | # character set is acceptable. If an Accept-Charset header is present, 632 | # and if the server cannot send a response which is acceptable 633 | # according to the Accept-Charset header, then the server SHOULD send 634 | # an error response with the 406 (not acceptable) status code, though 635 | # the sending of an unacceptable response is also allowed. See RFC 2068 636 | .url http://tools.ietf.org/html/rfc2068 637 | # 638 | #PREFERRED_CHARSET: 639 | 640 | .h2 CHARSETS_DIRECTORY 641 | # CHARSETS_DIRECTORY specifies the directory with the fonts (glyph data) 642 | # used by Lynx to switch the display-font to a font best suited for the 643 | # given document. The font should be in a format understood by the 644 | # platforms TTY-display-font-switching API. Currently supported on OS/2 only. 645 | # 646 | # Lynx expects the glyphs for the charset CHARSET with character cell 647 | # size HHHxWWW to be stored in a file HHHxWWW/CHARSET.fnt inside the directory 648 | # specified by CHARSETS_DIRECTORY. E.g., the font for koi8-r sized 14x9 649 | # should be in the file 14x9/koi8-r.fnt. 650 | # 651 | #CHARSETS_DIRECTORY: 652 | 653 | .h2 CHARSET_SWITCH_RULES 654 | # CHARSET_SWITCH_RULES hints lynx on how to choose the best display font given 655 | # the document encoding. This string is a sequence of chunks, each chunk 656 | # having the following form: 657 | # 658 | # IN_CHARSET1 IN_CHARSET2 ... IN_CHARSET5 :OUT_CHARSET 659 | # 660 | # For readability, one may insert arbitrary additional punctuation (anything 661 | # but : is ignored). E.g., if lynx is able to switch only to display charsets 662 | # cp866, cp850, cp852, and cp862, then the following setting may be useful 663 | # (split for readability): 664 | # 665 | # CHARSET_SWITCH_RULES: koi8-r ISO-8859-5 windows-1251 cp866u KOI8-U :cp866, 666 | # iso-8859-1 windows-1252 ISO-8859-15 :cp850, 667 | # ISO-8859-2 windows-1250 :cp852, 668 | # ISO-8859-8 windows-1255 :cp862 669 | # 670 | #CHARSET_SWITCH_RULES: 671 | 672 | .h1 Interaction 673 | 674 | .h2 URL_DOMAIN_PREFIXES 675 | .h2 URL_DOMAIN_SUFFIXES 676 | # URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES are strings which will be 677 | # prepended (together with a scheme://) and appended to the first element 678 | # of command line or 'g'oto arguments which are not complete URLs and 679 | # cannot be opened as a local file (file://localhost/string). Both 680 | # can be comma-separated lists. Each prefix must end with a dot, each 681 | # suffix must begin with a dot, and either may contain other dots (e.g., 682 | # .com.jp). The default lists are defined in userdefs.h and can be 683 | # replaced here. Each prefix will be used with each suffix, in order, 684 | # until a valid Internet host is created, based on a successful DNS 685 | # lookup (e.g., foo will be tested as www.foo.com and then www.foo.edu 686 | # etc.). The first element can include a :port and/or /path which will 687 | # be restored with the expanded host (e.g., wfbr:8002/dir/lynx will 688 | # become http://www.wfbr.edu:8002/dir/lynx). The prefixes will not be 689 | # used if the first element ends in a dot (or has a dot before the 690 | # :port or /path), and similarly the suffixes will not be used if the 691 | # the first element begins with a dot (e.g., .nyu.edu will become 692 | # http://www.nyu.edu without testing www.nyu.com). Lynx will try to 693 | # guess the scheme based on the first field of the expanded host name, 694 | # and use "http://" as the default (e.g., gopher.wfbr.edu or gopher.wfbr. 695 | # will be made gopher://gopher.wfbr.edu). 696 | # 697 | #URL_DOMAIN_PREFIXES:www. 698 | #URL_DOMAIN_SUFFIXES:.com,.edu,.net,.org 699 | 700 | .h2 FORMS_OPTIONS 701 | # Toggle whether the Options Menu is key-based or form-based; 702 | # the key-based version is available only if specified at compile time. 703 | #FORMS_OPTIONS:TRUE 704 | 705 | .h2 PARTIAL 706 | # Display partial pages while downloading 707 | #PARTIAL:TRUE 708 | 709 | .h2 PARTIAL_THRES 710 | # Set the threshold # of lines Lynx must render before it 711 | # redraws the screen in PARTIAL mode. Anything < 0 implies 712 | # use of the screen size. 713 | #PARTIAL_THRES:-1 714 | 715 | .h2 SHOW_KB_RATE 716 | # While getting large files, Lynx shows the approximate rate of transfer. 717 | # Set this to change the units shown. "Kilobytes" denotes 1024 bytes: 718 | # NONE to disable the display of transfer rate altogether. 719 | # TRUE or KB for Kilobytes/second. 720 | # FALSE or BYTES for bytes/second. 721 | # KB,ETA to show Kilobytes/second with estimated completion time. 722 | # BYTES,ETA to show BYTES/second with estimated completion time. 723 | # KB2,ETA to show Kilobytes/second with estimated completion time using 2-digits. 724 | # BYTES2,ETA to show BYTES/second with estimated completion time using 2-digits. 725 | # Note that the "ETA" values are available if USE_READPROGRESS was defined. 726 | #SHOW_KB_RATE:TRUE 727 | 728 | .h2 SHOW_KB_NAME 729 | # Set the abbreviation for Kilobytes (1024). 730 | # Quoting from 731 | .url http://www.romulus2.com/articles/guides/misc/bitsbytes.shtml 732 | # In December 1998, the International Electrotechnical Commission (IEC) 733 | # approved a new IEC International Standard. Instead of using the metric 734 | # prefixes for multiples in binary code, the new IEC standard invented specific 735 | # prefixes for binary multiples made up of only the first two letters of the 736 | # metric prefixes and adding the first two letters of the word "binary". Thus, 737 | # for instance, instead of Kilobyte (KB) or Gigabyte (GB), the new terms would 738 | # be kibibyte (KiB) or gibibyte (GiB). 739 | # 740 | # If you prefer using the conventional (and more common) "KB", modify this 741 | # setting. 742 | #SHOW_KB_NAME:KiB 743 | 744 | .h1 Timeouts 745 | 746 | .h2 INFOSECS 747 | .h2 MESSAGESECS 748 | .h2 ALERTSECS 749 | .h2 NO_PAUSE 750 | # The following definitions set the number of seconds for 751 | # pauses following statusline messages that would otherwise be 752 | # replaced immediately, and are more important than the unpaused 753 | # progress messages. Those set by INFOSECS are also basically 754 | # progress messages (e.g., that a prompted input has been canceled) 755 | # and should have the shortest pause. Those set by MESSAGESECS are 756 | # informational (e.g., that a function is disabled) and should have 757 | # a pause of intermediate duration. Those set by ALERTSECS typically 758 | # report a serious problem and should be paused long enough to read 759 | # whenever they appear (typically unexpectedly). The default values 760 | # are defined in userdefs.h, and can be modified here should longer 761 | # pauses be desired for braille-based access to Lynx. 762 | # 763 | # SVr4-curses implementations support time delays in milliseconds, 764 | # hence the value may be given shorter, e.g., 0.5 765 | # 766 | # Use the NO_PAUSE option (like the command-line -nopause) to override 767 | # all of the delay times. 768 | # 769 | #INFOSECS:1 770 | #MESSAGESECS:2 771 | #ALERTSECS:3 772 | #NO_PAUSE:FALSE 773 | 774 | .h2 DEBUGSECS 775 | # Set DEBUGSECS to a nonzero value to slow down progress messages 776 | # (see "-delay" option). 777 | #DEBUGSECS:0 778 | 779 | .h2 REPLAYSECS 780 | # Set REPLAYSECS to a nonzero value to allow for slow replaying of 781 | # command scripts (see "-cmd_script" option). 782 | #REPLAYSECS:0 783 | 784 | .h1 Appearance 785 | # These settings control the appearance of Lynx's screen and the way 786 | # Lynx renders some tags. 787 | 788 | .h2 USE_SELECT_POPUPS 789 | # If USE_SELECT_POPUPS is set FALSE, Lynx will present a vertical list of 790 | # radio buttons for the OPTIONs in SELECT blocks which lack the MULTIPLE 791 | # attribute, instead of using a popup menu. Note that if the MULTIPLE 792 | # attribute is present in the SELECT start tag, Lynx always will create a 793 | # vertical list of checkboxes for the OPTIONs. 794 | # The default defined here or in userdefs.h can be changed via the 'o'ptions 795 | # menu and saved in the RC file, and always can be toggled via the -popup 796 | # command line switch. 797 | # 798 | #USE_SELECT_POPUPS:TRUE 799 | 800 | .h2 SHOW_CURSOR 801 | # SHOW_CURSOR controls whether or not the cursor is hidden or appears 802 | # over the current link in documents or the current option in popups. 803 | # Showing the cursor is handy if you are a sighted user with a poor 804 | # terminal that can't do bold and reverse video at the same time or 805 | # at all. It also can be useful to blind users, as an alternative 806 | # or supplement to setting LINKS_AND_FIELDS_ARE_NUMBERED or 807 | # LINKS_ARE_NUMBERED. 808 | # The default defined here or in userdefs.h can be changed via the 809 | # 'o'ptions menu and saved in the RC file, and always can be toggled 810 | # via the -show_cursor command line switch. 811 | # 812 | #SHOW_CURSOR:FALSE 813 | 814 | .h2 UNDERLINE_LINKS 815 | # UNDERLINE_LINKS controls whether links are underlined by default, or shown 816 | # in bold. Normally this default is set from the configure script. 817 | # 818 | #UNDERLINE_LINKS:FALSE 819 | 820 | .h2 BOLD_HEADERS 821 | # If BOLD_HEADERS is set to TRUE the HT_BOLD default style will be acted 822 | # upon for

through

headers. The compilation default is FALSE 823 | # (only the indentation styles are acted upon, but see BOLD_H1, below). 824 | # On Unix, compilation with -DUNDERLINE_LINKS also will apply to the 825 | # HT_BOLD style for headers when BOLD_HEADERS is TRUE. 826 | # 827 | #BOLD_HEADERS:FALSE 828 | 829 | .h2 BOLD_H1 830 | # If BOLD_H1 is set to TRUE the HT_BOLD default style will be acted 831 | # upon for

headers even if BOLD_HEADERS is FALSE. The compilation 832 | # default is FALSE. On Unix, compilation with -DUNDERLINE_LINKS also 833 | # will apply to the HT_BOLD style for headers when BOLD_H1 is TRUE. 834 | # 835 | #BOLD_H1:FALSE 836 | 837 | .h2 BOLD_NAME_ANCHORS 838 | # If BOLD_NAME_ANCHORS is set to TRUE the content of anchors without 839 | # an HREF attribute, (i.e., anchors with a NAME or ID attribute) will 840 | # have the HT_BOLD default style. The compilation default is FALSE. 841 | # On Unix, compilation with -DUNDERLINE_LINKS also will apply to the 842 | # HT_BOLD style for NAME (ID) anchors when BOLD_NAME_ANCHORS is TRUE. 843 | # 844 | #BOLD_NAME_ANCHORS:FALSE 845 | 846 | .h1 Internal Behavior 847 | 848 | .h2 DEFAULT_CACHE_SIZE 849 | .h2 DEFAULT_VIRTUAL_MEMORY_SIZE 850 | # The DEFAULT_CACHE_SIZE specifies the number of WWW documents to be 851 | # cached in memory at one time. 852 | # 853 | # This so-called cache size (actually, number) is defined in userdefs.h and 854 | # may be modified here and/or with the command line argument -cache=NUMBER 855 | # The minimum allowed value is 2, for the current document and at least one 856 | # to fetch, and there is no absolute maximum number of cached documents. 857 | # On Unix, and VMS not compiled with VAXC, whenever the number is exceeded 858 | # the least recently displayed document will be removed from memory. 859 | # 860 | # On VMS compiled with VAXC, the DEFAULT_VIRTUAL_MEMORY_SIZE specifies the 861 | # amount (bytes) of virtual memory that can be allocated and not yet be freed 862 | # before previous documents are removed from memory. If the values for both 863 | # the DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE are exceeded, then 864 | # the least recently displayed documents will be freed until one or the other 865 | # value is no longer exceeded. The default value is defined in userdefs.h. 866 | # 867 | # The Unix and VMS (but not VAXC) implementations use the C library malloc's 868 | # and calloc's for memory allocation, but procedures for taking the actual 869 | # amount of cache into account still need to be developed. They use only 870 | # the DEFAULT_CACHE_SIZE value, and that specifies the absolute maximum 871 | # number of documents to cache (rather than the maximum number only if 872 | # DEFAULT_VIRTUAL_MEMORY_SIZE has been exceeded, as with VAXC/VAX). 873 | # 874 | #DEFAULT_CACHE_SIZE:10 875 | #DEFAULT_VIRTUAL_MEMORY_SIZE:512000 876 | 877 | .h2 SOURCE_CACHE 878 | # SOURCE_CACHE sets the source caching behavior for Lynx: 879 | # 880 | # FILE causes Lynx to keep a temporary file for each cached document 881 | # containing the HTML source of the document, which it uses to regenerate 882 | # the document when certain settings are changed (for instance, 883 | # historical vs. minimal vs. valid comment parsing) instead of reloading 884 | # the source from the network. 885 | # 886 | # MEMORY is like FILE, except the document source is kept in memory. You 887 | # may wish to adjust DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE 888 | # accordingly. 889 | # 890 | # NONE is the default; the document source is not cached, and is reloaded 891 | # from the network when needed. 892 | # 893 | #SOURCE_CACHE:NONE 894 | 895 | .h2 SOURCE_CACHE_FOR_ABORTED 896 | # This setting controls what will happen with cached source for the document 897 | # being fetched from the net if fetching was aborted (either user pressed 898 | # 'z' or network went down). If set to KEEP, the source fetched so far will 899 | # be preserved (and used as cache), if set to DROP lynx will drop the 900 | # source cache for that document (i.e. only completely downloaded documents 901 | # will be cached in that case). 902 | #SOURCE_CACHE_FOR_ABORTED:DROP 903 | 904 | .h2 ALWAYS_RESUBMIT_POSTS 905 | # If ALWAYS_RESUBMIT_POSTS is set TRUE, Lynx always will resubmit forms 906 | # with method POST, dumping any cache from a previous submission of the 907 | # form, including when the document returned by that form is sought with 908 | # the PREV_DOC command or via the history list. Lynx always resubmits 909 | # forms with method POST when a submit button or a submitting text input 910 | # is activated, but normally retrieves the previously returned document 911 | # if it had links which you activated, and then go back with the PREV_DOC 912 | # command or via the history list. 913 | # 914 | # The default defined here or in userdefs.h can be toggled via 915 | # the -resubmit_forms command line switch. 916 | # 917 | #ALWAYS_RESUBMIT_POSTS:FALSE 918 | 919 | .h2 TRIM_INPUT_FIELDS 920 | # If TRIM_INPUT_FIELDS is set TRUE, Lynx will trim trailing whitespace (e.g., 921 | # space, tab, carriage return, line feed and form feed) from the text entered 922 | # into form text and textarea fields. Older versions of Lynx do this trimming 923 | # unconditionally, but other browsers do not, which would yield different 924 | # behavior for CGI scripts. 925 | #TRIM_INPUT_FIELDS:FALSE 926 | 927 | .h1 HTML Parsing 928 | 929 | .h2 NO_ISMAP_IF_USEMAP 930 | # If NO_ISMAP_IF_USEMAP is set TRUE, Lynx will not include a link to the 931 | # server-side image map if both a server-side and client-side map for the 932 | # same image is indicated in the HTML markup. The compilation default is 933 | # FALSE, such that a link with "[ISMAP]" as the link name, followed by a 934 | # hyphen, will be prepended to the ALT string or "[USEMAP]" pseudo-ALT for 935 | # accessing Lynx's text-based rendition of the client-side map (based on 936 | # the content of the associated MAP element). If the "[ISMAP]" link is 937 | # activated, Lynx will send a 0,0 coordinate pair to the server, which 938 | # Lynx-friendly sites can map to a for-text-client document, homologous 939 | # to what is intended for the content of a FIG element. 940 | # 941 | # The compilation default, or default defined here, can be toggled via 942 | # the "-ismap" command line switch. 943 | # 944 | #NO_ISMAP_IF_USEMAP:FALSE 945 | 946 | .h2 SEEK_FRAG_MAP_IN_CUR 947 | # If SEEK_FRAG_MAP_IN_CUR is set FALSE, then USEMAP attribute values 948 | # (in IMG or OBJECT tags) consisting of only a fragment (USEMAP="#foo") 949 | # will be resolved with respect to the current document's base, which 950 | # might not be the same as the current document's URL. 951 | # The compilation default is to use the current document's URL in all 952 | # cases (i.e., assume the MAP is present below, if it wasn't present 953 | # above the point in the HTML stream where the USEMAP attribute was 954 | # detected). Lynx's present "single pass" rendering engine precludes 955 | # checking below before making the decision on how to resolve a USEMAP 956 | # reference consisting solely of a fragment. 957 | # 958 | #SEEK_FRAG_MAP_IN_CUR:TRUE 959 | 960 | .h2 SEEK_FRAG_AREA_IN_CUR 961 | # If SEEK_FRAG_AREA_IN_CUR is set FALSE, then HREF attribute values 962 | # in AREA tags consisting of only a fragment (HREF="#foo") will be 963 | # resolved with respect to the current document's base, which might 964 | # not be the same as the current document's URL. The compilation 965 | # default is to use the current document's URL, as is done for the 966 | # HREF attribute values of Anchors and LINKs that consist solely of 967 | # a fragment. 968 | # 969 | #SEEK_FRAG_AREA_IN_CUR:TRUE 970 | 971 | .h1 CGI scripts 972 | # These settings control Lynx's ability to execute various types of scripts. 973 | 974 | .h2 LOCAL_EXECUTION_LINKS_ALWAYS_ON 975 | .h2 LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE 976 | # Local execution links and scripts are by default completely disabled, 977 | # unless a change is made to the userdefs.h file to enable them or 978 | # the configure script is used with the corresponding options 979 | # (-enable-exec-links and -enable-exec-scripts). 980 | # See the Lynx source code distribution and the userdefs.h 981 | # file for more detail on enabling execution links and scripts. 982 | # 983 | # If you have enabled execution links or scripts the following 984 | # two variables control Lynx's action when an execution link 985 | # or script is encountered. 986 | # 987 | # If LOCAL_EXECUTION_LINKS_ALWAYS_ON is set to TRUE any execution 988 | # link or script will be executed no matter where it came from. 989 | # This is EXTREMELY dangerous. Since Lynx can access files from 990 | # anywhere in the world, you may encounter links or scripts that 991 | # will cause damage or compromise the security of your system. 992 | # 993 | # If LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE is set to TRUE only 994 | # links or scripts that reside on the local machine and are 995 | # referenced with a URL beginning with "file://localhost/" or meet 996 | # TRUSTED_EXEC or ALWAYS_TRUSTED_EXEC rules (see below) will be 997 | # executed. This is much less dangerous than enabling all execution 998 | # links, but can still be dangerous. 999 | # 1000 | #LOCAL_EXECUTION_LINKS_ALWAYS_ON:FALSE 1001 | #LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:FALSE 1002 | 1003 | .h2 TRUSTED_EXEC 1004 | # If LOCAL_EXECUTION_LINK_ON_BUT_NOT_REMOTE is TRUE, and no TRUSTED_EXEC 1005 | # rule is defined, it defaults to "file://localhost/" and any lynxexec 1006 | # or lynxprog command will be permitted if it was referenced from within 1007 | # a document whose URL begins with that string. If you wish to restrict the 1008 | # referencing URLs further, you can extend the string to include a trusted 1009 | # path. You also can specify a trusted directory for http URLs, which will 1010 | # then be treated as if they were local rather than remote. For example: 1011 | # 1012 | # TRUSTED_EXEC:file://localhost/trusted/ 1013 | # TRUSTED_EXEC:http://www.wfbr.edu/trusted/ 1014 | # 1015 | # If you also wish to restrict the commands which can be executed, create 1016 | # a series of rules with the path (Unix) or command name (VMS) following 1017 | # the string, separated by a tab. For example: 1018 | # 1019 | # Unix: 1020 | # ==== 1021 | # TRUSTED_EXEC:file://localhost//bin/cp 1022 | # TRUSTED_EXEC:file://localhost//bin/rm 1023 | # VMS: 1024 | # === 1025 | # TRUSTED_EXEC:file://localhost/copy 1026 | # TRUSTED_EXEC:file://localhost/delete 1027 | # 1028 | # Once you specify a TRUSTED_EXEC referencing string, the default is 1029 | # replaced, and all the referencing strings you desire must be specified 1030 | # as a series. Similarly, if you associate a command with the referencing 1031 | # string, you must specify all of the allowable commands as a series of 1032 | # TRUSTED_EXEC rules for that string. If you specify ALWAYS_TRUSTED_EXEC 1033 | # rules below, you need not repeat them as TRUSTED_EXEC rules. 1034 | # 1035 | # If EXEC_LINKS and JUMPFILE have been defined, any lynxexec or lynxprog 1036 | # URLs in that file will be permitted, regardless of other settings. If 1037 | # you also set LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE and a single 1038 | # TRUSTED_EXEC rule that will always fail (e.g., "none"), then *ONLY* the 1039 | # lynxexec or lynxprog URLs in JUMPFILE (and any ALWAYS_TRUSTED_EXEC rules, 1040 | # see below) will be allowed. Note, however, that if Lynx was compiled with 1041 | # CAN_ANONYMOUS_JUMP set to FALSE (default is TRUE), or -restrictions=jump 1042 | # is included with the -anonymous switch at run time, then users of an 1043 | # anonymous account will not be able to access the jumps file or enter 1044 | # 'j'ump shortcuts, and this selective execution feature will be overridden 1045 | # as well (i.e., they will only be able to access lynxexec or lynxprog 1046 | # URLs which meet any ALWAYS_TRUSTED_EXEC rules). 1047 | # 1048 | #TRUSTED_EXEC:none 1049 | 1050 | .h2 ALWAYS_TRUSTED_EXEC 1051 | # If EXEC_LINKS was defined, any lynxexec or lynxprog URL can be made 1052 | # always enabled by an ALWAYS_TRUSTED_EXEC rule for it. This is useful for 1053 | # anonymous accounts in which you have disabled execution links generally, 1054 | # and may also have disabled jumps file links, but still want to allow 1055 | # execution of particular utility scripts or programs. The format is 1056 | # like that for TRUSTED_EXEC. For example: 1057 | # 1058 | # Unix: 1059 | # ==== 1060 | # ALWAYS_TRUSTED_EXEC:file://localhost//usr/local/kinetic/bin/usertime 1061 | # ALWAYS_TRUSTED_EXEC:http://www.more.net//usr/local/kinetic/bin/who.sh 1062 | # VMS: 1063 | # === 1064 | # ALWAYS_TRUSTED_EXEC:file://localhost/usertime 1065 | # ALWAYS_TRUSTED_EXEC:http://www.more.net/show users 1066 | # 1067 | # The default ALWAYS_TRUSTED_EXEC rule is "none". 1068 | # 1069 | #ALWAYS_TRUSTED_EXEC:none 1070 | 1071 | .h2 TRUSTED_LYNXCGI 1072 | # Unix: 1073 | # ===== 1074 | # TRUSTED_LYNXCGI rules define the permitted sources and/or paths for 1075 | # lynxcgi links (if LYNXCGI_LINKS is defined in userdefs.h). The format 1076 | # is the same as for TRUSTED_EXEC rules (see above). Example rules: 1077 | # 1078 | # TRUSTED_LYNXCGI:file://localhost/ 1079 | # TRUSTED_LYNXCGI:/usr/local/etc/httpd/cgi-bin/ 1080 | # TRUSTED_LYNXCGI:file://localhost//usr/local/www/cgi-bin/ 1081 | # 1082 | # VMS: 1083 | # ==== 1084 | # Do not define this. 1085 | # 1086 | # The default TRUSTED_LYNXCGI rule is "none". 1087 | # 1088 | #TRUSTED_LYNXCGI:none 1089 | 1090 | .h2 LYNXCGI_ENVIRONMENT 1091 | # Unix: 1092 | # ===== 1093 | # LYNXCGI_ENVIRONMENT adds the current value of the specified 1094 | # environment variable to the list of environment variables passed on to the 1095 | # lynxcgi script. Useful variables are HOME, USER, etc... If proxies 1096 | # are in use, and the script invokes another copy of lynx (or a program like 1097 | # wget) in a subsidiary role, it can be useful to add http_proxy and other 1098 | # *_proxy variables. 1099 | # 1100 | # VMS: 1101 | # ==== 1102 | # Do not define this. 1103 | # 1104 | #LYNXCGI_ENVIRONMENT: 1105 | 1106 | .h2 LYNXCGI_DOCUMENT_ROOT 1107 | # Unix: 1108 | # ===== 1109 | # LYNXCGI_DOCUMENT_ROOT is the value of DOCUMENT_ROOT that will be passed 1110 | # to lynxcgi scripts. If set and the URL has PATH_INFO data, then 1111 | # PATH_TRANSLATED will also be generated. Examples: 1112 | # LYNXCGI_DOCUMENT_ROOT:/usr/local/etc/httpd/htdocs 1113 | # LYNXCGI_DOCUMENT_ROOT:/data/htdocs/ 1114 | # 1115 | # VMS: 1116 | # ==== 1117 | # Do not define this. 1118 | # 1119 | #LYNXCGI_DOCUMENT_ROOT: 1120 | 1121 | .h1 Cookies 1122 | 1123 | .h2 FORCE_SSL_COOKIES_SECURE 1124 | # If FORCE_SSL_COOKIES_SECURE is set to TRUE, then SSL encrypted cookies 1125 | # received from https servers never will be sent unencrypted to http 1126 | # servers. The compilation default is to impose this block only if the 1127 | # https server included a secure attribute for the cookie. The normal 1128 | # default or that defined here can be toggled via the -force_secure 1129 | # command line switch. 1130 | # 1131 | FORCE_SSL_COOKIES_SECURE:TRUE 1132 | 1133 | .h1 Internal Behavior 1134 | 1135 | .h2 MAIL_SYSTEM_ERROR_LOGGING 1136 | # MAIL_SYSTEM_ERROR_LOGGING will send a message to the owner of 1137 | # the information, or ALERTMAIL if there is no owner, every time 1138 | # that a document cannot be accessed! 1139 | # 1140 | # NOTE: This can generate A LOT of mail, be warned. 1141 | # 1142 | #MAIL_SYSTEM_ERROR_LOGGING:FALSE 1143 | 1144 | .h2 CHECKMAIL 1145 | # If CHECKMAIL is set to TRUE, the user will be informed (via a statusline 1146 | # message) about the existence of any unread mail at startup of Lynx, and 1147 | # will get statusline messages if subsequent new mail arrives. If a jumps 1148 | # file with a lynxprog URL for invoking mail is available, or your html 1149 | # pages include an mail launch file URL, the user thereby can access mail 1150 | # and read the messages. The checks and statusline reports will not be 1151 | # performed if Lynx has been invoked with the -restrictions=mail switch. 1152 | # 1153 | # VMS USERS !!! 1154 | # ============= 1155 | # New mail is normally broadcast as it arrives, via "unsolicited screen 1156 | # broadcasts", which can be "wiped" from the Lynx display via the Ctrl-W 1157 | # command. You may prefer to disable the broadcasts and use CHECKMAIL 1158 | # instead (e.g., in a public account which will be used by people who 1159 | # are ignorant about VMS). 1160 | # 1161 | #CHECKMAIL:FALSE 1162 | 1163 | .h1 News-groups 1164 | 1165 | .h2 NNTPSERVER 1166 | # To enable news reading ability via Lynx, the environment variable NNTPSERVER 1167 | # must be set so that it points to your site's NNTP server 1168 | # (see Lynx Users Guide on environment variables). 1169 | # Lynx respects RFC 1738 1170 | .url http://tools.ietf.org/html/rfc1738 1171 | # and does not accept a host field in news URLs (use nntp: instead of news: for 1172 | # the scheme if you wish to specify an NNTP host in a URL, as explained in the 1173 | # RFC). If you have not set the variable externally, you can set it at run 1174 | # time via this configuration file. It will not override an external setting. 1175 | # Note that on VMS it is set as a process logical rather than symbol, and will 1176 | # outlive the Lynx image. 1177 | # The news reading facility in Lynx is quite limited. Lynx does not provide a 1178 | # full featured news reader with elaborate error checking and safety features. 1179 | # 1180 | #NNTPSERVER:news.server.dom 1181 | 1182 | .h2 LIST_NEWS_NUMBERS 1183 | # If LIST_NEWS_NUMBERS is set TRUE, Lynx will use an ordered list and include 1184 | # the numbers of articles in news listings, instead of using an unordered 1185 | # list. The default is defined in userdefs.h, and can be overridden here. 1186 | # 1187 | #LIST_NEWS_NUMBERS:FALSE 1188 | 1189 | .h2 LIST_NEWS_DATES 1190 | # If LIST_NEWS_DATES is set TRUE, Lynx will include the dates of articles in 1191 | # news listings. The dates always are included in the articles, themselves. 1192 | # The default is defined in userdefs.h, and can be overridden here. 1193 | # 1194 | #LIST_NEWS_DATES:FALSE 1195 | 1196 | .h2 NEWS_CHUNK_SIZE 1197 | .h2 NEWS_MAX_CHUNK 1198 | # NEWS_CHUNK_SIZE and NEWS_MAX_CHUNK regulate the chunking of news article 1199 | # listings with inclusion of links for listing earlier and/or later articles. 1200 | # The defaults are defined in HTNews.c as 30 and 40, respectively. If the 1201 | # news group contains more than NEWS_MAX_CHUNK articles, they will be listed 1202 | # in NEWS_CHUNK_SIZE chunks. You can change the defaults here, and/or on 1203 | # the command line via -newschunksize=NUMBER and/or -newsmaxchunk=NUMBER 1204 | # switches. Note that if the chunk size is increased, here or on the command 1205 | # line, to a value greater than the current maximum, the maximum will be 1206 | # increased to that number. Conversely, if the maximum is set to a number 1207 | # less than the current chunk size, the chunk size will be reduced to that 1208 | # number. Thus, you need use only one of the two switches on the command 1209 | # line, based on the direction of intended change relative to the compilation 1210 | # or configuration defaults. The compilation defaults ensure that there will 1211 | # be at least 10 earlier articles before bothering to chunk and create a link 1212 | # for earlier articles. 1213 | # 1214 | #NEWS_CHUNK_SIZE:30 1215 | #NEWS_MAX_CHUNK:40 1216 | 1217 | .h2 NEWS_POSTING 1218 | # Set NEWS_POSTING to FALSE if you do not want to support posting to 1219 | # news groups via Lynx. If left TRUE, Lynx will use its news gateway to 1220 | # post new messages or followups to news groups, using the URL schemes 1221 | # described in the "Supported URLs" section of the online 'h'elp. The 1222 | # posts will be attempted via the nntp server specified in the URL, or 1223 | # if none was specified, via the NNTPSERVER configuration or environment 1224 | # variable. Links with these URLs for posting or sending followups are 1225 | # created by the news gateway when reading group listings or articles 1226 | # from nntp servers if the server indicates that it permits posting. 1227 | # The compilation default set in userdefs.h can be changed here. If 1228 | # the default is TRUE, posting can still be disallowed via the 1229 | # -restrictions command line switch. 1230 | # The posting facility in Lynx is quite limited. Lynx does not provide a 1231 | # full featured news poster with elaborate error checking and safety features. 1232 | # 1233 | #NEWS_POSTING:TRUE 1234 | 1235 | .h2 LYNX_SIG_FILE 1236 | # LYNX_SIG_FILE defines the name of a file containing a signature which 1237 | # can be appended to email messages and news postings or followups. The 1238 | # user will be prompted whether to append it. It is sought in the home 1239 | # directory. If it is in a subdirectory, begin it with a dot-slash 1240 | # (e.g., ./lynx/.lynxsig). The definition is set in userdefs.h and can 1241 | # be changed here. 1242 | # 1243 | #LYNX_SIG_FILE:.lynxsig 1244 | 1245 | .h1 Bibliographic Protocol (bibp scheme) 1246 | 1247 | .h2 BIBP_GLOBAL_SERVER 1248 | # BIBP_GLOBAL_SERVER is the default global server for bibp: links, used 1249 | # when a local bibhost or document-specified citehost is unavailable. 1250 | # Set in userdefs.h and can be changed here. 1251 | #BIBP_GLOBAL_SERVER:http://usin.org/ 1252 | 1253 | .h2 BIBP_BIBHOST 1254 | # BIBP_BIBHOST is the URL at which local bibp service may be found, if 1255 | # it exists. Defaults to http://bibhost/ for protocol conformance, but 1256 | # may be overridden here or via -bibhost parameter. 1257 | #BIBP_BIBHOST:http://bibhost/ 1258 | 1259 | .h1 Interaction 1260 | # These settings control interaction of the user with lynx. 1261 | 1262 | .h2 SCROLLBAR 1263 | # If SCROLLBAR is set TRUE, Lynx will show scrollbar on windows. With mouse 1264 | # enabled, the scrollbar strip outside the bar is clickable, and scrolls the 1265 | # window by pages. The appearance of the scrollbar can be changed from 1266 | # LYNX_LSS file: define attributes scroll.bar, scroll.back (for the bar, and 1267 | # for the strip along which the scrollbar moves). 1268 | #SCROLLBAR:FALSE 1269 | 1270 | .h2 SCROLLBAR_ARROW 1271 | # If SCROLLBAR_ARROW is set TRUE, Lynx's scrollbar will have arrows at the 1272 | # ends. With mouse enabled, the arrows are clickable, and scroll the window by 1273 | # 2 lines. The appearance of the scrollbar arrows can be changed from LYNX_LSS 1274 | # file: define attributes scroll.arrow, scroll.noarrow (for enabled-arrows, 1275 | # and disabled arrows). An arrow is "disabled" if the bar is at this end of 1276 | # the strip. 1277 | #SCROLLBAR_ARROW:TRUE 1278 | 1279 | .h2 USE_MOUSE 1280 | # If Lynx is configured with ncurses, PDcurses or slang & USE_MOUSE is TRUE, 1281 | # users can perform commands by left-clicking certain parts of the screen: 1282 | # on a link = `g'oto + ACTIVATE (i.e., move highlight & follow the link); 1283 | # on the top/bottom lines = PREV/NEXT_PAGE (i.e., go up/down 1 page); 1284 | # on the top/bottom left corners = PREV/NEXT_DOC (i.e., go to the previous 1285 | # document / undo goto previous document); 1286 | # on the top/bottom right corners = HISTORY/VLINKS (i.e., call up the history 1287 | # page or visited links page if on history page). 1288 | # NB if the mouse is defined in this way, it will not be available 1289 | # for copy/paste operations using the clipboard of a desktop manager: 1290 | # for flexibility instead, use the command-line switch -use_mouse . 1291 | # 1292 | # ncurses and slang have built-in support for the xterm mouse protocol. In 1293 | # addition, ncurses can be linked with the gpm mouse library, to automatically 1294 | # provide support for this interface in applications such as Lynx. (Please 1295 | # read the ncurses faq to work around broken gpm configurations packaged by 1296 | # some distributors). PDCurses implements mouse support for win32 console 1297 | # windows, as does slang. 1298 | #USE_MOUSE:FALSE 1299 | 1300 | .h1 HTML Parsing 1301 | # These settings control the way Lynx parses invalid HTML 1302 | # and how it may resolve such issues. 1303 | 1304 | .h2 COLLAPSE_BR_TAGS 1305 | # If COLLAPSE_BR_TAGS is set FALSE, Lynx will not collapse serial BR tags. 1306 | # If set TRUE, two or more concurrent BRs will be collapsed into a single 1307 | # line break. Note that the valid way to insert extra blank lines in HTML 1308 | # is via a PRE block with only newlines in the block. 1309 | # 1310 | #COLLAPSE_BR_TAGS:TRUE 1311 | 1312 | .h2 TRIM_BLANK_LINES 1313 | # If TRIM_BLANK_LINES is set FALSE, Lynx will not trim trailing blank lines 1314 | # from the document. Also, Lynx will not collapse BR-tags onto the previous 1315 | # line when it happens to be empty. 1316 | #TRIM_BLANK_LINES:TRUE 1317 | 1318 | .h2 TAGSOUP 1319 | # If TAGSOUP is set, Lynx uses the "Tag Soup DTD" rather than "SortaSGML". 1320 | # The two approaches differ by the style of error detection and recovery. 1321 | # Tag Soup DTD allows for improperly nested tags; SortaSGML is stricter. 1322 | #TAGSOUP:FALSE 1323 | 1324 | .h1 Cookies 1325 | 1326 | .h2 SET_COOKIES 1327 | # If SET_COOKIES is set FALSE, Lynx will ignore Set-Cookie headers 1328 | # in http server replies. Note that if a COOKIE_FILE is in use (see 1329 | # below) that contains cookies at startup, Lynx will still send those 1330 | # persistent cookies in requests as appropriate. Setting SET_COOKIES 1331 | # to FALSE just prevents accepting any new cookies from servers. To 1332 | # prevent all cookie processing (sending *and* receiving) in a session, 1333 | # make sure that PERSISTENT_COOKIES is not TRUE or that COOKIE_FILE does 1334 | # not point to a file with cookies, in addition to setting SET_COOKIES 1335 | # to FALSE. 1336 | # The default is defined in userdefs.h, and can be overridden here, 1337 | # and/or toggled via the -cookies command line switch. 1338 | # 1339 | SET_COOKIES:TRUE 1340 | 1341 | .h2 ACCEPT_ALL_COOKIES 1342 | # If ACCEPT_ALL_COOKIES is set TRUE, Lynx will accept cookies from all 1343 | # domains with no user interaction. This is equivalent to automatically 1344 | # replying to all cookie 'Allow?' prompts with 'A'lways. Note that it 1345 | # does not preempt validity checking, which has to be controlled separately 1346 | # (see below). 1347 | # The default is defined in userdefs.h and can be overridden here, or 1348 | # in the .lynxrc file via an o(ptions) screen setting. It may also be 1349 | # toggled via the -accept_all_cookies command line switch. 1350 | # 1351 | ACCEPT_ALL_COOKIES=TRUE 1352 | 1353 | .h2 COOKIE_ACCEPT_DOMAINS 1354 | .h2 COOKIE_REJECT_DOMAINS 1355 | # COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS are comma-delimited lists 1356 | # of domains from which Lynx should automatically accept or reject cookies 1357 | # without asking for confirmation. If the same domain is specified in both 1358 | # lists, rejection will take precedence. 1359 | # Note that in order to match cookies, domains have to be spelled out exactly 1360 | # in the form in which they would appear on the Cookie Jar page (case is 1361 | # insignificant). They are not wildcards. Domains that apply to more than 1362 | # one host have a leading '.', but have to match *the cookie's* domain 1363 | # exactly. 1364 | # 1365 | #COOKIE_ACCEPT_DOMAINS: 1366 | #COOKIE_REJECT_DOMAINS: 1367 | 1368 | .h2 COOKIE_LOOSE_INVALID_DOMAINS 1369 | .h2 COOKIE_STRICT_INVALID_DOMAINS 1370 | .h2 COOKIE_QUERY_INVALID_DOMAINS 1371 | # COOKIE_LOOSE_INVALID_DOMAINS, COOKIE_STRICT_INVALID_DOMAINS, and 1372 | # COOKIE_QUERY_INVALID_DOMAINS are comma-delimited lists of domains. 1373 | # They control the degree of validity checking that is applied to cookies 1374 | # for the specified domains. 1375 | # Note that in order to match cookies, domains have to be spelled out exactly 1376 | # in the form in which they would appear on the Cookie Jar page (case is 1377 | # insignificant). They are not wildcards. Domains that apply to more than 1378 | # one host have a leading '.', but have to match *the cookie's* domain 1379 | # exactly. 1380 | # If a domain is set to strict checking, strict conformance to RFC 2109 will 1381 | # be applied. A domain with loose checking will be allowed to set cookies 1382 | # with an invalid path or domain attribute. All domains will default to 1383 | # asking the user for confirmation in case of an invalid path or domain. 1384 | # Cookie validity checking takes place as a separate step before the 1385 | # final decision to accept or reject (see previous options), therefore 1386 | # a cookie that passes validity checking may still be automatically 1387 | # rejected or cause another prompt. 1388 | # 1389 | #COOKIE_LOOSE_INVALID_DOMAINS: 1390 | #COOKIE_STRICT_INVALID_DOMAINS: 1391 | #COOKIE_QUERY_INVALID_DOMAINS: 1392 | 1393 | .h2 MAX_COOKIES_DOMAIN 1394 | .h2 MAX_COOKIES_GLOBAL 1395 | .h2 MAX_COOKIES_BUFFER 1396 | # MAX_COOKIES_DOMAIN, 1397 | # MAX_COOKIES_GLOBAL and 1398 | # MAX_COOKIES_BUFFER are limits on the total number of cookies for each domain, 1399 | # globally, and the per-cookie buffer size. These limits are by default large 1400 | # enough for reasonable usage; if they are very high, some sites may present 1401 | # undue performance waste. 1402 | # 1403 | #MAX_COOKIES_DOMAIN:50 1404 | #MAX_COOKIES_GLOBAL:500 1405 | #MAX_COOKIES_BUFFER:4096 1406 | 1407 | .h2 PERSISTENT_COOKIES 1408 | # PERSISTENT_COOKIES indicates that cookies should be read at startup from 1409 | # the COOKIE_FILE, and saved at exit for storage between Lynx sessions. 1410 | # It is not used if Lynx was compiled without USE_PERSISTENT_COOKIES. 1411 | # The default is FALSE, so that the feature needs to be enabled here 1412 | # explicitly if you want it. 1413 | # 1414 | PERSISTENT_COOKIES:TRUE 1415 | 1416 | .h2 COOKIE_FILE 1417 | # COOKIE_FILE is the default file from which persistent cookies are read 1418 | # at startup (if the file exists), if Lynx was compiled with 1419 | # USE_PERSISTENT_COOKIES and the PERSISTENT_COOKIES option is enabled. 1420 | # The cookie file can also be specified in .lynxrc or on the command line. 1421 | # 1422 | COOKIE_FILE:~/.lynx_cookies 1423 | 1424 | .h2 COOKIE_SAVE_FILE 1425 | # COOKIE_SAVE_FILE is the default file in which persistent cookies are 1426 | # stored at exit, if Lynx was compiled with USE_PERSISTENT_COOKIES and the 1427 | # PERSISTENT_COOKIES option is enabled. The cookie save file can also be 1428 | # specified on the command line. 1429 | # 1430 | # With an interactive Lynx session, COOKIE_SAVE_FILE will default to 1431 | # COOKIE_FILE if it is not set. With a non-interactive Lynx session (e.g., 1432 | # -dump), cookies will only be saved to file if COOKIE_SAVE_FILE is set. 1433 | # 1434 | COOKIE_SAVE_FILE:~/.lynx_cookies 1435 | 1436 | .h1 Mail-related 1437 | 1438 | .h2 SYSTEM_MAIL 1439 | .h2 SYSTEM_MAIL_FLAGS 1440 | # VMS: 1441 | # === 1442 | # The mail command and qualifiers are defined in userdefs.h. Lynx 1443 | # will spawn a subprocess to send replies and error messages. The 1444 | # command, and qualifiers (if any), can be re-defined here. If 1445 | # you use PMDF then headers will we passed via a header file. 1446 | # If you use "generic" VMS MAIL, the subject will be passed on the 1447 | # command line via a /subject="SUBJECT" qualifier, and inclusion 1448 | # of other relevant headers may not be possible. 1449 | # If your mailer uses another syntax, some hacking of the mailform() 1450 | # mailmsg() and reply_by_mail() functions in LYMail.c, and send_file_to_mail() 1451 | # function in LYPrint.c, may be required. 1452 | # 1453 | .ex 2 1454 | #SYSTEM_MAIL:PMDF SEND 1455 | #SYSTEM_MAIL_FLAGS:/headers 1456 | # 1457 | .ex 2 1458 | #SYSTEM_MAIL:MAIL 1459 | #SYSTEM_MAIL_FLAGS: 1460 | # 1461 | # Unix: 1462 | #====== 1463 | # The mail path and flags normally are defined for sendmail (or submit 1464 | # with MMDF) in userdefs.h. You can change them here, but should first 1465 | # read the zillions of CERT advisories about security problems with Unix 1466 | # mailers. 1467 | # 1468 | .ex 2 1469 | #SYSTEM_MAIL:/usr/mmdf/bin/submit 1470 | #SYSTEM_MAIL_FLAGS:-mlruxto,cc\* 1471 | # 1472 | .ex 2 1473 | #SYSTEM_MAIL:/usr/sbin/sendmail 1474 | #SYSTEM_MAIL_FLAGS:-t -oi 1475 | # 1476 | .ex 2 1477 | #SYSTEM_MAIL:/usr/lib/sendmail 1478 | #SYSTEM_MAIL_FLAGS:-t -oi 1479 | # 1480 | # Win32: 1481 | #======= 1482 | # The Win32 port assumes that the mailer cannot read via a pipe. That is, it 1483 | # must read all information from files. The "sendmail" utility in the 2.8.1 1484 | # release is able to work with that assumption. There is no way to tell the 1485 | # Win32 port of Lynx to send its information to the sendmail utility via a 1486 | # pipe. 1487 | # 1488 | # Please read sendmail.txt in the LYNX_W32.ZIP distribution 1489 | .url http://invisible-mirror.net/archives/lynx/tarballs/lynx2.8.1_w32.zip 1490 | .url ftp://ftp.invisible-island.net/lynx/tarballs/lynx2.8.1_w32.zip 1491 | # 1492 | # As an alternative, the newer "sendmail for windows" may be useful: 1493 | .url http://glob.com.au/sendmail/ 1494 | # 1495 | # See also BLAT_MAIL and ALT_BLAT_MAIL flags. 1496 | # 1497 | #SYSTEM_MAIL:sendmail -f me@my.host -h my.host -r my.smtp.mailer -m SMTP 1498 | 1499 | .h2 MAIL_ADRS 1500 | # VMS ONLY: 1501 | # ======== 1502 | # MAIL_ADRS is defined in userdefs.h and normally is structured for PMDF's 1503 | # IN%"INTERNET_ADDRESS" scheme. The %s is replaced with the address given 1504 | # by the user. If you are using a different Internet mail transport, change 1505 | # the IN appropriately (e.g., to SMTP, MX, or WINS). 1506 | # 1507 | #MAIL_ADRS:"IN%%""%s""" 1508 | 1509 | .h2 USE_FIXED_RECORDS 1510 | # VMS ONLY: 1511 | # ======== 1512 | # If USE_FIXED_RECORDS is set to TRUE here or in userdefs.h, Lynx will 1513 | # convert 'd'ownloaded binary files to FIXED 512 record format before saving 1514 | # them to disk or acting on a DOWNLOADER option. If set to FALSE, the 1515 | # headers of such files will indicate that they are Stream_LF with Implied 1516 | # Carriage Control, which is incorrect, and can cause downloading software 1517 | # to get confused and unhappy. If you do set it FALSE, you can use the 1518 | # FIXED512.COM command file, which is included in this distribution, to do 1519 | # the conversion externally. 1520 | # 1521 | #USE_FIXED_RECORDS:TRUE 1522 | 1523 | .h1 Keyboard Input 1524 | # These settings control the way Lynx interprets user input. 1525 | 1526 | .h2 VI_KEYS_ALWAYS_ON 1527 | .h2 EMACS_KEYS_ALWAYS_ON 1528 | # Vi or Emacs movement keys, i.e. familiar hjkl or ^N^P^F^B . 1529 | # These are defaults, which can be changed in the Options Menu or .lynxrc . 1530 | #VI_KEYS_ALWAYS_ON:FALSE 1531 | #EMACS_KEYS_ALWAYS_ON:FALSE 1532 | 1533 | .h2 DEFAULT_KEYPAD_MODE 1534 | # DEFAULT_KEYPAD_MODE may be set to NUMBERS_AS_ARROWS 1535 | # or LINKS_ARE_NOT_NUMBERED (the same) 1536 | # or LINKS_ARE_NUMBERED 1537 | # or LINKS_AND_FIELDS_ARE_NUMBERED 1538 | # or FIELDS_ARE_NUMBERED 1539 | # to specify whether numbers (e.g. [10]) appear next to all links, 1540 | # allowing immediate access by entering the number on the keyboard, 1541 | # or numbers on the numeric key-pad work like arrows; 1542 | # the "FIELDS" options cause form fields also to be numbered. 1543 | # This may be overridden by the keypad_mode setting in .lynxrc, 1544 | # and can also be changed via the Options Menu. 1545 | # 1546 | #DEFAULT_KEYPAD_MODE:NUMBERS_AS_ARROWS 1547 | 1548 | .h2 NUMBER_LINKS_ON_LEFT 1549 | .h2 NUMBER_FIELDS_ON_LEFT 1550 | # Denotes the position for link- and field-numbers (whether it is on the left 1551 | # or right of the anchor). These are subject to DEFAULT_KEYPAD_MODE, which 1552 | # determines whether numbers are shown. 1553 | #NUMBER_LINKS_ON_LEFT:TRUE 1554 | #NUMBER_FIELDS_ON_LEFT:TRUE 1555 | 1556 | .h2 DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS 1557 | # Obsolete form of DEFAULT_KEYPAD_MODE, 1558 | # numbers work like arrows or numbered links. 1559 | # Set to TRUE, indicates numbers act as arrows, 1560 | # and set to FALSE indicates numbers refer to numbered links on the page. 1561 | # LINKS_AND_FIELDS_ARE_NUMBERED cannot be set by this option because 1562 | # it allows only two values (true and false). 1563 | # 1564 | #DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS:TRUE 1565 | 1566 | .h2 CASE_SENSITIVE_ALWAYS_ON 1567 | # The default search type. 1568 | # This is a default that can be overridden by the user! 1569 | # 1570 | #CASE_SENSITIVE_ALWAYS_ON:FALSE 1571 | 1572 | .h1 Auxiliary Facilities 1573 | 1574 | .h2 DEFAULT_BOOKMARK_FILE 1575 | # DEFAULT_BOOKMARK_FILE is the filename used for storing personal bookmarks. 1576 | # It will be prepended by the user's home directory. 1577 | # NOTE that a file ending in .html or other suffix mapped to text/html 1578 | # should be used to ensure its treatment as HTML. The built-in default 1579 | # is lynx_bookmarks.html. On both Unix and VMS, if a subdirectory off of 1580 | # the HOME directory is desired, the path should begin with "./" (e.g., 1581 | # ./BM/lynx_bookmarks.html), but the subdirectory must already exist. 1582 | # Lynx will create the bookmark file, if it does not already exist, on 1583 | # the first ADD_BOOKMARK attempt if the HOME directory is indicated 1584 | # (i.e., if the definition is just filename.html without any slashes), 1585 | # but requires a pre-existing subdirectory to create the file there. 1586 | # The user can re-define the default bookmark file, as well as a set 1587 | # of sub-bookmark files if multiple bookmark file support is enabled 1588 | # (see below), via the 'o'ptions menu, and can save those definitions 1589 | # in the .lynxrc file. 1590 | # 1591 | #DEFAULT_BOOKMARK_FILE:lynx_bookmarks.html 1592 | 1593 | .h2 MULTI_BOOKMARK_SUPPORT 1594 | # If MULTI_BOOKMARK_SUPPORT is set TRUE, and BLOCK_MULTI_BOOKMARKS (see 1595 | # below) is FALSE, and sub-bookmarks exist, all bookmark operations will 1596 | # first prompt the user to select an active sub-bookmark file or the 1597 | # default bookmark file. FALSE is the default so that one (the default) 1598 | # bookmark file will be available initially. The definition here will 1599 | # override that in userdefs.h. The user can turn on multiple bookmark 1600 | # support via the 'o'ptions menu, and can save that choice as the startup 1601 | # default via the .lynxrc file. When on, the setting can be STANDARD or 1602 | # ADVANCED. If SUPPORT is set to the latter, and the user mode also is 1603 | # ADVANCED, the VIEW_BOOKMARK command will invoke a statusline prompt at 1604 | # which the user can enter the letter token (A - Z) of the desired bookmark, 1605 | # or '=' to get a menu of available bookmark files. The menu always is 1606 | # presented in NOVICE or INTERMEDIATE mode, or if the SUPPORT is set to 1607 | # STANDARD. No prompting or menu display occurs if only one (the startup 1608 | # default) bookmark file has been defined (define additional ones via the 1609 | # 'o'ptions menu). The startup default, however set, can be overridden on 1610 | # the command line via the -restrictions=multibook or the -anonymous or 1611 | # -validate switches. 1612 | # 1613 | #MULTI_BOOKMARK_SUPPORT:FALSE 1614 | 1615 | .h2 BLOCK_MULTI_BOOKMARKS 1616 | # If BLOCK_MULTI_BOOKMARKS is set TRUE, multiple bookmark support will 1617 | # be forced off, and cannot to toggled on via the 'o'ptions menu. The 1618 | # compilation setting is normally FALSE, and can be overridden here. 1619 | # It can also be set via the -restrictions=multibook or the -anonymous 1620 | # or -validate command line switches. 1621 | # 1622 | #BLOCK_MULTI_BOOKMARKS:FALSE 1623 | 1624 | .h1 Interaction 1625 | 1626 | .h2 DEFAULT_USER_MODE 1627 | # DEFAULT_USER_MODE sets the default user mode for Lynx users. 1628 | # NOVICE shows a three line help message at the bottom of the screen. 1629 | # INTERMEDIATE shows normal amount of help (one line). 1630 | # ADVANCED help is replaced by the URL of the current link. 1631 | # 1632 | #DEFAULT_USER_MODE:NOVICE 1633 | 1634 | .h1 External Programs 1635 | 1636 | .h2 DEFAULT_EDITOR 1637 | # If DEFAULT_EDITOR is defined, users may edit local documents with it 1638 | # & it will also be used for sending mail messages. 1639 | # If no editor is defined here or by the user, 1640 | # the user will not be able to edit local documents 1641 | # and a primitive line-oriented mail-input mode will be used. 1642 | # 1643 | # For sysadmins: do not define a default editor 1644 | # unless you know EVERY user will know how to use it; 1645 | # users can easily define their own editor in the Options Menu. 1646 | # 1647 | #DEFAULT_EDITOR: 1648 | 1649 | .h2 SYSTEM_EDITOR 1650 | # SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR, 1651 | # except that it can't be changed by users. 1652 | # 1653 | #SYSTEM_EDITOR: 1654 | 1655 | .h3 POSITIONABLE_EDITOR 1656 | # If POSITIONABLE_EDITOR is defined once or multiple times and if the same 1657 | # editor is used as editor in lynx, lynx will use its features, i.e., adding an 1658 | # option to set the initial line-position, when editing files and textarea. 1659 | # The commented editors below are already known; there is no need to uncomment 1660 | # them. 1661 | # 1662 | #POSITIONABLE_EDITOR:emacs 1663 | #POSITIONABLE_EDITOR:jed 1664 | #POSITIONABLE_EDITOR:jmacs 1665 | #POSITIONABLE_EDITOR:joe 1666 | #POSITIONABLE_EDITOR:jove 1667 | #POSITIONABLE_EDITOR:jpico 1668 | #POSITIONABLE_EDITOR:jstar 1669 | #POSITIONABLE_EDITOR:nano 1670 | #POSITIONABLE_EDITOR:pico 1671 | #POSITIONABLE_EDITOR:rjoe 1672 | #POSITIONABLE_EDITOR:vi 1673 | 1674 | .h1 Proxy 1675 | 1676 | .h2 HTTP_PROXY 1677 | .h2 HTTPS_PROXY 1678 | .h2 FTP_PROXY 1679 | .h2 GOPHER_PROXY 1680 | .h2 NEWSPOST_PROXY 1681 | .h2 NEWSREPLY_PROXY 1682 | .h2 NEWS_PROXY 1683 | .h2 NNTP_PROXY 1684 | .h2 SNEWSPOST_PROXY 1685 | .h2 SNEWSREPLY_PROXY 1686 | .h2 SNEWS_PROXY 1687 | .h2 WAIS_PROXY 1688 | .h2 FINGER_PROXY 1689 | .h2 CSO_PROXY 1690 | # Lynx version 2.2 and beyond supports the use of proxy servers that can act as 1691 | # firewall gateways and caching servers. They are preferable to the older 1692 | # gateway servers. Each protocol used by Lynx can be mapped separately using 1693 | # PROTOCOL_proxy environment variables (see Lynx Users Guide). If you have not set 1694 | # them externally, you can set them at run time via this configuration file. 1695 | # They will not override external settings. The no_proxy variable can be used 1696 | # to inhibit proxying to selected regions of the Web (see below). Note that on 1697 | # VMS these proxy variables are set as process logicals rather than symbols, to 1698 | # preserve lowercasing, and will outlive the Lynx image. 1699 | # 1700 | .ex 15 1701 | #http_proxy:http://some.server.dom:port/ 1702 | #https_proxy:http://some.server.dom:port/ 1703 | #ftp_proxy:http://some.server.dom:port/ 1704 | #gopher_proxy:http://some.server.dom:port/ 1705 | #news_proxy:http://some.server.dom:port/ 1706 | #newspost_proxy:http://some.server.dom:port/ 1707 | #newsreply_proxy:http://some.server.dom:port/ 1708 | #snews_proxy:http://some.server.dom:port/ 1709 | #snewspost_proxy:http://some.server.dom:port/ 1710 | #snewsreply_proxy:http://some.server.dom:port/ 1711 | #nntp_proxy:http://some.server.dom:port/ 1712 | #wais_proxy:http://some.server.dom:port/ 1713 | #finger_proxy:http://some.server.dom:port/ 1714 | #cso_proxy:http://some.server.dom:port/ 1715 | #no_proxy:host.domain.dom 1716 | 1717 | .h2 NO_PROXY 1718 | # The no_proxy variable can be a comma-separated list of strings defining 1719 | # no-proxy zones in the DNS domain name space. If a tail substring of the 1720 | # domain-path for a host matches one of these strings, transactions with that 1721 | # node will not be proxied. 1722 | .ex 1723 | #no_proxy:domain.path1,path2 1724 | # 1725 | # A single asterisk as an entry will override all proxy variables and no 1726 | # transactions will be proxied. 1727 | .ex 1728 | #no_proxy:* 1729 | # This is the only allowed use of * in no_proxy. 1730 | # 1731 | # Warning: Note that setting 'il' as an entry in this list will block proxying 1732 | # for the .mil domain as well as the .il domain. If the entry is '.il' this 1733 | # will not happen. 1734 | 1735 | .h1 External Programs 1736 | 1737 | .h2 PRINTER 1738 | .h2 DOWNLOADER 1739 | .h2 UPLOADER 1740 | # PRINTER, DOWNLOADER & UPLOADER DEFINITIONS: 1741 | # Lynx has 4 pre-defined print options & 1 pre-defined download option, 1742 | # which are called up on-screen when `p' or `d' are entered; 1743 | # any number of options can be added by the user, as explained below. 1744 | # Uploaders can be defined only for UNIX with DIRED_SUPPORT: 1745 | # see the Makefile in the top directory & the header of src/LYUpload.c . 1746 | # 1747 | # For `p' pre-defined options are: `Save to local file', `E-mail the file', 1748 | # `Print to screen' and `Print to local printer attached to vt100'. 1749 | # `Print to screen' allows file transfers in the absence of alternatives 1750 | # and is often the only option allowed here for anonymous users; 1751 | # the 3rd & 4th options are not pre-defined for DOS/WINDOWS versions of Lynx. 1752 | # For `d' the pre-defined option is: `Download to local file'. 1753 | # 1754 | # To define your own print or download option use the following formats: 1755 | # 1756 | # PRINTER:::