diff --git a/twander.1 b/twander.1 index c9b0615..a6fc2ec 100644 --- a/twander.1 +++ b/twander.1 @@ -1,3 +1,7 @@ +.ds CP 2002-2003 +.ds TW \'twander\' +.ds W3 \'win32all\' + .TH twander 1 "TundraWare Inc." @@ -8,21 +12,21 @@ .SH OVERVIEW Wander around a filesystem executing commands of your choice on selected files and directories. The general idea here is -that \'twander\' provides GUI facilities for navigating around your +that \*(TW provides GUI facilities for navigating around your filesystem, but .B you define the commands you want available via "Command Definitions" in the Configuration File. -If you're new to \'twander\' and want +If you're new to \*(TW and want to know why this program is better and different than whatever you're using at the moment, take a moment to read the section called .B DESIGN PHILOSOPHY toward the end of this document first. -Similarly, if this is the first time you've worked with \'twander\', +Similarly, if this is the first time you've worked with \*(TW, there is a section near the end of this document entitled -.B INSTALLING \'twander\' +.B INSTALLING \*(TW which describes how the program should be installed. @@ -36,7 +40,7 @@ Directory in which to begin. (default: directory in which program was started) -If this directory does not exist or cannot be opened, \'twander\' +If this directory does not exist or cannot be opened, \*(TW will display an error message and abort. .TP @@ -44,9 +48,9 @@ Specify the location and name of the configuration file. (default is ~/.twander) -If this file does not exist or cannot be opened, \'twander\' will +If this file does not exist or cannot be opened, \*(TW will display a warning to that effect but continue to run. This is -reasonable behavior because \'twander\' provides a command to reload +reasonable behavior because \*(TW provides a command to reload the Configuration File without exiting the program (which you would presumably do after fixing the Configuration File problem). @@ -55,7 +59,7 @@ Start in debug mode dumping the items specified in the debuglevel. (default: debuglevel=0/debug off) -\'twander\' is able to selectively dump debugging information to +\*(TW is able to selectively dump debugging information to stdout. \'debuglevel\' is understood to be a bitfield in which each bit specifies some kind of debugging information or behavior. \'debuglevel\' can be specified in either decimal @@ -98,11 +102,11 @@ Turn off automatic refreshing of directory display. (default: refresh on) -Normally \'twander\' re-reads and displays the current directory +Normally \*(TW re-reads and displays the current directory every few seconds to reflect any changes that might have occurred to that directory's contents. This option is useful on slow machines (or slow X connections) and/or when working with very large directories. -In this situation, the frequent updating of the \'twander\' display +In this situation, the frequent updating of the \*(TW display can make the program unacceptably slow and unresponsive. In this case you can still force an update manually with the REFRESH function (default assignment is to the Control-l key). @@ -111,7 +115,7 @@ .B -t Turn off quoting when substituting built-in variables. (default: quoting on) -Anytime \'twander\' encounters a reference to one of the built-in +Anytime \*(TW encounters a reference to one of the built-in variables which do string replacement (DIR, DSELECTION, DSELECTIONS, MEM1-12, PROMPT:, SELECTION, SELECTIONS) in a command, it will replace them with @@ -126,10 +130,10 @@ Print detailed version information. -.SH OTHER WAYS TO SET \'twander\' OPTIONS +.SH OTHER WAYS TO SET \*(TW OPTIONS In addition to these command line options, there are two other ways -you can set \'twander\' program features. If you prefer, you +you can set \*(TW program features. If you prefer, you can set the command line options via the environment variable, TWANDER. That way you don't have to type them in each time you start the program. Say you set the environment variable this way @@ -147,7 +151,7 @@ by setting the appropriate entries in the Configuration File. This is covered later in this document. -\'twander\' evaluates options in the following order (from first +\*(TW evaluates options in the following order (from first to last: .IP \(bu 4 @@ -182,15 +186,15 @@ If the Configuration File is reloaded while the program is running (see the READCONF key below), any options set in the file will have the last word. This allows you to edit the Configuration File and -have your changes reflected in a running instance of \'twander\', but +have your changes reflected in a running instance of \*(TW, but it also means that the environment variable/command line arguments are ignored after initial program startup. .SH KEYBOARD USE -By design, \'twander\' allows you to do almost everything of interest -using only the keyboard. Various \'twander\' features are thus +By design, \*(TW allows you to do almost everything of interest +using only the keyboard. Various \*(TW features are thus associated with particular keystrokes which are described below. It is also very simple to change the default key assignments with entries in the Configuration File, also described below. @@ -204,13 +208,13 @@ X-Windows is somewhat more problematic in this area. Just what an arrow key is "supposed" to do depends on how it's been mapped in your X -server software. Testing \'twander\' on various X servers showed +server software. Testing \*(TW on various X servers showed quite a bit of variability in how they handled the arrows and keypad. So ... if you're running in an X Windows universe and arrows or keypad do nothing, or do strange things, look into your key maps, don't blame -\'twander\'. +\*(TW. -There are several features of \'twander\' that will present the user a +There are several features of \*(TW that will present the user a text entry dialog. These include the CHANGEDIR and RUNCMD features as well as the [PROMPT:...] Built-In Variable (all described below). @@ -225,7 +229,7 @@ .SH DEFAULT KEYBOARD AND MOUSE BINDINGS Here, ordered by category, are the default keyboard and mouse -bindings for \'twander\'. The general format is: +bindings for \*(TW. The general format is: .TP .B Description (Program Function Name) @@ -236,27 +240,27 @@ .PD .P -The "Program Function Name" is the internal variable \'twander\' +The "Program Function Name" is the internal variable \*(TW uses to associate a particular feature with a particular keystroke or mouse action. You can ignore it unless you intend to override the default key assignments. This use is described below in the section entitled, .B Key Binding Statements. -It is important to realize that \'twander\' key-bindings are +It is important to realize that \*(TW key-bindings are .B case-sensitive. This means that \'Control-b\' and \'Control-B\' are different. This was a conscious design decision because it effectively doubles the number of Control/Alt key combinations available for the addition of future features. -The default bindings chosen for \'twander\' features are all currently +The default bindings chosen for \*(TW features are all currently .B lower-case. If your program suddenly stops responding to keyboard commands, check to make sure you don't have CapsLock turned on. .B NOTE: -Some \'twander\' features are doubled on the mouse. These mouse +Some \*(TW features are doubled on the mouse. These mouse button assignments are documented below for the sake of completeness. However, .B mouse button assignments cannot be changed by the user, @@ -264,7 +268,7 @@ .SS General Program Commands -This family of commands controls the operation of \'twander\' itself. +This family of commands controls the operation of \*(TW itself. .TP .B Clear History (CLRHIST) @@ -289,15 +293,15 @@ Increase font size. These two features allow you to change the display font sizes while -\'twander\' is running. But, you may not immediately get the results -you expect. \'twander\' internally keeps track of separate font +\*(TW is running. But, you may not immediately get the results +you expect. \*(TW internally keeps track of separate font sizes for the main display, the main menu text, and the help menu -text. When you use the two font sizing commands above, \'twander\' +text. When you use the two font sizing commands above, \*(TW subtracts or adds 1 to each of these three values respectively. On systems like Win32 using TrueType fonts, this works as you would expect, because every font is effectively available in every size. However, in systems like X-Windows or Win32 using fixed-size fonts, -you may have to press these keys repeatedly until \'twander\' finds +you may have to press these keys repeatedly until \*(TW finds a font matching the requested size. This can also cause some parts of the display to change but not @@ -307,7 +311,7 @@ available larger than 12 point is 16 point. If you press FONTINCR twice, both the menu text and help text will jump to 12 point, but the main display text will remain unchanged. Why? Because pressing -FONTINCR twice tells \'twander\' to set the main display to 14 point +FONTINCR twice tells \*(TW to set the main display to 14 point (12+1+1) which does not exist, and the menu and help text to 12 point (10+1+1) which does exist, so that change is visible. @@ -338,7 +342,7 @@ Command Menu at the top of the GUI, or via selection from the Command Menu. -Win32 users should note that, unlike Windows Explorer, the \'twander\' +Win32 users should note that, unlike Windows Explorer, the \*(TW Command Menu does not change the set of currently selected items. It merely provides a list of available commands. This allows the command chosen via the Command Menu to operate on a previously @@ -377,7 +381,7 @@ Control-r Re-read the Configuration File. This allows you to edit the -Configuration File while \'twander\' is running and then read your +Configuration File while \*(TW is running and then read your changes in without having to exit the program. This is handy when editing or changing Command Definitions. @@ -406,14 +410,14 @@ Toggle between detailed and filename-only views of the directory. .TP -.B Toggle \'win32all\' Features (TOGWIN32ALL) +.B Toggle \*(W3 Features (TOGWIN32ALL) Control-w -As described later in this document, \'twander\' provides enhanced -features for Win32 users who also install Mark Hammond's \'win32all\' +As described later in this document, \*(TW provides enhanced +features for Win32 users who also install Mark Hammond's \*(W3 extensions for Python on Win32. This key binding will toggle those advanced features on- and off. This is useful if you happen to -be examining a very large directory. The \'win32all\' features, +be examining a very large directory. The \*(W3 features, while handy, can be computationally expensive and make updates of a directory with many entries somewhat slow. This toggle is provided as a means to temporarily disable the advanced features when viewing @@ -423,11 +427,11 @@ This family of commands controls movement between directories. If you attempt to navigate into a directory that does not exist or which does -not have appropriate permissions, \'twander\' will display a warning +not have appropriate permissions, \*(TW will display a warning message and remain in the current directory. This is .B unlike the case of a non-existent or unreadable directory specified when the program -is first started. In that case, \'twander\' reports the error and aborts. +is first started. In that case, \*(TW reports the error and aborts. .TP .B Change Directory (CHANGEDIR) @@ -460,7 +464,7 @@ Control-DoubleClick-Left-Mouse-Button .PD -\'twander\' keeps track of every directory visited and the order in +\*(TW keeps track of every directory visited and the order in which they are visited. This command allows you to move back successively until you get to the directory in which you started. This feature is implemented as a stack - each "backing up" removes @@ -479,7 +483,7 @@ .B Go To Starting Directory (DIRSTART) Control-s -Go back to the original directory in which \'twander\' was started. +Go back to the original directory in which \*(TW was started. .TP .B Go Up To Parent Directory (DIRUP and MOUSEUP) @@ -500,7 +504,7 @@ This is a Win32-only feature which displays a list of all available disk drives. Details about each drive are also displayed if you have details enabled. In order for this feature to work, you must be -running on Win32 AND have the \'win32all\' package installed, AND the +running on Win32 AND have the \*(W3 package installed, AND the USEWIN32ALL Program Option must be True (default condition,) AND you must not have toggled these features off with the TOGWIN32ALL key described above. For more details about Drive List View, see the @@ -578,7 +582,7 @@ .SS Scrolling Commands If a given directory's contents cannot be displayed on a single -screen, \'twander\' supports both vertical and horizontal scrolling +screen, \*(TW supports both vertical and horizontal scrolling via scrollbars. This capability is doubled on the keyboard with: .TP @@ -607,7 +611,7 @@ .SS Command Execution Options -This family of commands causes \'twander\' to actually +This family of commands causes \*(TW to actually attempt to execute some command you've chosen: .TP @@ -621,7 +625,7 @@ You may enter a number of different things in the RUNCMD dialog. You may type literal text or refer to any of the variable types -(User-Defined, Environment, or Built-In) supported by \'twander\' just +(User-Defined, Environment, or Built-In) supported by \*(TW just as you do in writing Command Definitions (see below). This makes it easy to enter complex commands without having to type everything literally. For example, if you would like to copy all the currently @@ -631,12 +635,12 @@ cp [SELECTIONS] newdir .fi -\'twander\' understands the variable reference syntax here just as it +\*(TW understands the variable reference syntax here just as it does in a Command Definition. This also gives you a single way of referring to environment variables, regardless of OS platform. Recall that in Unix-like shells, an environment variable is in the form "$NAME", but on Win32 it is in the form "%NAME%". Instead if having -to keep track of this difference, you can just use a \'twander\' +to keep track of this difference, you can just use a \*(TW Environment Variable reference. For instance, assuming the EDITOR environment variable is set, this command works the same on both systems: @@ -670,14 +674,14 @@ DoubleClick-Left-Mouse-Button .PD -If the selected item is a Directory, \'twander\' will move into +If the selected item is a Directory, \*(TW will move into that directory when this command is issued. If the selected item -is a file, \'twander\' will attempt to execute it. Whether or not +is a file, \*(TW will attempt to execute it. Whether or not the file is actually executed depends on how the underlying operating system views that file. In the case of Unix-like operating systems, the execute permission -must be set for the user running \'twander\' (or their group) for the +must be set for the user running \*(TW (or their group) for the file to be executed. On Win32, the file will be executed if the user has permission to do @@ -689,7 +693,7 @@ the \'notepad\' program (unless the association for ".txt" has been changed). -If \'twander\' determines that it is running on neither a Unix-like +If \*(TW determines that it is running on neither a Unix-like or Win32 system, double-clicking on a file does nothing. .TP @@ -703,7 +707,7 @@ .SS Directory Shortcuts -\'twander\' provides a way to directly navigate into a frequently-used +\*(TW provides a way to directly navigate into a frequently-used directory using a single keystroke. You can define up to 12 such "Directory Shortcuts" in the Configuration File. Each of the definitions is associated with one of the following 12 keys: @@ -736,10 +740,10 @@ It would be nice if we could not only keep adding things to the Clipboard, but be able to do so as we navigate around the filesystem. -\'twander\' addresses these concerns by means of 12 separate "Program -Memories". As you use \'twander\', you can add (append) the names of +\*(TW addresses these concerns by means of 12 separate "Program +Memories". As you use \*(TW, you can add (append) the names of any directories or files in the currently viewed directory by -selecting them and then using the appropriate \'twander\' MEMSETx key +selecting them and then using the appropriate \*(TW MEMSETx key (see below). To take advantage of this feature, you write Command Definitions (or manually issue a command via the RUNCMD key) which reference the contents of a Program Memory using one of the [MEMx] @@ -747,7 +751,7 @@ .B Program Memory Built-Ins for more details in how to apply Program Memories). -\'twander\' provides key combinations for selectively setting and +\*(TW provides key combinations for selectively setting and clearing particular Program Memories as well as a key combination for clearing all Program Memories in a single keystroke: @@ -775,9 +779,9 @@ .SH MENU OPTIONS -Although \'twander\' is primarily keyboard-oriented, several +Although \*(TW is primarily keyboard-oriented, several menu-based features are also implemented to make the program more -convenient to use. These menus appear at the top of the \'twander\' +convenient to use. These menus appear at the top of the \*(TW display window, above the directory listing. A menu can be invoked in one of several ways. You can click on it, @@ -789,9 +793,9 @@ The first item in each menu is a dashed line ("----") which indicates that it is a "tearoff" menu. Clicking on the dashed line will detach -the menu from \'twander\' allowing it to be placed anywhere on screen. +the menu from \*(TW allowing it to be placed anywhere on screen. Even when detatched, these menus remain current and in-sync with -\'twander\' as it continues to run. You can also tear off multiple +\*(TW as it continues to run. You can also tear off multiple instances of these menus if you'd like copies of them at several locations on the screen simultaneously. @@ -800,7 +804,7 @@ bottom of the menu respectively. This is not a feature of the Unix Tk implementation, so menus which grow too large are simply truncated to fit the screen on Unix-like systems. As described in the following -paragraphs, \'twander\' provides some options to limit the size of the +paragraphs, \*(TW provides some options to limit the size of the Directory and History menus for this reason. .SS Commands Menu (Alt-c) [Right-Mouse-Button] @@ -822,7 +826,7 @@ .SS Directories Menu (Alt-d) [Shift-Right-Mouse-Button] -\'twander\' keeps track of every directory visited. The previously +\*(TW keeps track of every directory visited. The previously described command to move "Back" one directory allows directory navigation in reverse traversal order - you can back up to where you started. However, this feature "throws away" directories as it backs up, sort @@ -845,7 +849,7 @@ the tracking of the last manually entered directory via the CHANGEDIR key. (default: Control-x) -MAXDIRBUF specifies how many directories \'twander\' keeps track +MAXDIRBUF specifies how many directories \*(TW keeps track of internally, no matter how many are actually displayed. It defaults to 250. @@ -861,7 +865,7 @@ .SS History Menu (Alt-h) [Shift-Control-Right-Mouse-Button] -\'twander\' keeps track of every command you attempt to execute, +\*(TW keeps track of every command you attempt to execute, whether it is an invocation of a Command Definition found in the Configuration File or a manually entered command via the RUNCMD key. (default: Control-z) This is done whether or not the command is @@ -882,7 +886,7 @@ the tracking of the last manually entered command via the RUNCMD key. -MAXHISTBUF specifies how many previously-run commands \'twander\' +MAXHISTBUF specifies how many previously-run commands \*(TW keeps track of internally, no matter how many are actually displayed. It defaults to 250. @@ -908,7 +912,7 @@ .SS Help Menu (Alt-l) [No Mouse Shortcut] This menu provides information about various internal settings of -\'twander\' including User-Defined Variables, Command Definitions, +\*(TW including User-Defined Variables, Command Definitions, Internal Program Variables, User-Settable Options, Keyboard Assignments, and Directory Shortcuts. It also has an About feature which provides version and copyright information about the program. @@ -916,15 +920,15 @@ For the most part, this help information should fit on screen easily. However, very long Command Definitions will probably not fit on-screen once User-Defined and Environment Variables have been substituted. In -this case, if you are curious about just how \'twander\' is +this case, if you are curious about just how \*(TW is interpreting your Command Definitions, invoke the program with the relevant debug bit turned on and watch the output on stdout as -\'twander\' runs. +\*(TW runs. -.SH THE \'twander\' CONFIGURATION FILE +.SH THE \*(TW CONFIGURATION FILE -Much of \'twander\'s flexibility comes from the fact that it is +Much of \*(TWs flexibility comes from the fact that it is a .B macro-programmable user interface. The program itself does little more than provide a way to navigate @@ -943,10 +947,10 @@ but you can override this with the -c command line option. (Recommended for Win32 systems - see the section below entitled, -.B INSTALLING \'twander\' +.B INSTALLING \*(TW ) -Actually, \'twander\' can look in a number +Actually, \*(TW can look in a number of places to find its Configuration File. It does this using the following scheme (in priority order): @@ -963,17 +967,17 @@ .B and a -c command line argument was not provided, look for a file called ".twander" in the directory from which -\'twander\' was invoked. +\*(TW was invoked. .SH CONFIGURATION FILE FORMAT -\'twander\' Configuration Files consist of freeform lines of text. +\*(TW Configuration Files consist of freeform lines of text. Each line is considered independently - no configuration line may cross into the next line. Whitespace is ignored within a line as are blank lines. -There are several possible legal lines in a \'twander\' Configuration +There are several possible legal lines in a \*(TW Configuration File: .nf @@ -987,16 +991,16 @@ (See the ".twander" file provided with the program distribution for examples of valid configuration statements.) -Everything else is considered invalid. \'twander\' will respond with +Everything else is considered invalid. \*(TW will respond with errors or warnings as is appropriate anytime it encounters a problem in a Configuration File. An error will cause the program to terminate, but the program continues to run after a warning. For the -most part, \'twander\' tries to be forgiving and merely ignores +most part, \*(TW tries to be forgiving and merely ignores invalid configuration statements (after an appropriate warning). It only declares an error when it cannot continue. This is true both when the program initially loads as well as during any subsequent Configuration File reloads initiated from the keyboard while running -\'twander\'. +\*(TW. The following sections describe each of the valid Configuration File entires in more detail. @@ -1005,7 +1009,7 @@ A comment is begun with the "#" character which may be placed anywhere on a line. Comments may appear freely within a Configuration File. -\'twander\' strictly ignores everything from the "#" to the end of the +\*(TW strictly ignores everything from the "#" to the end of the line on which it appears without exception. This means that "#" cannot occur anywhere within a User-Defined Variable Definition, Key Binding Statement, or Command Definition (these are described below). @@ -1014,7 +1018,7 @@ be placed on the same line to the right of such statements. It is conceivable that the "#" character might be needed in the -Command String portion of a Command Definition. \'twander\' +Command String portion of a Command Definition. \*(TW provides a Built-In Variable, [HASH], for exactly this purpose. See the section below entitled, .B Variables And Command Definitions, @@ -1022,10 +1026,10 @@ .SS Program Option Statements -Many of \'twander\'s internal program defaults can be overriden in the +Many of \*(TWs internal program defaults can be overriden in the Configuration File using Program Option statements. These statements look just like the User-Defined variables described later in this -document except \'twander\' recognizes the variable name as a Program +document except \*(TW recognizes the variable name as a Program Option rather than an arbitrary variable. Program Option Statements thus take the form: @@ -1034,7 +1038,7 @@ .fi The Option Name is case-sensitive and must be entered exactly as -described below. For instance, \'twander\' understands +described below. For instance, \*(TW understands "AUTOREFRESH" as a Program Option, but will treat "AutoRefresh" as a User-Defined Variable. @@ -1060,19 +1064,19 @@ .fi Furthermore, as described above, you cannot use the \'#\' symbol -as part of the string assignment because \'twander\' always +as part of the string assignment because \*(TW always treats this character as the beginning of a comment no matter where it appears. -Other than this basic type-checking, \'twander\' does no further +Other than this basic type-checking, \*(TW does no further validation of the Right Hand Side of a Program Option Statement. -It is perfectly possible to provide a RHS which passes \'twander\'s +It is perfectly possible to provide a RHS which passes \*(TWs type validation but which makes no sense whatsoever to the program. -Entries like this cause everything from a mild \'twander\' warning +Entries like this cause everything from a mild \*(TW warning to a spectacular program failure and Python traceback on stdout: .nf -# A Nice Way To Clobber \'twander\' +# A Nice Way To Clobber \*(TW BCOLOR = goo .fi @@ -1086,7 +1090,7 @@ .TP .B AUTOREFRESH [Boolean] (True) -By default, \'twander\' regularly re-reads the current directory to +By default, \*(TW regularly re-reads the current directory to refresh the display with any changes. If you are running on a very slow machine or slow connection between the X-Windows server and client, set this option to False. You can manually force an update at @@ -1101,7 +1105,7 @@ .TP .B CMDSHELL [String] ("") -This option is primarily intended for people running \'twander\' on +This option is primarily intended for people running \*(TW on Unix-like operating systems like FreeBSD and Linux. As described in the .B GOTCHAS @@ -1171,7 +1175,7 @@ CMDSHELL processing, even though that feature has been defined in the Configuration File. You can disable CMDSHELL operation on a per-RUNCMD basis. Just begin your entering your command with the -backslash (\\) character. \'twander\' understands this to "escape" +backslash (\\) character. \*(TW understands this to "escape" CMDSHELL processing. As a general matter, CMDSHELL allows you to prepend @@ -1227,7 +1231,7 @@ .TP .B HEIGHT [Numeric] (600) -Initial vertical size of the \'twander\' window in pixels. +Initial vertical size of the \*(TW window in pixels. .TP .B HFCOLOR [String] (black) @@ -1255,15 +1259,15 @@ Maximum number of entries to .B display in the Directory Menu. This keeps the menu size reasonable. -Internally, \'twander\' keeps track of way more than this +Internally, \*(TW keeps track of way more than this number of directories (see the MAXDIRBUF option below). .TP .B MAXDIRBUF [Numeric] (250) -Maximum number of visited directories \'twander\' +Maximum number of visited directories \*(TW .B tracks internally. This value need normally not be changed. It is present only -to bound how much memory \'twander\' consumes for this task. +to bound how much memory \*(TW consumes for this task. .TP .B MAXHIST [Numeric] (32) @@ -1271,15 +1275,15 @@ Maximum number of entries to .B display in the History Menu. This keeps the menu size reasonable. -Internally, \'twander\' keeps track of way more than this +Internally, \*(TW keeps track of way more than this number of commands (see the MAXHISTBUF option below). .TP .B MAXHISTBUF [Numeric] (250) -Maximum number of commands executed \'twander\' +Maximum number of commands executed \*(TW .B tracks internally. This value need normally not be changed. It is present only -to bound how much memory \'twander\' consumes for this task. +to bound how much memory \*(TW consumes for this task. .TP .B MAXNESTING [Numeric] (32) @@ -1294,7 +1298,7 @@ x mycmd [BAM] [SELECTION] .fi -When you press the x key, the \'twander\' command interpreter has to +When you press the x key, the \*(TW command interpreter has to process the line repeatedly until all variables are resolved: .nf @@ -1311,12 +1315,12 @@ FOO = x[FOO] .fi -This kind of construct will cause \'twander\' to iterate +This kind of construct will cause \*(TW to iterate MAXNESTING number of times and then give up with a warning about exeeding the nesting (dereferencing) limit. A 32 iteration limit should be plenty for any reasonable -Command Definitions. If you set MAXNESTING to 0, \'twander\' +Command Definitions. If you set MAXNESTING to 0, \*(TW will not allow .B any variable dereferencing, @@ -1364,7 +1368,7 @@ Prevents the user from navigating out of the starting directory. Command Definitions and commands initiated manually via RUNCMD (default: Control-z) can still "see" other directories, the user -just cannot move elsewhere with any of the \'twander\' navigation +just cannot move elsewhere with any of the \*(TW navigation commands. The NODETAILS and NONAVIGATE commands are @@ -1376,7 +1380,7 @@ Say you want to define a few simple commands for your boss to use which won't challenge his or her feeble managerial mind ;) By defining these commands and setting both NODETAILS and NONAVIGATE -to TRUE, you really limit what can be done with \'twander\'. +to TRUE, you really limit what can be done with \*(TW. They can't wander off into other directories and get lost, or worse yet, clobber files they don't understand. There are no details to confuse them. Your instructions for using the program @@ -1392,7 +1396,7 @@ .TP .B QUOTECHAR [String] (") -As described below, \'twander\' ordinarily quotes most Built-In +As described below, \*(TW ordinarily quotes most Built-In Variables as it replaces them during command processing. This is useful because modern operating systems allow file and directory names to have spaces in them. Such names must be @@ -1424,14 +1428,14 @@ than the default of 3 seconds), but it can be off this nominal value by quite a bit. -If you run \'twander\' on a slow system (or have a slow link between +If you run \*(TW on a slow system (or have a slow link between X-Client and X-Server) you might want to increase this value substantially. You can get into the situtation where just as one -refresh completes, its time to do the next one, and the \'twander\' +refresh completes, its time to do the next one, and the \*(TW will seem really sluggish and unresponsive. By lengthening the time between automatic updates, the amount of unresponsive behavior is reduced. Of course, this also means that any changes in the currently -viewed directory will also take longer to appear in the \'twander\' +viewed directory will also take longer to appear in the \*(TW display. .TP @@ -1447,22 +1451,22 @@ .TP .B STARTX [Numeric] (0) -Initial horizontal offset of the \'twander\' window in pixels. +Initial horizontal offset of the \*(TW window in pixels. .TP .B STARTY [Numeric] (0) -Initial vertical offset of the \'twander\' window in pixels. +Initial vertical offset of the \*(TW window in pixels. .TP .B USETHREADS [Boolean] (True) -Normally, \'twander\' uses threads to run the commands you've +Normally, \*(TW uses threads to run the commands you've defined/entered and requested. As noted later in the .B GOTCHAS section, there are circumstances under which this does not work properly. In this case setting USETHREADS=False, -will cause \'twander\' to use more traditional process +will cause \*(TW to use more traditional process mechanics to run a command. This option applies only to Unix-like operating systems. @@ -1474,17 +1478,17 @@ .TP .B USEWIN32ALL [Boolean] (True) -Win32 only. If \'win32all\' is installed, determines whether its +Win32 only. If \*(W3 is installed, determines whether its features should be used (see section below entitled, .B ADVANCED WIN32 FEATURES for details). Normally, this option should be left alone. However, if you have -\'win32all\' installed on your system for some other reason, but don't -want it used by \'twander\', set this option to False. +\*(W3 installed on your system for some other reason, but don't +want it used by \*(TW, set this option to False. The main reason to do this would be on a slow machine with very large -directories. The advanced features of \'win32all\' come at a +directories. The advanced features of \*(W3 come at a computational price. This is especially noticeable when it is computing the attributes, ownership, and size in a directory with hundreds (or more) of entries. Typically, you would just use the @@ -1497,7 +1501,7 @@ .B WARN [Boolean] (True) Determines whether interactive warnings should be displayed -as \'twander\' encounters them (while parsing a Configuration +as \*(TW encounters them (while parsing a Configuration File or just in normal execution). Setting this option to False is the same thing as using the @@ -1510,7 +1514,7 @@ top of your Configuration File will suppress this. It is not recommended that you operate normally with the --q flag or with WARN=False. \'twander\' is pretty +-q flag or with WARN=False. \*(TW is pretty forgiving in most cases and when it does warn you about something, there is a good reason for it - you probably want to know what the problem is. @@ -1518,14 +1522,14 @@ .TP .B WIDTH [Numeric] (800) -Initial horizontal size of the \'twander\' window in pixels. +Initial horizontal size of the \*(TW window in pixels. .P A few general notes about Program Options are worth mentioning here: .IP \(bu 4 You can set the same option multiple times in a single -Configuration File - \'twander\' pays no attention. +Configuration File - \*(TW pays no attention. However, only the .B last (the one nearest the end of the file) instance of that Program Option @@ -1552,14 +1556,14 @@ actually exist on your system. If your setting in the Configuration File seems not to work, take a -look at the command window in which you started \'twander\' (or start +look at the command window in which you started \*(TW (or start it from one manually, if you're using a GUI shortcut to start it). Attempts to use unavailable colors and weights will cause Python/Tkinter to dump traceback information on stdout. .IP \(bu 4 -Although you can use proportionally spaced fonts with \'twander\', -the result is pretty ugly. \'twander\' assumes a fixed width +Although you can use proportionally spaced fonts with \*(TW, +the result is pretty ugly. \*(TW assumes a fixed width font when it calculates display formatting. Variable-width fonts will cause your display to be ragged and hard to read. @@ -1577,7 +1581,7 @@ Changing either MAXDIR or MAXHIST and then reloading the Configuration File only changes .B the number of items visible on their respective menus. -\'twander\' actually keeps track of more than this internally +\*(TW actually keeps track of more than this internally (governed by the MAXDIRBUF and MAXHISTBUF options). Say MAXDIR and MAXHIST are set to 4, but you've actually visited 20 @@ -1589,10 +1593,10 @@ .IP \(bu 4 At first glance, the ability to set QUOTECHAR to any arbitary string may seem silly, but it actually has a purpose. As good as the -\'twander\' macro capability is, it is still a fairly simple language. +\*(TW macro capability is, it is still a fairly simple language. Really complex tasks will need to be handed off to some other scripting language (like Python!). It may be useful to delimit -Built-In Variables (which indicate your selections via the \'twander\' +Built-In Variables (which indicate your selections via the \*(TW interface) in such a way that your script knows where they came from. So, say you set QUOTECHAR=+++ and you have a Command Definition like this: @@ -1602,7 +1606,7 @@ .fi When MyPythonScript runs, it can immediately tell which arguments -came from \'twander\' (the ones that are in the form +++dir+++ +came from \*(TW (the ones that are in the form +++dir+++ or +++file+++) and which arguments are just other stuff. You probably won't need this often, but its nice to have. @@ -1621,14 +1625,14 @@ everyone's (anyone's!) idea of what the "correct" key bindings should be. An emacs user, vi user, BSD user, and Windows user are going to differ considerably on what keys should be bound to what -feature. \'twander\' ships from the factory with a set of default key +feature. \*(TW ships from the factory with a set of default key bindings, but it also provides a mechanism for changing these bindings via entries in the Configuration File. This feature is available only for .B Keyboard Assignments. Mouse Button Assignments may not be changed by the user. An attempt -to do so in the Configuration File will cause \'twander\' to display a +to do so in the Configuration File will cause \*(TW to display a warning and ignore the offending line. It is not difficult to override the default keyboard bindings by @@ -1648,7 +1652,7 @@ both in print and on the Internet.) Keyboard binding assignments look just like variable definitions -in the Configuration File. (The \'twander\' Configuration File parser +in the Configuration File. (The \*(TW Configuration File parser automatically distinguishes between Key Binding Statements and Variable Definitions or other legitimate statements. This means you can never use one of the program function names as one of your own @@ -1693,7 +1697,7 @@ .IP \(bu 4 The Program Function Name variables (the left side of the assignment) may not be used as names for your own user-defined variables elsewhere -in the Configuration File. In fact, \'twander\' will never even +in the Configuration File. In fact, \*(TW will never even recognize such an attempt. For example, suppose you try to do this: .nf @@ -1701,11 +1705,11 @@ .fi Because you want to be able to reference [QUITPROG] in a subsequent -Command Definition. \'twander\' will actually interpret this as just +Command Definition. \*(TW will actually interpret this as just another key binding command, in this case binding the program function QUITPROG to "something-or-other" - probably not what you intended. Moreover, if you have a Command String somewhere with [QUITPROG] in it, -\'twander\' will declare and error and abort because it has no +\*(TW will declare and error and abort because it has no User-Defined variable of that name in its symbol table. .IP \(bu 4 @@ -1714,15 +1718,15 @@ the new bindings. .IP \(bu 4 -Be aware that \'twander\' does no sanity testing on the assignments -you change. If you assign a particular \'twander\' function to +Be aware that \*(TW does no sanity testing on the assignments +you change. If you assign a particular \*(TW function to an illegal or silly key string, the program will probably blow-up spectacularly. At the very least, that program feature will probably -be unusable, even if \'twander\' manages to run. +be unusable, even if \*(TW manages to run. .SS Directory Shortcut Statements -\'twander\' provides a mechanism for directly navigating into one +\*(TW provides a mechanism for directly navigating into one of 12 frequently used directories. 12 keys, KDIRSC1 ... KDIRSC12 (default: F1 ... F12) have been set aside for this purpose. Directory Shortcut Statements are entries in the Configuration File which @@ -1747,7 +1751,7 @@ understand: .IP \(bu 4 -You can end the path with slash or not - \'twander\' +You can end the path with slash or not - \*(TW will understand the entry either way. .IP \(bu 4 @@ -1771,12 +1775,12 @@ Configuration File reload) whether or not you've actually visited those directories. The assumption is that you will be visiting these directories a lot (which is why -you've defined shortcuts to them), so \'twander\' also +you've defined shortcuts to them), so \*(TW also makes them available in the directory "history" for easy access. .IP \(bu 4 -\'twander\' does absolutely no checking of what you enter +\*(TW does absolutely no checking of what you enter to the right of the equals sign. If you enter something silly for the shortcut path, you will probably get a warning that the directory cannot be opened when you try to run that @@ -1793,29 +1797,29 @@ .IP \(bu 4 If you enter a Directory Shortcut Name that is invalid or out of range - examples include, DIRSC01 and DIRSC13 - -\'twander\' treats them like a User-Defined Variable as +\*(TW treats them like a User-Defined Variable as described below. .SS Variables And Command Definitions Most programs "ship from the factory" with a pre-defined -set of features or commands. \'twander\' comes with +set of features or commands. \*(TW comes with .B no built-in commands! Instead, it comes with a mechanism which allows you to specify your own .B Command Definitions. By means of a simple and very powerful macro lanuage, you "program" -\'twander\' and equip it with commands of your own choosing. For +\*(TW and equip it with commands of your own choosing. For example, you might define commands to copy, delete, edit, and move the files or directories you choose. Perhaps you have a specialized shell -script for doing backups. It's a simple matter to write a \'twander\' +script for doing backups. It's a simple matter to write a \*(TW Command Definition that will pass the names of the files and directories you've selected to that backup script. You might combine -this with \'twander\'s Program Memory feature to keep a running list +this with \*(TWs Program Memory feature to keep a running list of the files and directories you want to backup and then finally issue the backup command when you're ready. Best of all, commands you define this way are always a single keystroke. This means that -once you've programmed \'twander\' to suit your needs, actually using +once you've programmed \*(TW to suit your needs, actually using it is very fast and convenient. Command Definitions are built out of literal text and may also have @@ -1865,7 +1869,7 @@ Here are several other subtleties regarding User-Defined Variables: .IP \(bu 4 -\'twander\' variable definitions are nothing more than a +\*(TW variable definitions are nothing more than a string substitution mechanism. Suppose you have a variable definition that refers to another variable: @@ -1902,7 +1906,7 @@ FB = [Var1][Var2] .fi -Later on (when defining some command) when \'twander\' runs into the +Later on (when defining some command) when \*(TW runs into the variable reference [FB], it will keep substituting variables until all [...] references have been resolved or it hits the nesting limit (The default is 32, but you can change it with the MAXNESTING option). @@ -1912,7 +1916,7 @@ Var = a[Var] .fi -This recursive definition is a no-no and will be cause \'twander\' +This recursive definition is a no-no and will be cause \*(TW to generate an error while parsing the Configuration File and then terminate. @@ -1976,7 +1980,7 @@ .IP \(bu 4 A Variable Name must never begin with "$". This is because a Command Definition containing a string in the form [$something] is understood -by \'twander\' to be a reference to an +by \*(TW to be a reference to an .B Environment Variable, named "something". If you do this: @@ -1985,7 +1989,7 @@ .fi You will never be able to subsequently reference it because, -[$MYVAR] tells \'twander\' to look in the current environment, +[$MYVAR] tells \*(TW to look in the current environment, not its own symbol table to resolve the reference. However, note that "$" symbol may appear anywhere else but the first character of a variable name. So, for example, MY$VAR is fine. @@ -2000,11 +2004,11 @@ .SS Command Definitions -The heart of the \'twander\' configuration process is creating +The heart of the \*(TW configuration process is creating of one or more .B Command Definitions. These definitions are the way user-defined commands are added to a -given instance of \'twander\'. A Command Definition consists of three +given instance of \*(TW. A Command Definition consists of three fields separated by whitespace: .nf @@ -2017,7 +2021,7 @@ the key that will be used to invoke the command from the keyboard. Command Keys are case-sensitive. If "m" is used as a Command Key, "M" will not invoke that command. Command Keys must be unique within a -given Configuration File. If \'twander\' finds multiple Command +given Configuration File. If \*(TW finds multiple Command Definitions assigned to the same Command Key, it will warn you and ignore everything except the first definition. A Command Key can never be "#" which is always understood to be the beginning of a @@ -2035,7 +2039,7 @@ The .B Command String -is any arbitrary string which is what \'twander\' actually tries to +is any arbitrary string which is what \*(TW actually tries to execute when the command is invoked. .SS A Simple Command Definition @@ -2050,7 +2054,7 @@ This command can be invoked pressing the "m" key on the keyboard or selecting the "MyMore" entry from the Command Menu - either directly from the menu or from the Command Menu Pop-Up. No matter how it is -invoked, \'twander\' will then execute the command, "more somefile". +invoked, \*(TW will then execute the command, "more somefile". The problem is that this command as written actually will not give you the result you'd like (...well, on X-Windows - is does work on Win32 @@ -2105,10 +2109,10 @@ .SS Built-In Variables In A Command String It would also be really nice if the command applied to more than just -a single file called "somefile". The whole point of \'twander\' +a single file called "somefile". The whole point of \*(TW is to allow you to use the GUI to select one or more directories and/or files and have your Command Definitions make use of those -selections. \'twander\' uses a set of +selections. \*(TW uses a set of .B Built-In Variables to communicate the current directory and user selections to the any commands you've defined. Built-In Variables are referenced @@ -2133,7 +2137,7 @@ .SS Selection-Related Built-Ins -\'twander\' has a rich set of Built-In Variables for use in your +\*(TW has a rich set of Built-In Variables for use in your Command Definitions. The first group of these is used to convey your current directory and items which you've selected to a Command Definition: @@ -2142,7 +2146,7 @@ .IP \(bu 4 .B [DIR] -[DIR] is replaced with the current directory \'twander\' +[DIR] is replaced with the current directory \*(TW is viewing. .IP \(bu 4 @@ -2186,7 +2190,7 @@ .IP \(bu 4 .B [HASH] -Because \'twander\' always recognizes the "#" as the beginning of a +Because \*(TW always recognizes the "#" as the beginning of a comment, there is no direct way to include this character in a Command String. It is conceivable that some commands (such as \'sed\') need to make use of this character. The [HASH] built-in is provided for @@ -2238,7 +2242,7 @@ .SS Program Memory Built-Ins -As described previously, \'twander\' implements an advanced notion of +As described previously, \*(TW implements an advanced notion of a Clipboard called "Program Memories". There is a corresponding group of Built-In Variables which allows the contents of these memories to be used in a Command Definition: @@ -2264,7 +2268,7 @@ even though it is visible in the GUI. This provides maximum flexibility when defining commands. It is up to the command author to insert the appropriate path separator character where needed. (NOTE: -Earlier releases of \'twander\' +Earlier releases of \*(TW .B did include the trailing path separator and you may have to edit older Configuration Files accordingly. This change was necessary @@ -2288,7 +2292,7 @@ [DIR][WPSEP][SELECTION] .fi -Be aware that, because of \'twander\' quoting rules, such constructs +Be aware that, because of \*(TW quoting rules, such constructs will result in strings like: .nf @@ -2310,7 +2314,7 @@ .IP \(bu 4 User-Defined and Environment Variables are processed -at the time the Configuration File is read by \'twander\'. That +at the time the Configuration File is read by \*(TW. That is, they are handled .B once at load time. @@ -2326,7 +2330,7 @@ default is recommended so that any built-in substitutions of, say, file names with spaces in them, will be properly recognized by your commands. You can suppress the addition of double-quotes by using the --t command line option when starting \'twander\'. +-t command line option when starting \*(TW. .IP \(bu 4 Any of the variable types may appear multiple times in the @@ -2344,46 +2348,46 @@ .SH ADVANCED WIN32 FEATURES -As shipped from the factory, \'twander\' runs pretty much identically +As shipped from the factory, \*(TW runs pretty much identically on various Unix variants (FreeBSD, Linux) and Win32. However, -\'twander\' is written to take advantage of Mark Hammond's -\'win32all\' Python extensions if they are present on the system. +\*(TW is written to take advantage of Mark Hammond's +\*(W3 Python extensions if they are present on the system. These extensions add many Windows-specific features to Python -and allow \'twander\' to provide quite a bit more Windows-centric +and allow \*(TW to provide quite a bit more Windows-centric information about files, directories, and drives. You do .B not -have to install \'win32all\' for \'twander\' to operate properly +have to install \*(W3 for \*(TW to operate properly on your Win32 system. Installing this package just means you'll -get even more \'twander\' features on Win32 than you would otherwise. -If you've installed \'win32all\', you can toggle these features +get even more \*(TW features on Win32 than you would otherwise. +If you've installed \*(W3, you can toggle these features on- and off with the TOGWIN32ALL key described above. -.SS Getting \'win32all\' +.SS Getting \*(W3 -You can get the \'win32all\' extensions one of two ways. If you've +You can get the \*(W3 extensions one of two ways. If you've installed the Active State version of Python for Win32, -(http://www.activestate.com/Products/ActivePython/) \'win32all\' is +(http://www.activestate.com/Products/ActivePython/) \*(W3 is already installed on your system. If you installed the standard Python release for Win32 (http://www.python.org/download/download_windows.html), you must add -\'win32all\' to your installation. You'll find the extensions and +\*(W3 to your installation. You'll find the extensions and painless installation instructions at: http://starship.python.net/crew/mhammond/ -.SS New Features Supported With \'win32all\' +.SS New Features Supported With \*(W3 One important note is in order here: The features enabled by -\'win32all\' are only available on "true" Win32 systems like Windows +\*(W3 are only available on "true" Win32 systems like Windows 2000 and Windows XP. Earlier versions of Windows like Win98 and WinME emulate portions of the Win32 API and do not implement the advanced security features found in the NTFS file system. Therefore, as noted below, some of these features will not work on any of the older 16-bit -Windows operating systems. \'twander\' handles this gracefully -without blowing-up so you can safely have \'win32all\' installed on +Windows operating systems. \*(TW handles this gracefully +without blowing-up so you can safely have \*(W3 installed on one of these older systems to take advantage of the features that do work. -Once you have these extensions installed, \'twander\' will +Once you have these extensions installed, \*(TW will automatically enable three new features otherwise unavailable. .IP \(bu 4 @@ -2395,7 +2399,7 @@ .IP \(bu 4 Instead of showing Unix-style file permissions (which don't mean much -under Win32), systems with \'win32all\' installed will show the +under Win32), systems with \*(W3 installed will show the so-called "file attributes" maintained by the operating system. Each detailed entry in the display will have one or more of the following attributes displayed in what is normally the Unix permissions field: @@ -2411,13 +2415,13 @@ .fi .IP \(bu 4 -A top-level "Drive List View" is enabled if \'win32all\' is installed. +A top-level "Drive List View" is enabled if \*(W3 is installed. This shows you a list of all currently available drives reachable by the system, and information about those drives. For locally attached drives, the drive label is shown. For network-attached drives, the share string is shown. The drive type (CD/DVD, Fixed, Ramdisk, Remote, Removable) is shown as are the free/total space statistics. -As is the case with other \'twander\' displays, these details can be +As is the case with other \*(TW displays, these details can be toggled on- and off via the TOGDETAIL key. You can enter the Drive List View in a number of ways: @@ -2426,7 +2430,7 @@ 1) Select the ".." from the root directory of any drive. 2) Enter the string "\\\\" from the CHANGDIR dialog. 3) Press the DRIVELIST key. (default: Control-k) -4) Start \'twander\' using "\\\\" as the starting directory +4) Start \*(TW using "\\\\" as the starting directory argument, either on the command line or using the Configuration File STARTDIR option. .fi @@ -2450,22 +2454,22 @@ The [DIR] Built-In returns an empty string in this view. .IP \(bu 4 -Normally, as you navigate around a file system, \'twander\' sets its +Normally, as you navigate around a file system, \*(TW sets its own program context to the current directory. This is why you can write Command Definitions using only the file/directory name currently -selected - \'twander\' knows the current directory. When you are in +selected - \*(TW knows the current directory. When you are in Drive List View, the notion of "current directory" has no real -meaning. So, \'twander\' treats the directory from which you entered +meaning. So, \*(TW treats the directory from which you entered Drive List View as the "current directory" while in that view. .IP \(bu 4 -By default, \'twander\' automatically rereads the current view +By default, \*(TW automatically rereads the current view about every 3 seconds. This is fine for a file/directory view but would be annoyingly slow in the Drive List View since it takes a moment or two to get the status of any floppy disk drives attached to the system. Instead of forcing the user to listen to (and wait for) the floppy drive status to be determined -every 3 seconds, \'twander\' +every 3 seconds, \*(TW .B only reads the drive information once when it enters Drive List View. This means if a drive is connected or a floppy is inserted into the system while in Drive List View, this fact will not be automatically @@ -2474,7 +2478,7 @@ .IP \(bu 4 The TOGWIN32ALL key (default: Control-w) is disabled in Drive List -View. Drive List View is only available in \'win32all\' mode and +View. Drive List View is only available in \*(W3 mode and toggling that mode off makes no sense here. .IP \(bu 4 @@ -2490,31 +2494,31 @@ .B do select it as is appropriate. -.SS Disabling \'win32all\' Features +.SS Disabling \*(W3 Features You can toggle these features on-and off using the TOGWIN32ALL key. (default: Control-w) You can also permanently disable them by setting the USEWIN32ALL option to False in the Configuration File. -This allows you to leave \'win32all\' installed on your system +This allows you to leave \*(W3 installed on your system if you need it for other reasons but don't want these features -enabled in \'twander\' +enabled in \*(TW .SH GOTCHAS -There are several tricky corners of \'twander\' which need +There are several tricky corners of \*(TW which need further explanation: .SS Program Starts Very Slowly -\'twander\' attempts to determine the name of the host on which it is +\*(TW attempts to determine the name of the host on which it is running at program startup. This is used in the title bar display. It first looks to see if the environment variable HOSTNAME is set, and -uses that value if it is. If this variable is not set, \'twander\' +uses that value if it is. If this variable is not set, \*(TW does a socket call to see if it can determine the hostname that way. Either of these methods works fine, but the socket call can be very slow if the network is misconfigured or malfunctioning. If -\'twander\' is starting very slowly, try setting HOSTNAME explicitly +\*(TW is starting very slowly, try setting HOSTNAME explicitly in your environment - this will prevent the socket call from ever taking place. A simple way to do this with \'ksh\' or \'bash\' is: @@ -2570,11 +2574,11 @@ .SS Getting Command Results Displayed In A New Window -When you invoke a command via \'twander\' (whether via a command +When you invoke a command via \*(TW (whether via a command definition in the Configuration File or the keyboard shortcut), you generally want it to run in a new window. This turns out to be tricky on Unix-like systems. If the program you are running is GUI-aware, -this should not be a problem. However, if you are using \'twander\' +this should not be a problem. However, if you are using \*(TW to run a command line program or script, you have to take extra care in the formulation of the Command String. In the case of Unix-like systems you have to invoke the command so that it runs in some GUI @@ -2586,15 +2590,15 @@ .fi Sadly, this will not work, at least not the way you expect. -If you started \'twander\' from a terminal session and use +If you started \*(TW from a terminal session and use the command above, it will work, but the results will appear in the invoking terminal window, .B not -in a new window as you might expect. If you started \'twander\' +in a new window as you might expect. If you started \*(TW from a GUI or disconnected it from the initiating terminal with a \'nohup\' ... & invocation, you will get .B no -output. This is not a \'twander\' problem, it is innate to how +output. This is not a \*(TW problem, it is innate to how command line programs run under Unix shell control. To achieve the desired results, you have to create a new GUI window in @@ -2643,10 +2647,10 @@ However, .B which terminal window is used for output can be confusing. If you -start \'twander\' from a terminal session, +start \*(TW from a terminal session, all terminal output will be sent to .B the terminal session you used to invoke the program. -The way to work around this is to start \'twander\' from a Win32 +The way to work around this is to start \*(TW from a Win32 shortcut, using \'pythonw.exe\' rather than \'python.exe\'. Now each time you run a command that needs a terminal session for output, Win32 will automatically create that session for you. @@ -2677,7 +2681,7 @@ This works fine .B so long as the user does not enter a wildcard pattern -in response to the prompt. Why? Recall that \'twander\' +in response to the prompt. Why? Recall that \*(TW quotes all Built-In Variable substitutions by default. If the user enters this at the prompt: @@ -2685,7 +2689,7 @@ /kern* .fi -The command \'twander\' tries to execute is: +The command \*(TW tries to execute is: .nf VSHELL Stuff ... 'ls -l "/kern*" | ... pager stuff @@ -2736,15 +2740,15 @@ Notice our example commands above do not end with "&". These should not be needed on either Unix-like or Win32 -operating systems. When a command is executed, \'twander\' +operating systems. When a command is executed, \*(TW starts a new thread of execution which runs concurrently -with \'twander\' itself. This means you should be able to -continue using \'twander\' while the new command executes. -If not (\'twander\' is locked out while the new command runs - +with \*(TW itself. This means you should be able to +continue using \*(TW while the new command executes. +If not (\*(TW is locked out while the new command runs - so-called "modal" operation), it means your system does not completely or correctly implement threading. In this case, try adding this statement to your Configuration File: -"USETHREADS=False" which will force \'twander\' to +"USETHREADS=False" which will force \*(TW to invoke new commands using conventional (heavyweight) process spawning. @@ -2752,7 +2756,7 @@ It appears that some X Windows implementations (noted on XFree86 / FreeBSD) do not correctly destroy an \'xterm\' window after a command -initiated with -e terminates. This is not a \'twander\' problem. The +initiated with -e terminates. This is not a \*(TW problem. The workaround is to add the following statement to your Configuration File: "USETHREADS=False" This forces conventional (heavyweight) process spawning when a command is run. This mechanism correctly @@ -2773,9 +2777,9 @@ .B really slow response times when you change to a new directory. This occurs when you enter a huge directory with thousands of file or subdirectory -entries. \'twander\' has to to compute the detail information for +entries. \*(TW has to to compute the detail information for each of these entries and this can take a lot of time. On a fast -machine with modern hard drives and controllers, \'twander\' is able +machine with modern hard drives and controllers, \*(TW is able to process several thousand entries in just a second or two. However, a number of factors can significantly slow down this process: @@ -2785,11 +2789,11 @@ right away. The program will appear to hang. There are two possibilities here. Either disable autorefreshing (via the -r command line option or the AUTOREFRESH Configuration File option), or set the -REFRESHINT value to some high number so that \'twander\' has plenty +REFRESHINT value to some high number so that \*(TW has plenty of time to process a directory before the next refresh occurs. .IP \(bu 4 -Slow disk drives. You can really watch \'twander\' grind if you +Slow disk drives. You can really watch \*(TW grind if you change to a large directory on a CDROM, for instance. There is no good solution here. These drives are inherently slower than hard drives, and you just have to wait. Make sure you lengthen your @@ -2797,22 +2801,22 @@ .IP \(bu 4 By far the worst culprit here, though, is when running Win32 -with \'win32all\' options enabled. It takes a lot more work +with \*(W3 options enabled. It takes a lot more work to get win32all-style information about each directory entry, than the default Unix-style information. Simply turning -off \'win32all\' features alone can speed up directory processing +off \*(W3 features alone can speed up directory processing by a factor as high as 4X. .P When you combine these factors, it is possible to get really long processing times. One test situation we observed was reading a directory with over 4000 entries on a Win32 CDROM. -With \'win32all\' processing enabled this took over a minute. +With \*(W3 processing enabled this took over a minute. By disabling these features, the time came down to under 30 seconds. .SS Your Configuration File Does Not Produce The Desired Results -It's easy to fall into the trap of treating the \'twander\' +It's easy to fall into the trap of treating the \*(TW configuration capabilities as a real "programming language". It is not, it is a fairly simple macro language that does very little more than string substitutions. You should thus kee these @@ -2866,17 +2870,17 @@ # in a Command Definition ##### - .if [EDT] == /usr/local/bin/emacs +\&.if [EDT] == /usr/local/bin/emacs ... - .endif +\&.endif # Note, however, that *this* would work because # Environment Variables are permitted in conditionals ... - .if [$EDITOR] == /usr/local/bin/emacs +\&.if [$EDITOR] == /usr/local/bin/emacs ... - .endif +\&.endif .fi @@ -2899,11 +2903,11 @@ appropriate release of Tkinter. This is the case, for example, with FreeBSD. -You must install the \'win32all\' extensions if you want to use +You must install the \*(W3 extensions if you want to use the advanced Win32 features. You'll find the latest version, and occasionally, Release Candidates -of the next version of \'twander\' at: +of the next version of \*(TW at: .nf http://www.tundraware.com/Software/twander @@ -2915,7 +2919,7 @@ .SH BUGS AND MISFEATURES -As of this release, a number of problems relating to \'twander\' +As of this release, a number of problems relating to \*(TW use have been noted: .IP \(bu 4 @@ -2923,7 +2927,7 @@ of its various entries for Program Options, Key Bindings, Directory Shortcuts, Variable Definitions, and Command Definitions. It is entirely possible to edit something into this file that makes no sense -at all and causes \'twander\' to misbehave. +at all and causes \*(TW to misbehave. .IP \(bu 4 There appears to be a Tkinter/Tk bug on Unix which sometimes inhibits @@ -2932,11 +2936,11 @@ Tkinter/Tk/X-Windows. .IP \(bu 4 -Some \'win32all\' features do not work correctly or at all on +Some \*(W3 features do not work correctly or at all on older Windows OSs. For example, the free/total space available in the Drive List View has been noted to display incorrect values on Win98. Similarly, the owner and group names are displayed as "Unavailable" on -pre-NTFS file systems. These are OS limitations which \'twander\' +pre-NTFS file systems. These are OS limitations which \*(TW handles gracefully. .IP \(bu 4 @@ -2956,9 +2960,9 @@ it works there and any issues you discover. -.SH INSTALLING \'twander\' +.SH INSTALLING \*(TW -Installation of \'twander\' is fairly simple and takes only a few +Installation of \*(TW is fairly simple and takes only a few moments. The most important thing before installing the program is to make sure you have Python 2.2 (or later) with Tkinter support installed on your system. @@ -2971,7 +2975,7 @@ .SS Installing Using The FreeBSD Port -If you've installed \'twander\' using the FreeBSD port, all you have +If you've installed \*(TW using the FreeBSD port, all you have to do is copy the example Configuration File, ".twander" found in /usr/local/share/doc/twander to your home directory and edit it to taste. @@ -2992,8 +2996,8 @@ .B Red Hat Linux Users Please Note: RH Linux (and possibly other Linux systems) installs two versions of Python. Version 1.52 is called \'python\', and Version 2.2 is called -\'python2\'. \'twander\' requires the latter and will not run on the -former. As shipped, \'twander\' invokes Python with the Unix shell +\'python2\'. \*(TW requires the latter and will not run on the +former. As shipped, \*(TW invokes Python with the Unix shell "#!" mechanism using the name \'python\' - which in this case is the wrong version. You can work around this problem one of several ways: @@ -3003,7 +3007,7 @@ .IP \(bu 4 Write an alias or shell script which explicity starts -\'twander\' with the correct version of Python: +\*(TW with the correct version of Python: .nf #!/bin/sh @@ -3011,14 +3015,14 @@ .fi .IP \(bu 4 -Change the first line of the \'twander\' code to refer +Change the first line of the \*(TW code to refer to \'python2\' instead of \'python\'. .P Red Hat users who have upgraded from earlier Linux versions should also note that you may have files in your home directories owned by owners and groups which are no longer defined in the system! -\'twander\' shows the owner and group fields for such files as numbers +\*(TW shows the owner and group fields for such files as numbers rather than names. As best as we can determine, this is caused when an RH installation is updated from an older version. @@ -3037,7 +3041,7 @@ is especially the case for older Win32 operating systems like Win98. For this reason, it is recommended that you rename the ".twander" default Configuration File provided in the program distribution to -something else like "twander.conf" and use the \'twander\' -c command +something else like "twander.conf" and use the \*(TW -c command line option to point to this Configuration File. @@ -3047,7 +3051,7 @@ directory - Well, they do, but it is called "USERPROFILE" not "HOME". So, you can either create a new user-specific environment variable called HOME yourself (which points to your desired home directory) or -you can invoke \'twander\' with the -c argument to explictly declare +you can invoke \*(TW with the -c argument to explictly declare where it can find its Configuration File. You can run the program several ways on Win32 systems: @@ -3074,15 +3078,15 @@ .IP \(bu 4 Use Windows Explorer (or better still, an already running instance -of \'twander\'!) to navigate to the directory where "twander.py" +of \*(TW!) to navigate to the directory where "twander.py" is located. Double-click on the file. If Python is properly installed, there should be an association for ".py" file types -and \'twander\' should start automatically. +and \*(TW should start automatically. -.SH GETTING HELP: THE \'twander\' MAILING LIST +.SH GETTING HELP: THE \*(TW MAILING LIST -TundraWare Inc. maintains an email list for \'twander\' +TundraWare Inc. maintains an email list for \*(TW users to get help and exchange ideas. To subscribe, send mail to: @@ -3123,7 +3127,7 @@ You Get" - Each program has a predefined set of commands and the user cannot easily extend these with their own, new commands. -\'twander\' is another approach to the filesystem navigation problem +\*(TW is another approach to the filesystem navigation problem which embraces the best of both the GUI-based approach and the text-based approach. It also provides a rich mechanism whereby each user can easily define their own command set and thereby customize the @@ -3141,7 +3145,7 @@ .TP 2) -\'twander\' also supports a number of +\*(TW also supports a number of .B navigation shortcuts. It provides single control-key access to changing directories, moving to the previous directory, moving up one directory level, moving to @@ -3159,7 +3163,7 @@ This Command Definition is done in an external Configuration File using a simple but powerful command macro language. This means that that the command set of the program can easily be changed or expanded -without having to release a new version of \'twander\' every time. +without having to release a new version of \*(TW every time. Better still, every different user can have their own command set defined in a way that suits their style of working. Best of all, commands can be invoked either graphically (with a mouse click) or via @@ -3167,7 +3171,7 @@ .TP 4) -Because \'twander\' is written in Python using Tkinter, the same +Because \*(TW is written in Python using Tkinter, the same program runs essentially identically on many Unix-like and Win32 systems. The only thing that may need to be changed across these various platforms are the Command Definitions in the configuration @@ -3175,7 +3179,7 @@ defined) across all the different systems you use. .P -The consequence of all this is that \'twander\' is an extremely +The consequence of all this is that \*(TW is an extremely powerful and highly customizable filesystem navigator. Once learned, both navigation and command execution are lightning-fast (or at least, as fast as your machine can go ;) while minimizing @@ -3183,9 +3187,9 @@ .SH COPYRIGHT AND LICENSING -\'twander\' is Copyright(c) 2002-2003 TundraWare Inc. For terms of +\*(TW is Copyright(c) \*(CP TundraWare Inc. For terms of use, see the twander-license.txt file in the program distribution. If -you install \'twander\' on a FreeBSD system using the 'ports' +you install \*(TW on a FreeBSD system using the 'ports' mechanism, you will also find this file in /usr/local/share/doc/twander.