userguide: Remove mention of config directives with 'command equivalents'

See #3657
This commit is contained in:
Orestis Floros 2019-10-17 12:55:16 +03:00
parent 9138bb37f1
commit 72765bbb94
No known key found for this signature in database
GPG Key ID: A09DBD7D3222C1C3
1 changed files with 2 additions and 5 deletions

View File

@ -680,8 +680,8 @@ for_window [class="urxvt"] border pixel 1
for_window [title="x200: ~/work"] floating enable for_window [title="x200: ~/work"] floating enable
------------------------------------------------ ------------------------------------------------
The valid criteria are the same as those for commands, see <<command_criteria>>. Only config The valid criteria are the same as those for commands, see <<command_criteria>>. Only
directives with a command equivalent can be executed at runtime, see <<list_of_commands>>. commands can be executed at runtime, not config directives, see <<list_of_commands>>.
[[no_focus]] [[no_focus]]
=== Don't focus window upon opening === Don't focus window upon opening
@ -1901,9 +1901,6 @@ The criteria +class+, +instance+, +role+, +title+, +workspace+ and +mark+ are
actually regular expressions (PCRE). See +pcresyntax(3)+ or +perldoc perlre+ for actually regular expressions (PCRE). See +pcresyntax(3)+ or +perldoc perlre+ for
information on how to use them. information on how to use them.
Note that config directives listed under <<configuring>> cannot be changed at runtime
unless they happen to have a command equivalent.
[[exec]] [[exec]]
=== Executing applications (exec) === Executing applications (exec)