ZacharyZhang-NY/omarchycn
2
2
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 3 Wiki Activity

Describe what omarchy-refresh-config validates, not what it doesn't

Browse Source 
The previous wording claimed the argument must name a file under
$OMARCHY_PATH/config/ and that anything else is rejected. The check is
`[[ -e $default_config_file ]]` against an interpolated path, so `../AGENTS.md`
resolves in both trees and copies over $HOME/AGENTS.md, exit 0.
This commit is contained in:
Jeremy Daer
2026-07-31 01:24:51 -07:00
parent e872d3c0b9
commit a737ec4ce3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+2 -2
View File
@@ -262,8 +262,8 @@ omarchy-refresh-config hypr/hyprland.lua
```
This copies `$OMARCHY_PATH/config/hypr/hyprland.lua` to `~/.config/hypr/hyprland.lua`. The argument
must name a file that exists under `$OMARCHY_PATH/config/`; anything else exits with "Not a shipped
user config".
is interpolated into both paths and only checked with `[[ -e ]]`, so pass a plain relative path: a
name containing `..` resolves and copies, landing outside `~/.config` rather than being rejected.
# Migrations