20
849
Fork
You've already forked fuzzel
83

wish: documen expected output format of output configuration #185

Closed
opened 2022年11月11日 16:31:32 +01:00 by markstos · 1 comment
Collaborator
Copy link

The expected format of the output configuration values is not currently documented.

From looking at how the completions work, a correct format is like DP-1 or eDP-2.

It would be helpful to document if these are the only the accepted formats, since these values sometimes change.

Sway supports targetting a specific brand/model/serial number with values like " "Some Company ABC123 0x00000000". From a test, it appears Fuzzel doesn't support that style if output ID, but maybe there's another format I'm missing.

This relates some to #130, because if people are going to be able to position Fuzzel, they will also likely want to target the specific monitor it appears on.

The expected format of the `output` configuration values is not currently documented. From looking at how the completions work, a correct format is like `DP-1` or `eDP-2`. It would be helpful to document if these are the only the accepted formats, since these values sometimes change. Sway supports targetting a specific brand/model/serial number with values like " "Some Company ABC123 0x00000000". From a test, it appears Fuzzel doesn't support that style if output ID, but maybe there's another format I'm missing. This relates some to #130, because if people are going to be able to position Fuzzel, they will also likely want to target the specific monitor it appears on.
markstos changed title from (削除) wish: documented expected output format of output configuration (削除ここまで) to wish: documen expected output format of output configuration 2022年11月11日 16:33:51 +01:00
Owner
Copy link

There's no "format", it's just the identifier (as set by the compositor). But I guess we could make this more clear. We could also mention e.g. wlr-randr and what to look for in its output.

I'm open for other suggestions.

There's no "format", it's just the identifier (as set by the compositor). But I guess we could make this more clear. We could also mention e.g. `wlr-randr` and what to look for in its output. I'm open for other suggestions.
Sign in to join this conversation.
No Branch/Tag specified
master
gnome-support
releases/1.14
issue-319-window-switching
issue-561-nord-theme-only
resvg-filtering-take-2
resvg-filtering
releases/1.13
rehanzo-dont-ignore-execute-648
keybinds-overwrite
issue-561-refresh-theme
ci-automated-testing
reenable-legacy-icons
releases/1.12
test-coverage-for-fzf-caching
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.2
1.4.1
1.4.0
1.3.0
1.2.0
1.1.0
1.0.1
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fuzzel#185
Reference in a new issue
dnkl/fuzzel
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?