From a737ec4ce348b29d1fdba86c3c9196ae4b189eea Mon Sep 17 00:00:00 2001 From: Jeremy Daer Date: Fri, 31 Jul 2026 01:24:51 -0700 Subject: [PATCH] Describe what omarchy-refresh-config validates, not what it doesn't 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. --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 975f2497..868b3b41 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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