docs/userguide: document the --no-startup-id flag for exec directives in the config
This commit is contained in:
parent
15f36cdc91
commit
73d4737e42
|
@ -541,16 +541,21 @@ keyword. These commands will be run in order.
|
|||
|
||||
*Syntax*:
|
||||
-------------------
|
||||
exec command
|
||||
exec_always command
|
||||
exec [--no-startup-id] command
|
||||
exec_always [--no-startup-id] command
|
||||
-------------------
|
||||
|
||||
*Examples*:
|
||||
--------------------------------
|
||||
exec chromium
|
||||
exec_always ~/my_script.sh
|
||||
|
||||
# Execute the terminal emulator urxvt, which is not yet startup-notification aware.
|
||||
exec --no-startup-id urxvt
|
||||
--------------------------------
|
||||
|
||||
The flag --no-startup-id is explained in <<exec>>.
|
||||
|
||||
[[workspace_screen]]
|
||||
|
||||
=== Automatically putting workspaces on specific screens
|
||||
|
@ -1034,6 +1039,8 @@ The criteria +class+, +instance+, +role+, +title+ and +mark+ are actually
|
|||
regular expressions (PCRE). See +pcresyntax(3)+ or +perldoc perlre+ for
|
||||
information on how to use them.
|
||||
|
||||
[[exec]]
|
||||
|
||||
=== Executing applications (exec)
|
||||
|
||||
What good is a window manager if you can’t actually start any applications?
|
||||
|
|
Loading…
Reference in New Issue