mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-12-26 12:27:52 +00:00
remove TEXT in config_settings.xml and variables.xml
This commit is contained in:
parent
25c1b1d919
commit
7310bff162
@ -1,16 +1,4 @@
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>
|
||||
<option>TEXT</option>
|
||||
</command>
|
||||
</term>
|
||||
<listitem>After this begins text to be formatted on screen.
|
||||
Backslash (\) escapes newlines in the text section. This
|
||||
can be useful for cleaning up config files where conky is
|
||||
used to pipe input to dzen2.
|
||||
<para /></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
<command>
|
||||
@ -78,7 +66,7 @@
|
||||
<option>colorN</option>
|
||||
</command>
|
||||
</term>
|
||||
<listitem>Predefine a color for use inside TEXT segments.
|
||||
<listitem>Predefine a color for use inside conky.text segments.
|
||||
Substitute N by a digit between 0 and 9, inclusively. When
|
||||
specifying the color value in hex, omit the leading hash
|
||||
(#).
|
||||
@ -508,8 +496,8 @@
|
||||
</command>
|
||||
<option>bytes</option>
|
||||
</term>
|
||||
<listitem>Maximum size of user text buffer, i.e. layout
|
||||
below TEXT line in config file (default is 16384 bytes)
|
||||
<listitem>Maximum size of user text buffer, i.e. text inside
|
||||
conky.text section in config file (default is 16384 bytes)
|
||||
<para /></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
@ -909,10 +897,10 @@
|
||||
<option>templateN</option>
|
||||
</command>
|
||||
</term>
|
||||
<listitem>Define a template for later use inside TEXT
|
||||
<listitem>Define a template for later use inside conky.text
|
||||
segments. Substitute N by a digit between 0 and 9,
|
||||
inclusively. The value of the variable is being inserted
|
||||
into the stuff below TEXT at the corresponding position,
|
||||
into the stuff inside conky.text at the corresponding position,
|
||||
but before some substitutions are applied:
|
||||
<simplelist>
|
||||
<member>'\n' -> newline</member>
|
||||
|
@ -944,7 +944,7 @@
|
||||
<option>string</option>
|
||||
</term>
|
||||
<listitem>Evaluates given string according to the rules of
|
||||
TEXT interpretation, i.e. parsing any contained text object
|
||||
conky.text interpretation, i.e. parsing any contained text object
|
||||
specifications into their output, any occuring '$$' into a
|
||||
single '$' and so on. The output is then being parsed
|
||||
again.
|
||||
@ -1766,7 +1766,7 @@
|
||||
pixels. Conky does not make any attempt to adjust the
|
||||
position (or any other formatting) of images, they are just
|
||||
rendered as per the arguments passed. The only reason
|
||||
$image is part of the TEXT section, is to allow for runtime
|
||||
$image is part of the conky.text section, is to allow for runtime
|
||||
modifications, through $execp $lua_parse, or some other
|
||||
method.
|
||||
<para /></listitem>
|
||||
@ -1949,7 +1949,7 @@
|
||||
</term>
|
||||
<listitem>Executes a Lua function with given parameters as
|
||||
per $lua, then parses and prints the result value as per
|
||||
the syntax for Conky's TEXT section. See also 'lua_load' on
|
||||
the syntax for the conky.text section. See also 'lua_load' on
|
||||
how to load scripts. Conky puts 'conky_' in front of
|
||||
function_name to prevent accidental calls to the wrong
|
||||
function unless you put you place 'conky_' in front of it
|
||||
|
Loading…
Reference in New Issue
Block a user