lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev (patch) INSTALLATION & Options refs


From: Philip Webb
Subject: lynx-dev (patch) INSTALLATION & Options refs
Date: Fri, 26 Nov 1999 15:10:14 -0500 (EST)

first, disregard my two previous patches, which this supersedes.

most of this replaces inconsistent references to `o'ptions
in  INSTALLATION PROBLEMS userdefs.h lynx.cfg lynx.hlp lynx.man
with consistent use of `Key-based/Form-based Options Menu'
(it's `form' (singular), as the document contains  1  form);
on reflection i retained `menu', as `screen/page' are less clearly defined
& some Lynx menus contain other options (eg jumps).

this patch also contains the earlier INSTALLATION revisions,
adjusted to satisfy DK & compromise with HN (i hope),
and the simplification of the uploader section in lynx.cfg .
also, i tidied up a few mis-shapen lines along the way.

*** as always with docs, please put yourself in the shoes of JU ***
`o'ptions revisions for the help docs should follow soon.

PS for TD:  LOCAL_EXECUTION_LINKS_ALWAYS_OFF_FOR_ANONYMOUS
seems to conflict with your 32-character rule (there's another similar).

--- old/INSTALLATION    Sat Aug 28 15:04:14 1999
+++ new/INSTALLATION    Fri Nov 26 14:10:42 1999
@@ -25,62 +25,74 @@
 Follow the instructions given immediately below to configure for your system,
 and then go to the respective section concerning the port you wish to compile.
 
-
 I. General configuration instructions (all ports).
 
-Step 1. (define compile-time variables  -- See the userdefs.h file.)
-    There are a few variables that MUST be defined, or Lynx will not build.
-    There are a few more that you will probably want to change.  The variables
-    that must be changed are marked as such in the userdefs.h file.  Just edit
-    this file, and the changes should be straight forward.  If you compile
-    using autoconfigure, you can set most defines with option switches and do
-    not absolutely have to edit userdefs.h.  Many of the variables are now
-    configurable in the lynx.cfg file, so you may set them at run-time if you
-    wish.  Lynx implements Native Language Support.  Read "ABOUT-NLS" if you
-    want to build an international version of Lynx or tailor the statusline
-    prompts, messages and warnings to the requirements of your site.
-
-Step 2. (define run-time variables -- See the lynx.cfg file for details.)
-    Set up local printers, downloaders, assumed character set, key mapping,
-    and colors in the lynx.cfg file.  Please read "lynx.cfg" thoroughly as
-    many of the features of Lynx, and how to use them, are explained.  Also
-    see the example mime.types, mailcap and jumps files in the samples
-    subdirectory.  Lynx MUST be able to find the lynx.cfg file at start-up.
-    The location of the lynx.cfg file may be compiled in with the LYNX_CFG_FILE
-    defined in userdefs.h (or with the configure option explained in the Unix
-    section below), specified with an environment variable, LYNX_CFG, or
-    specified with the "-cfg" command line option.
-
-Step 3. (You may skip this step if you are not interested in any special
-    characters and any local files or WWW pages you will view all use the
-    ISO-8859-1 "ISO Latin 1" Western European character set.) People who
-    will be running Lynx in an environment with different and incompatible
-    character sets should configure CHARACTER_SET (the Display character set)
-    and ASSUME_LOCAL_CHARSET to work correctly for them before creating
-    bookmark files et cetera.  Read "lynx.cfg" for detailed instructions.
-    Additional character sets and their properties may be defined with tables
-    in the src/chrtrans directory, see the README.* files therein.
-
-Step 4. (optional -- news for UNIX and VMS)
-    Set NNTPSERVER in "lynx.cfg" to your site's NNTP server, or set the
-    environment variable externally.  For news posting ability to be enabled
-    in Lynx, the NEWS_POSTING symbol must be defined to TRUE in userdefs.h or
-    lynx.cfg.  Also define LYNX_SIG_FILE in userdefs.h or lynx.cfg so that it
-    points to users' signature files for appending to posted messages.
-
-Step 5. (Anonymous account -- VERY IMPORTANT!!!!! -- )
-    If you are building Lynx for your personal use only you may skip this
-    step.  If you are setting up an anonymous account with Lynx, you are
-    STRONGLY advised to use the -anonymous command line option.  If you do
-    not use this option, users may be able to gain access to all readable
-    files on your machine!  ALSO NOTE that many implementations of telnetd
-    allow passing of environment variables, which might be used by
-    unscrupulous people to modify the environment in anonymous accounts.
-    When making Web access publicly available via anonymous accounts intended
-    to run Lynx captively, be sure the wrapper uses the -cfg and -homepage
-    switches to specify the configuration and start files, rather than relying
-    on the LYNX_CFG, LYNX_CFG_FILE, or WWW_HOME variables.
+Step 1.  Compile-time variables.
 
+  There are a few variables that MUST be defined if Lynx is to build
+  and there are others you may want to change.
+  
+  Lynx MUST be able to find lynx.cfg at start-up: using configure
+  (e.g. with UNIX or Cygwin), its location is best set with --libdir ;
+  you can check in lynx_cfg.h after configure has run, if you wish.
+  otherwise, you can use LYNX_CFG_FILE in userdefs.h ,
+  environment variable LYNX_CFG or the -cfg command-line option.
+
+  If you are using configure, you need not make any changes in userdefs.h .
+  There are a few variables you can't define with configure --options
+  but can define in userdefs.h , e.g. numbering fields as well as links.
+  Many variables which can be defined with configure or userdefs.h
+  can also be defined in lynx.cfg or via the Options Menu.
+  
+  Lynx implements Native Language Support.  Read "ABOUT-NLS", if you want
+  to build an international version of Lynx or tailor status-line prompts,
+  messages and warnings to the requirements of your site.
+
+Step 2.  Run-time variables.
+
+  Read lynx.cfg thoroughly, as many Lynx features and how to use them
+  are explained there, in some cases ONLY there.  Set up local printers,
+  downloaders, assumed character set, key mapping and colors in lynx.cfg .
+  Also see the sample mime.types, mailcap and jumps files
+  in the samples subdirectory.
+
+Step 3.  Alternative Character Sets.
+
+  You may skip this, if you are not interested in special characters
+  and all local files or WWW pages you will view will use the ISO-8859-1
+  "ISO Latin 1" Western European character set.
+
+  If you will be running Lynx in an environment with different incompatible
+  character sets, configure CHARACTER_SET (the Display character set)
+  and ASSUME_LOCAL_CHARSET to work correctly before creating bookmark files
+  and other such items: read lynx.cfg for detailed instructions.
+  Additional character sets and their properties may be defined with tables
+  in the src/chrtrans directory: see the README.* files therein.
+
+Step 4.  News.
+
+  Set NNTPSERVER in lynx.cfg to your site's NNTP server
+  or set the environment variable externally.  For posting to be enabled,
+  NEWS_POSTING must be TRUE in userdefs.h or lynx.cfg.
+  Also define LYNX_SIG_FILE in userdefs.h or lynx.cfg ,
+  so that it points to users' signature files for appending to messages.
+
+Step 5.  Anonymous accounts *** VERY IMPORTANT!!!!! ***
+
+  If you are building Lynx for personal use only, you can skip this.
+
+  If you are setting up anonymous accounts to use Lynx captively,
+  i.e. making Web access publicly available to users who should not
+  be allowed any other type of access to your system,
+  you are STRONGLY advised to use the -anonymous command-line option:
+  if you do not use this option, users may be able to gain access
+  to all readable files on your machine!
+
+  ALSO, many implementations of telnetd allow passing of environment variables,
+  which might be used to modify the environment in anonymous accounts,
+  allowing mischief or damage by malicious users, so make sure the wrapper
+  uses the -cfg and -homepage switches to specify lynx.cfg and start-file,
+  rather than relying on variables LYNX_CFG, LYNX_CFG_FILE and WWW_HOME.
 
 II. Compile instructions -- UNIX
 
@@ -238,11 +250,11 @@
        Do not compile-in code used to connect to FTP servers.
 
   --disable-forms-options              (define NO_OPTION_FORMS)
-       Disable the forms-based options screen.  (See --disable-menu-options).
-       Please note that a few users with broken curses may have problems with
-       popup forms fields.  The default behaviour is to compile both forms and
-       menu options code with FORMS_OPTIONS switch in lynx.cfg, or
-       -forms_options command-line switch.
+       Disable the Form-based Options Menu (cp --disable-menu-options).
+       Note: broken curses may cause problems with pop-up form fields.
+       The default is to compile key-based & form-based Options Menu code,
+       allowing users the final choice via FORMS_OPTIONS in lynx.cfg
+       or the -forms_options command-line switch.
 
   --disable-gopher                     (define DISABLE_GOPHER)
        Do not compile-in code used to connect to GOPHER servers.
@@ -261,11 +273,8 @@
        enabled, the actual directory style is configurable from lynx.cfg).
 
   --disable-menu-options               (define NO_OPTION_MENU)
-       Disable the menu-style options screen.  (See --disable-forms-options).
-       Please note that a few users with broken curses may have problems with
-       popup forms fields.  The default behaviour is to compile both styles
-       options menu code with FORMS_OPTIONS switch in lynx.cfg, or
-       -forms_options command-line switch.
+       Disable the Key-based Options Menu.
+       See --disable-forms-options (above) for further details.
 
   --disable-news                       (define DISABLE_NEWS)
        Do not compile-in code used to connect to NEWS servers.
@@ -274,8 +283,7 @@
        Use this option to disable "Up-to" parent-links in directory listings.
 
   --disable-partial                    (define DISP_PARTIAL)
-       Turn off code that lets Lynx display parts of a long page while loading
-       it.
+       Turn off code which displays parts of a long page while loading it.
 
   --disable-persistent-cookies         (define EXP_PERSISTENT_COOKIES)
        Use this option to tell configure whether to compile-in support for
@@ -296,7 +304,7 @@
        which always lists URLs rather than titles.
 
   --enable-change-exec                 (define ENABLE_OPTS_CHANGE_EXEC)
-       Allow users to change the execution status within the options screen.
+       Allow users to change the execution status within the Options Menu.
        See EXEC_LINKS and EXEC_SCRIPTS.
 
   --enable-cgi-links                   (define LYNXCGI_LINKS)
   
--- old/PROBLEMS        Mon Sep 13 20:07:18 1999
+++ new/PROBLEMS        Fri Nov 26 12:48:39 1999
@@ -127,8 +127,8 @@
     in fact support.  Setting the right TERM environment variable, tweaking
     terminfo or termcap files, or compiling with a newer version of ncurses
     or slang may solve problems with missing highlighting or strange
-    characters appearing on the screen.  Also, for a mono terminal, make sure
-    that there is no "show color (&)  : ON" on the Options screen.
+    characters appearing on the screen.  Also, for a mono terminal,
+    make sure "show color" is not set to ON in the Options Menu.
 
     The Wyse 50 and older TeleVideo terminals, among others, are
     "magic cookie" terminals.  This means that display attributes like
     
--- old/userdefs.h      Sun Nov  7 22:22:46 1999
+++ new/userdefs.h      Fri Nov 26 14:32:42 1999
@@ -1002,9 +1002,8 @@
 #if defined(EXEC_LINKS) || defined(EXEC_SCRIPTS)
 
 /**********
- * if ENABLE_OPTS_CHANGE_EXEC
- * is defined then the user will be able to change
- * the execution status within the options screen.
+ * if ENABLE_OPTS_CHANGE_EXEC is defined, the user will be able to change
+ * the execution status within the Options Menu.
  */
 /* #define ENABLE_OPTS_CHANGE_EXEC */
 
@@ -1012,8 +1011,8 @@
  * if NEVER_ALLOW_REMOTE_EXEC is defined then local execution of
  * scripts or lynxexec and lynxprog URLs will only be implemented
  * from HTML files that were accessed via a "file://localhost/" URL,
- * and the options menu for "L)ocal executions links" will only
- * allow toggling between "ALWAYS OFF" and "FOR LOCAL FILES ONLY".
+ * and the Options Menu for "Local executions links" will allow toggling
+ * only between "ALWAYS OFF" and "FOR LOCAL FILES ONLY".
  */
 /* #define NEVER_ALLOW_REMOTE_EXEC */
 
@@ -1038,16 +1037,14 @@
  * LOCAL_EXECUTION_LINKS_ALWAYS_ON will be FALSE
  * if NEVER_ALLOW_REMOTE_EXEC has been defined.
  *
- * if LOCAL_EXECUTION_LINKS_ALWAYS_OFF_FOR_ANONYMOUS is
- * true all execution links will be disabled when the
- * -anonymous command line option is used.  Anonymous
- * users are not allowed to change the execution options
- * from within the Lynx options menu so you might be able
- * to use this option to enable execution links and set
- * LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE to TRUE to
- * give anonymous execution link capability without compromising
- * your system (see comments about TRUSTED_EXEC rules in
- * lynx.cfg for more information).
+ * if LOCAL_EXECUTION_LINKS_ALWAYS_OFF_FOR_ANONYMOUS is true,
+ * all execution links will be disabled when the -anonymous
+ * command-line option is used.  Anonymous users are not allowed
+ * to change the execution options from within the Lynx Options Menu,
+ * so you might be able to use this option to enable execution links
+ * and set LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE to TRUE
+ * to give anonymous execution-link capability without compromising
+ * your system (see comments about TRUSTED_EXEC rules in lynx.cfg ).
  *
  */
 #define LOCAL_EXECUTION_LINKS_ALWAYS_ON          FALSE
@@ -1133,27 +1130,21 @@
 #define CHECKMAIL      FALSE   /* report unread and new mail messages */
 
 /*********************************
- * VI_KEYS can be changed in lynx.cfg and can be turned on by the user
- * in the options screen or the .lynxrc file.  This is just the default.
- */
-#define VI_KEYS_ALWAYS_ON      FALSE /* familiar h,j,k, & l */
-
-/*********************************
- * EMACS_KEYS can be changed in lynx.cfg and can be turned on by the user
- * in the options screen or the .lynxrc file.  This is just the default.
- */
-#define EMACS_KEYS_ALWAYS_ON   FALSE /* familiar ^N, ^P, ^F, ^B */
+ * Vi or Emacs movement keys.  These are defaults,
+ * which can be changed in lynx.cfg , the Options Menu or .lynxrc .
+#define VI_KEYS_ALWAYS_ON      FALSE /* familiar h j k l */
+#define EMACS_KEYS_ALWAYS_ON   FALSE /* familiar ^N ^P ^F ^B */
 
 /*********************************
- * DEFAULT_KEYPAD_MODE specifies whether by default the user
- * has numbers that work like arrows or else numbered links
- * DEFAULT KEYPAD MODE may be set to
- *     NUMBERS_AS_ARROWS   or
- *     LINKS_ARE_NUMBERED  or
- *     LINKS_AND_FIELDS_ARE_NUMBERED
- *
- * This default setting can be overridden in lynx.cfg (but not to
- * the third value), and it can be changed at run time by the user.
+ * DEFAULT KEYPAD MODE may be set to NUMBERS_AS_ARROWS
+ *                                or LINKS_ARE_NUMBERED
+ *                                or LINKS_AND_FIELDS_ARE_NUMBERED
+ * to specify whether numbers (e.g. [10]) appear before all links,
+ * allowing immediate access by entering the number on the keyboard,
+ * or numbers on the numeric key-pad work like arrows;
+ * the 3rd option causes form fields also to be preceded by numbers.
+ * The first two options (but not the last) can be overridden in lynx.cfg
+ * and all three can be changed via the Options Menu.
  */
 #define DEFAULT_KEYPAD_MODE    LINKS_AND_FIELDS_ARE_NUMBERED
 
--- old/lynx.cfg        Wed Nov  3 19:41:40 1999
+++ new/lynx.cfg        Fri Nov 26 14:25:38 1999
@@ -491,8 +491,8 @@
 #URL_DOMAIN_PREFIXES:www.
 #URL_DOMAIN_SUFFIXES:.com,.edu,.net,.org
 
-# Lynx Options Menu style toggle:  forms-based or old-style.
-# Works if old-style menu is compiled in as well as the forms-based menu.
+# Toggle whether the Options Menu is key-based or form-based;
+# the key-based version is available only if specified at compile time.
 #FORMS_OPTIONS:TRUE
 
 # Display partial pages while downloading
@@ -1070,14 +1070,10 @@
 #
 #USE_FIXED_RECORDS:TRUE
 
-# VI_KEYS can be turned on by the user in the options
-# screen or the .lynxrc file.  This is just the default.
+# Vi or Emacs movement keys, i.e. familiar hjkl or ^N^P^F^B .
+# These are defaults, which can be changed in the Options Menu or .lynxrc .
 #
 #VI_KEYS_ALWAYS_ON:FALSE
-
-# EMACS_KEYS can be turned on by the user in the options
-# screen or the .lynxrc file.  This is just the default.
-#
 #EMACS_KEYS_ALWAYS_ON:FALSE
 
 # DEFAULT_KEYPAD_MODE specifies whether numbers work like arrows or
@@ -1147,22 +1143,20 @@
 #
 #DEFAULT_USER_MODE:NOVICE
 
-# DEFAULT_EDITOR sets the default editor for Lynx users.
-# If an editor is defined then the user may edit local documents
-# using that editor.  The editor will also be used for sending
-# mail messages.  If no editor is defined here or by the user
-# the user will not be able to edit local documents and a primitive
-# line oriented mail input mode will be used.
-# NOTE: Do not define an editor unless you know that every user will
-#       know how to use it.  Most users do not enjoy getting stuck in
-#       an unknown editor that they can't exit.  Users can
-#       easily define an editor of their own using the options menu,
-#       so it is not always desirable to set the DEFAULT_EDITOR.
+# If DEFAULT_EDITOR is defined, users may edit local documents with it
+# & it will also be used for sending mail messages.
+# If no editor is defined here or by the user,
+# the user will not be able to edit local documents
+# and a primitive line-oriented mail-input mode will be used.
+#
+# For sysadmins: do not define a default editor
+# unless you know EVERY user will know how to use it;
+# users can easily define their own editor in the Options Menu.
 #
 #DEFAULT_EDITOR:
 
-# SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR except that it can't be
-# changed.
+# SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR,
+# except that it can't be changed by users.
 #
 #SYSTEM_EDITOR:
 
@@ -1208,10 +1202,12 @@
 # for the .mil domain as well as the .il domain.  If the entry is '.il' this
 # will not happen.
 
-# PRINTER & DOWNLOADER DEFINITIONS:
+# PRINTER, DOWNLOADER & UPLOADER DEFINITIONS:
 # Lynx has 4 pre-defined print options & 1 pre-defined download option,
 # which are called up on-screen when `p' or `d' are entered;
 # any number of options can be added by the user, as explained below.
+# Uploaders can be defined only for UNIX with DIRED_SUPPORT:
+# cp the Makefile in the top directory & the header of  src/LYUpload.c .
 #
 # For `p' pre-defined options are: `Save to local file', `E-mail the file',
 # `Print to screen' and `Print to local printer attached to vt100'.
@@ -1252,7 +1248,7 @@
 # `Printer' can be any file-handling program you find useful,
 # even if it does not physically print anything.
 #
-# Usually, downloading involves the use of (e.g.) Ckermit or ZModem
+# Usually, down/up-loading involves the use of (e.g.) Ckermit or ZModem
 # to transfer files to a user's local machine over a serial link,
 # but download options do not have to be download-protocol programs.
 #
@@ -1285,39 +1281,16 @@
 # by using a script to make a subdirectory in /tmp,
 # but may conflict with very strong security or permissions restrictions:
 #DOWNLOADER:Use Zmodem to download to the local terminal:set %s 
%s;td=/tmp/Lsz$$;mkdir $td;ln -s $1 $td/"$2";sz $td/"$2";rm -r $td:TRUE
-
-# Note for OS/390: The following is strongly recommended  /* S/390 -- gil -- 
1464 */
-# to undo ASCII->EBCDIC conversion.
-#
-#DOWNLOADER:Save OS/390 binary file: iconv -f IBM-1047 -t ISO8859-1 %s 
>%s:FALSE
-
-# Unix ONLY:
-#===========
-# Uploader definitions (implemented only with Unix DIRED_SUPPORT;
-#                       see the Makefile in the top directory,
-#                      and the header of ./src/LYUpload.c)
-# any number of uploaders may be defined by using multiple
-# uploader definition sets.  Uploaders may be any programs
-# that could be useful to your users; they do not necessarily
-# have to be upload protocol programs.  The most common use
-# of an uploader is to use Ckermit or some other transfer
-# program so that the user may easily transfer files from
-# their local machine over a serial link.
-#
-# the definition of an uploader is of the same form as a downloader
-# UPLOADER:<uploadername>:<uploader command>:<uploader option>
 #
-#  You must put the whole definition on one line.
-#
-#  If you must use a colon, precede it with a backslash!
-#
-#  If you do not include a %s, you will not be prompted for an
-#  output filename.
-#
-#    example
+# Uploader examples:
 #UPLOADER:Use Kermit to upload from your computer: kermit -i -r -a %s:TRUE
 #UPLOADER:Use Zmodem to upload from your computer: rz %s:TRUE
 
+# Note for OS/390: /* S/390 -- gil -- 1464 */
+# The following is strongly recommended to undo ASCII->EBCDIC conversion.
+#
+#DOWNLOADER:Save OS/390 binary file: iconv -f IBM-1047 -t ISO8859-1 %s 
>%s:FALSE
+
 # If NO_DOT_FILES is TRUE (normal default via userdefs.h), the user will not
 # be allowed to specify files beginning with a dot in reply to output filename
 # prompts, and files beginning with a dot (e.g., file://localhost/path/.lynxrc)
@@ -1375,7 +1348,7 @@
 # The definition here will override that in userdefs.h
 # and can be toggled via an "-image_links" command-line switch.
 # The user can also use the LYK_IMAGE_TOGGLE key (default `*')
-# or the `Show Images' option in the (new) Options Form.
+# or `Show Images' in the Form-based Options Menu.
 #MAKE_LINKS_FOR_ALL_IMAGES:FALSE
 
 # If MAKE_PSEUDO_ALTS_FOR_INLINES is FALSE, inline images which don't specify
@@ -1388,7 +1361,7 @@
 # The definition here will override that in userdefs.h
 # and can be toggled via a "-pseudo_inlines" command-line switch.
 # The user can also use the LYK_INLINE_TOGGLE key (default `[')
-# or the `Show Images' option in the (new) Options Form.
+# or `Show Images' in the Form-based Options Form.
 #MAKE_PSEUDO_ALTS_FOR_INLINES:TRUE
 
 # If SUBSTITUTE_UNDERSCORES is TRUE, the _underline_ format will be used
@@ -1858,8 +1831,8 @@
 #KEYMAP:x:NOCACHE      # Force submission of form or link with no-cache
 #*** Do not change INTERRUPT from 'z' & 'Z' ***
 #KEYMAP:z:INTERRUPT    # Interrupt network transmission
-#KEYMAP:m:MAIN_MENU    # Return to the main menu
-#KEYMAP:o:OPTIONS      # Show the options menu
+#KEYMAP:m:MAIN_MENU    # Return to the main screen
+#KEYMAP:o:OPTIONS      # Show the Options Menu
 #KEYMAP:i:INDEX_SEARCH # Search a server based index
 #KEYMAP:/:WHEREIS      # Find a string within the current document
 #KEYMAP:n:NEXT         # Find next occurrence of string within document
 
--- old/lynx.hlp        Wed Nov  3 19:41:40 1999
+++ new/lynx.hlp        Fri Nov 26 12:55:08 1999
@@ -184,7 +184,7 @@
               toggles forcing of the secure flag for SSL cookies.
 
        -forms_options
-              toggles the style of options (menu or forms).
+              toggles whether the Options Menu is key-based or form-based.
 
        -from  toggles transmissions of From headers.
 
--- old/lynx.man        Wed Nov  3 19:41:40 1999
+++ new/lynx.man        Fri Nov 26 12:56:21 1999
@@ -198,7 +198,7 @@
 toggles forcing of the secure flag for SSL cookies.
 .TP
 .B -forms_options
-toggles the style of options (menu or forms).
+toggles whether the Options Menu is key-based or form-based.
 .TP
 .B -from
 toggles transmissions of From headers.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto

reply via email to

[Prev in Thread] Current Thread [Next in Thread]