Start 1Password at a fixed device scale factor (#10673)
1Password reads the display scale itself, the way Electron apps do, so on a scaled monitor it comes up oversized next to every other window. Pin it with --force-device-scale-factor=1 and let the compositor scale it. The app menu is covered by the packaged .desktop, which we build ourselves in omarchy-pkgs. This is the other route in: the hotkey runs the binary directly and never reads that file. Claude-Session: https://claude.ai/code/session_01JB9phxP56gnP7qSidkkUJE Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
a7486beb60
commit
446fbc28b1
2 files changed
+7
-3
No files matched your search
@@ -31,8 +31,9 @@ chmod +x "$mock_bin"/*
|
||||
launch_log="$test_tmp/launch-log"
|
||||
PATH="$mock_bin:$PATH" OMARCHY_TEST_INSTALLED=true OMARCHY_TEST_LOG="$launch_log" \
|
||||
bash "$ROOT/bin/omarchy-launch-1password"
|
||||
grep -Fxq 'launch:-- 1password' "$launch_log" || fail "1Password launcher starts the installed app"
|
||||
pass "1Password launcher starts the installed app"
|
||||
grep -Fxq 'launch:-- 1password --force-device-scale-factor=1' "$launch_log" ||
|
||||
fail "1Password launcher starts the installed app at a fixed scale factor"
|
||||
pass "1Password launcher starts the installed app at a fixed scale factor"
|
||||
|
||||
PATH="$mock_bin:$PATH" OMARCHY_TEST_INSTALLED=false OMARCHY_TEST_LOG="$launch_log" \
|
||||
bash "$ROOT/bin/omarchy-launch-1password"
|
||||
|
||||
Reference in new issue
Block a user