Skip to content

fix: resolve Omarchy configuration conflicts - #54

Merged
Elliot-32 merged 7 commits into
masterfrom
fix/omarchy-conflicts
Sep 15, 2026
Merged

Elliot-32 merged 7 commits into
masterfrom
fix/omarchy-conflicts

Conversation

@Elliot-32

@Elliot-32 Elliot-32 commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Summary

  • keep Bash as the Omarchy login shell while launching Zsh explicitly from Ghostty
  • route the update alias to omarchy update on Omarchy and document the platform-safe update command
  • make dotfiles own the full Fcitx environment, including GTK compatibility for X11 hosts
  • add hk coverage for the Omarchy compatibility overrides

Rationale

Omarchy's session/login path expects Bash, while interactive terminals should still use Zsh. Omarchy system updates also need to go through its own updater rather than Topgrade so snapshots, migrations, hooks, and package guards remain in the expected path. Fcitx variables remain dotfiles-owned across platforms, preserving GTK IM support on X11.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 855da954e2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -1,3 +1,4 @@
GTK_IM_MODULE=fcitx
INPUT_METHOD=fcitx

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the GTK input method outside Wayland

On supported X11 sessions—explicitly detected via /usr/share/xsessions in home/.miserc.toml—GTK applications rely on GTK_IM_MODULE=fcitx to select the installed Fcitx GTK frontend; INPUT_METHOD is not a GTK replacement. Removing this variable from the shared environment file can therefore disable Fcitx input in GTK applications on non-Omarchy X11 hosts. If Omarchy's Wayland session requires it to be unset, scope that behavior to Omarchy rather than removing it globally.

Useful? React with 👍 / 👎.

]

[shell_alias]
update = "omarchy update"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Document the Omarchy-safe update command

For Omarchy users this only changes the update alias, while README.md:52 still identifies the canonical update command as the literal topgrade. Invoking topgrade directly does not expand this alias, and the interactive Topgrade configuration does not disable system updates, so users following the documented workflow can still bypass Omarchy's snapshot, migration, and package-guard path. Update the command table to direct Omarchy users to update or omarchy update.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

@codex review

1 similar comment

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 4dbe9df436

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@Elliot-32
Elliot-32 merged commit b56b171 into master Sep 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant