Tweak language.

This commit is contained in:
Nicholas Marriott 2009-02-08 19:06:16 +00:00
parent 44cc9c4459
commit 8c7c4423e1

18
FAQ
View File

@ -166,17 +166,17 @@ exit (elinks, for some strange reason, sets it to the value of TERM):
echo -ne \\033]0\;\\007; echo -ne \\033]0\;\\007;
} }
* What's the proper way to escape characters with #(command)? * What is the proper way to escape characters with #(command)?
When using the character pair #(command), the command will be parsed twice. When using the #(command) construction to include the output from a command in
First when it's read by the configuration file, or the command-prompt parser, the status line, the command will be parsed twice. First, when it's read by the
and another right before the command is passed to the shell by popen(3). As an configuration file or the command-prompt parser, and second when the status
example, to echo the string (test) to the status line, one could use single, line is being drawn and the command is passed to the shell. For example, to
or double-quotes (the meaning is the same as if in the shell): echo the string "(test)" to the status line, either single or double quotes
could be used:
set -g status-right "#(echo \\\\(test\\\\))" set -g status-right "#(echo \\\\(test\\\\))"
set -g status-right '#(echo \\\(test\\\))' set -g status-right '#(echo \\\(test\\\))'
With the double-quotes, the string when is first parsed will be set to In both cases, the status-right option will be set to the string "#(echo
#(echo \\(test\\)), and then again parsed as echo \(test\) before passing the \\(test\\))" and the command executed will be "echo \(test\)".
command to sh -c.