Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for scratchpad_state field present in the output of the command i3-msg -t get_tree #4465

Closed
slashfoo opened this issue Jul 28, 2021 · 0 comments · Fixed by #4466
Assignees

Comments

@slashfoo
Copy link

I'm submitting a…

[ ] Bug
[ ] Feature Request
[X] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

Browsing the TREE reply of the IPC interface (interprocess communication) there is no mention of the field scratchpad_state, this field is present in the output of running i3-msg -t get_tree.

Desired Behavior

The document should mention the meaning of the field scratchpad_state, it's possible values, and perhaps the conditions that cause a change in these values.

Impact

[ ] This feature requires new configuration and/or commands

Environment

Output of i3 --moreversion 2>&-:

Binary i3 version:  4.19.1-non-git © 2009 Michael Stapelberg and contributors
Running i3 version: 4.19.1-non-git (pid 2291)
Loaded i3 config: /home/jamielalmeida/.config/i3/config (Last modified: Mon 19 Jul 2021 07:29:28 PM PDT, 141549 seconds ago)

The i3 binary you just called: /usr/bin/i3
The i3 binary you are running: i3
- Linux Distribution & Version: Debian GNU/Linux 11
- Are you using a compositor (e.g., xcompmgr or compton): picom
stapelberg added a commit to stapelberg/i3 that referenced this issue Jul 30, 2021
@stapelberg stapelberg self-assigned this Jul 30, 2021
stapelberg added a commit that referenced this issue Jul 30, 2021
LinoBigatti pushed a commit to LinoBigatti/i3-rounded that referenced this issue Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants