diff --git a/twander.1 b/twander.1 index a7c7d9e..24ac0a2 100644 --- a/twander.1 +++ b/twander.1 @@ -1872,6 +1872,19 @@ .fi .ft \" revert + +.TP +.B DEFAULTSEP [String] (==>) + +This is the string that separates the prompting text and the default +response in \fC{PROMPT: ...}\fP and \fC{YESNO: ...}\fP Built-In +Variables. You may change this to any string you like, though doing +so is not recommended. Changing DEFAULTSEP will require you to edit +any configuration files that use these Built-Ins with default +responses. In no case should the delimiter string include any of the +characters, \fC[ ]{ }\fP since these are used as delimiters in the +\fCtwander\fP configuration language. + .TP .B FCOLOR [String] (green) @@ -2268,6 +2281,14 @@ Initial horizontal size of the \fCtwander\fP window in pixels. +.TP +.B WILDNOCASE [Boolean] (True On Win32 / False Elsewhere) + +Set's whether or not case is significant in wildcard filtering and +selection. If True, case is ignored, if False, case is significant in +these wildcard operations. + + .P A few general notes about Program Options are worth mentioning here: @@ -2904,7 +2925,7 @@ .ft C \" courier .nf - a mycommand echo "[`-ls`]" + a mycommand echo "[`-ls`]" # We need the double-quotes to make echo work right .fi .ft \" revert @@ -3065,6 +3086,25 @@ .fi .ft \" revert + +.SS Execution Variables In A Command String + +We can further extend the power of Command Definitions by using an +Execution Variable to define part of the command. Suppose we want a +command that will let us examine all the text files in the current +directory: + +.ft C \" courier +.nf + # Our command using User-Defined, Environment, and + # Execution Variables + + XTERM = xterm -l -e + m MyMore [XTERM] [$PAGER] [`-ls *.txt`] +.fi +.ft \" revert + + .SS Built-In Variables In A Command String It would also be really nice if the command applied to more than just @@ -3243,6 +3283,42 @@ .ft \" revert +.SS Using Variable References Within Prompting Built-Ins + +You may have guessed that there is something special about the +Prompting Built-In Variables. After all, they use a different +delimiter pair than all other variables in the \fCtwander\fP +configuration language. That's because you can include references to +other variables within a Prompting Built-In like this: + +.ft C \" courier +.nf + PromptYN = Are You Sure You Want To Do This? + DefaultYN = No + + a mycommand {YESNO:[PromptYN]==>[DefaultYN]} SomeDangerousCommand +.fi +.ft \" revert + + +A more sophisticated use of this would be when creating a "rename" command. +You often want to rename a file by changing only a few of its characters, +not the whole file name. Instead of forcing the user to type the whole name +in over again, why not just do this: + +.ft C \" courier +.nf + Prompt = New File Name? + r rename mv [SELECTION] {PROMPT:[Prompt]==>[SELECTION]} +.fi +.ft \" revert + +Now when the user runs the command, the default string will be the +name of the file to be renamed. They can around inside the +dialog box created by \fC{PROMPT: ...}\fP at runtime to edit +the existing file name to taste. + + .SS Program Memory Built-Ins As described previously, \fCtwander\fP implements an advanced notion of @@ -3322,16 +3398,19 @@ .IP \(bu 4 -User-Defined and Environment Variables are processed -at the time the Configuration File is read by \fCtwander\fP. That -is, they are handled -.B once -at load time. +All User-Defined, Environment, and Execution Variables are processed +each time a command is +.B run. +This is especially important for Execution Variables. The +variable will be "executed" each time the Command Definition +in which it is referenced is run. + .IP \(bu 4 -By contrast, Built-In Variables are resolved +Similarly, Built-In Variables are resolved .B on each command invocation, -i.e - at command runtime. +i.e - at command runtime. The Built-Ins will always reflect +the current set of files selected in the user interface. .IP \(bu 4 The results of all built-ins (except HASH) are put inside @@ -4580,4 +4659,4 @@ .ft \" revert .SH DOCUMENT REVISION INFORMATION -$Id: twander.1,v 1.120 2005/02/04 10:19:14 tundra Exp $ \ No newline at end of file +$Id: twander.1,v 1.121 2005/02/04 11:04:29 tundra Exp $ \ No newline at end of file