aboutsummaryrefslogtreecommitdiffstats
path: root/sway/sway.5.scd
Commit message (Collapse)AuthorAge
* Change workspace_layout to match i3 behaviorLibravatar Ronan Pigott2020-12-20
| | | | | | | In i3, the workspace_layout command does not affect the workspace layout. Instead, new workspace level containers are wrapped in the desired layout and the workspace layout always defaults to the output orientation.
* document force_display_urgency_hintLibravatar Rex Hackbro2020-08-03
|
* fix typosLibravatar Rex Hackbro2020-08-03
|
* Fix typos in man page.Libravatar Antonin Décimo2020-07-21
|
* added ppt unit to move position commandLibravatar Nils Schulte2020-07-21
|
* sway.5: add missing underscoreLibravatar Ronan Pigott2020-07-19
|
* Reload command now matches i3's implementationLibravatar Geoffrey Casper2020-07-07
|
* sway.5: make formatting more consistentLibravatar Martin Michlmayr2020-05-20
|
* commands: Add per-view shortcuts_inhibitor commandLibravatar Michael Weiser2020-05-13
| | | | | | | | | | | | | | | | | | | | | Add a separate per-view shortcuts_inhibitor command that can be used with criteria to override the per-seat defaults. This allows to e.g. disable shortcuts inhibiting globally but enable it for specific, known-good virtualization and remote desktop software or, alternatively, to blacklist that one slightly broken piece of software that just doesn't seem to get it right but insists on trying. Add a flag to sway_view and handling logic in the input manager that respects that flag if configured but falls back to per-seat config otherwise. Add the actual command but with just enable and disable subcommands since there's no value in duplicating the per-seat activate/deactivate/toggle logic here. Split the inhibitor retrieval helper in two so we can use the backend half in the command to retrieve inhibitors for a specific surface and not just the currently focused one. Extend the manual page with documentation of the command and references to its per-seat sibling and usefulness with criteria. Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
* Simplify repaint scheduling documentationLibravatar Kenny Levinsen2020-05-11
| | | | | | | The current documentation for repaint scheduling is very technical and somewhat confusing. Closes: https://github.com/swaywm/sway/issues/4769
* man: add note about sway-input and sway-output pagesLibravatar Simon Ser2020-04-27
|
* scdoc: unbindcode --input-device, not input-deviceLibravatar Ihor Kalnytskyi2020-04-20
| | | | | Apparently, there's a typo in Sway's man page where `input-device` of `unbindcode` command has no dashes.
* Reference wev instead of xevLibravatar Tobi Fuhrimann2020-04-02
|
* add --no-repeat option for bindingsLibravatar Linus Heckemann2020-03-30
| | | | | | | | | This allows e.g. triggering one command while a key is held, then triggering another to undo the change performed by it afterwards. One use case for this is triggering push-to-talk functionality for VoIP tools without granting them full access to all input events. Fixes #3151
* Change focus_on_window_activation default to urgentLibravatar Simon Ser2020-03-29
| | | | | | | | | | Before the default was "smart". This means a visible app could steal focus whenever it wanted to. This can be an issue since having focus allows for e.g. clipboard access. This commit changes the default to "urgent" instead. Closes: https://github.com/swaywm/sway/issues/5139
* sway.5: fix missing background scaling mode in a block exampleLibravatar rinpatch2020-03-28
|
* input: Add support for keyboard shortcuts inhibitLibravatar Michael Weiser2020-03-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | Adding support for the keyboard shortcuts inhibit protocol allows remote desktop and virtualisation software to receive all keyboard input in order to pass it through to their clients so users can fully interact the their remote/virtual session. The software usually provides its own key combination to release its "grab" to all keyboard input. The inhibitor can be deactivated by the user by removing focus from the surface using another input device such as the pointer. Use support for the procotol in wlroots to add support to sway. Extend the input manager with handlers for inhibitor creation and destruction and appropriate bookkeeping. Attach the inhibitors to the seats they apply to to avoid having to search the list of all currently existing inhibitors on every keystroke and passing the inhibitor manager around. Add a helper function to retrieve the inhibitor applying to the currently focused surface of a seat, if one exists. Extend bindsym with a flag for bindings that should be processed even if an inhibitor is active. Conversely this disables all normal shortcuts if an inhibitor is found for the currently focused surface in keyboard::handle_key_event() since they don't have that flag set. Use above helper function to determine if an inhibitor exists for the surface that would eventually receive input. Signed-off-by: Michael Weiser <michael.weiser@gmx.de>
* sway.5: correct description of workspace [number]Libravatar Brian Ashworth2020-02-29
| | | | | | | | This correct the description of the commmand: workspace [--no-auto-back-and-forth] [number] <[num:]name> Previously, the number and num pieces were being confused. This also documents the behavior of the --no-auto-back-and-forth flag.
* Introduce pid criteria tokenLibravatar Ryan Dwyer2020-02-27
| | | | | | | | | | This can be used as a workaround to flag terminal windows as urgent when commands are completed, until urgency is introduced in the Wayland protocol. Configure your shell to run `swaymsg "[pid=$PPID] urgent enable"` when commands are completed, and use a terminal which uses one process per window.
* Add documentation for floating_modifierLibravatar Alex Maese2020-01-20
|
* sway.5: Document missing bindsym flags for unbindsymLibravatar Ronan Pigott2020-01-16
| | | | sway.5: Remove indents within long command descriptions
* cmd_client_*: support optional args for i3 compatLibravatar Brian Ashworth2019-12-29
| | | | | | For i3 compatibility, allow the indicator and child_border colors values to be optional. The indicator will fallback to sane defaults and child_border will fallback to the background color for the class.
* view: add max_render_timeLibravatar Ivan Molodetskikh2019-11-17
|
* smart_borders: separate smartness from edge typesLibravatar Ronan Pigott2019-11-04
|
* focus: support focus prev|next [sibling]Libravatar Ronan Pigott2019-10-27
|
* focus: support focus_wrapping workspaceLibravatar lbonn2019-10-17
| | | | Following i3 support: https://github.com/i3/i3/pull/3407
* sway(5): move workspace_layout to config onlyLibravatar Rouven Czerwinski2019-10-16
| | | | | According to the source files, workspace_layout is a configuration only command, move it to the correct section within the man page.
* sway(5): Highlight valid values in the description of tiling_dragLibravatar Wieland Hoffmann2019-10-09
|
* sway(5): Add a missing verbLibravatar Wieland Hoffmann2019-10-09
|
* sway.5: clarify that a marks are unqiueLibravatar Brian Ashworth2019-09-05
| | | | | This just clarifies that a mark can only be set for a single window since they are used as unique identifiers
* swaybar: complete barconfig_update event handlingLibravatar Brian Ashworth2019-09-04
| | | | | | | | This adds complete support for the barconfig_update ipc event. This also changes the bar command and subcommand handlers to correctly emit the event. This makes it so all bar subcommands other than id and swaybar_command are dynamically changeable at runtime. sway-bar.5 has been updated accordingly
* Fix formatting for title_format in man 5 swayLibravatar Michael Aquilina2019-08-25
| | | | | Use explicit linebreaks to make scdoc use a separate line for each entry listed
* sway.5: remove mention of floating_scrollLibravatar Brian Ashworth2019-08-22
| | | | | | | It looks like floating_scroll was still in the sway(5) man page as a remnant of the 0.x era. This just removes it from the man page since it is no longer a valid command. Mouse bindings with Button4-7 can be used instead
* cmd_xwayland: add force for immediate launchLibravatar Brian Ashworth2019-08-20
| | | | | | | This just adds a force option to cmd_xwayland that allows for xwayland to be immediately launched instead of lazily launched. This is useful for slower machines so it can be part of the startup time instead of when the user is actively trying to use it
* sway{,-bar}.5: add link to pango font descriptionLibravatar Brian Ashworth2019-08-16
| | | | | | This just specifies that both cmd_font and bar_cmd_font should be specified using the pango font description and adds a link to the pango documentation regarding the font description
* sway.5: explain how to enable pango markup in fontLibravatar Brian Ashworth2019-08-07
| | | | | This clarifies the syntax to use for the font command to enable pango markup support.
* cmd_opacity: add relative opacity changesLibravatar Jeff Peeler2019-08-05
| | | | | | | | | | | | | | | | | | | This enhances the opacity command to support relative assignment as well as the currently implemented absolute assignment. The syntax is copied from the same format that gaps uses for relative and absolute setting. An example usage in a sway config looks like: // relative change (this feature) bindsym button4 opacity plus .1 bindsym button5 opacity minus .1 // absolute change (this feature) bindsym button4 opacity set 1 bindsym button5 opacity set .3 // old way, still supported bindsym button4 opacity 1 bindsym button5 opacity .3
* bindsym/code: add group supportLibravatar Brian Ashworth2019-08-01
| | | | | | | | | | | This adds support for specifying a binding for a specific group. Any binding without a group listed will be available in all groups. The priority for matching bindings is as follows: input device, group, and locked state. For full compatibility with i3, this also adds Mode_switch as an alias for Group2. Since i3 only supports this for backwards compatibility with older versions of i3, it is implemented here, but not documented.
* Fix typo in sway(5) manpageLibravatar Paul Ouellette2019-07-31
|
* Add missing description for focus_on_window_activation command in docs.Libravatar rpigott2019-07-17
|
* cmd_bindswitch: add option to execute on reloadLibravatar Brian Ashworth2019-07-09
| | | | | | | This adds a --reload flag to cmd_bindswitch that allows for the binding to be executed on reload. One possible use case for this is to allow users to disable outputs when the lid closes and enable them when the lid opens without having to open and re-close the lid after a reload.
* Add missing underscore in bindswitch documentationLibravatar Robert Sacks2019-06-14
| | | | | The missing underscore after "toggle" causes the underline to continue for a whole sentence.
* criteria: reset on semicolon separationLibravatar Brian Ashworth2019-06-05
| | | | | | This matches i3's behavior of only retaining criteria across comma separated commands. When separating commands with a semicolon, the criteria is reset and allows for new criteria to be set, if desired.
* bindings: allow unlocked and locked bindingsLibravatar Brian Ashworth2019-05-30
| | | | | | | | | | | | | | | | This changes the behavior of bindings to make the `BINDING_LOCKED` flag conflicting, which will allow for both unlocked and locked bindings. If there are two matching bindings and one has `--locked` and the other does not, the one with `--locked` will be preferred when locked and the one without will be preferred when unlocked. If there are two matching bindings and one has both a matching `--input-device=<input>` and `--locked` and the other has neither, the former will be preferred for both unlocked and locked. This also refactors `get_active_binding` in `sway/input/keyboard.c` to make it easier to read.
* Add infos to help using for_window to man 5Libravatar Nomeji2019-05-14
|
* sway.5.scd: clarify workspace config commandsLibravatar Brian Ashworth2019-04-30
| | | | | | | This clarifies that `workspace <name> output <outputs...>` and `workspace <name> gaps ...` do not operate on existing workspaces. Additionally, alternate commands/solutions that operate on existing workspaces are listed.
* cmd_move: add support for output currentLibravatar Brian Ashworth2019-04-30
| | | | | | | | | This adds support for the following commands for i3 compatibility: - `move [window|container] [to] output current` - `move workspace to [output] current` - `move workspace [to] output current` The above commands are only useful when used with criteria.
* bindsym: update the man page to include --to-codeLibravatar Konstantin Pospelov2019-04-26
|
* cmd_move: allow for all i3 syntax optionsLibravatar Brian Ashworth2019-04-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | This modifies cmd_move to allow for the syntax options allowed by i3. The following syntaxes are supported: - `move left|right|up|down [<amount> [px]]` - `move [--no-auto-back-and-forth] [window|container] [to] workspace <name>|next|prev|next_on_output|prev_on_output|current|number <num>` - `move [window|container] [to] output <name/id>|left|right|up|down` - `move [window|container] [to] mark <mark>` - `move workspace to [output] <name/id>|left|right|up|down` - `move [window|container] [to] [absolute] position <x> [px] <y> [px]` - `move [window|container] [to] [absolute] position center` - `move [window|container] [to] position mouse|cursor|pointer` This also allows retains the following syntax option that is not supported by i3, but is supported in sway 1.0: - `move workspace [to] output <name/id>|left|right|up|down` The changes are: - `window` and `container` are now optional - `output` is now optional for `move workspace` when `to` is given There is also stricter command checking now. If `absolute` or `--no-auto-back-and-forth` are given for commands that do not support them, it will be treated as invalid syntax instead of being silently ignored.
* Add unbindswitch commandLibravatar Alex Maese2019-04-17
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-27 15:22:08 +0000