dots/nvim
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update documentation references for keymaps and logs

Browse source 
- Changed references from KEYMAPS.md to README.md in multiple files.
- Updated decision log entries to reflect the new documentation structure.
This commit is contained in:
Ray Elliott 2026-01-05 20:27:01 +00:00
commit 025222da2a
7 changed files with 15 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

8
.github/copilot-instructions.md vendored
View file

@ -22,7 +22,7 @@ Modern Lua-first Neovim configuration using lazy.nvim, currently in active migra
│ └── mason*.lua # LSP server installation
├── AGENTS.md # PRIMARY: All rules, migration plan, do-not-reintroduce list
├── MIGRATION_PLAN.md # Phase-by-phase checklist (source of truth for progress)
├── README.md # Decision log and design rationale
├── LOG.md # Decision log and design rationale
└── legacy/ # Archived Vimscript (do not edit; reference only)
```
@ -111,8 +111,8 @@ return {
1. Check `MIGRATION_PLAN.md` for current phase and priorities
2. **Before large changes**: Update plan via CLI `update_plan` tool (if available)
3. **After any change**: Immediately update `MIGRATION_PLAN.md` (check off items, add notes)
4. **After decisions**: Update `README.md` decisions log
5. **After adding/removing/editing any keymaps**: Immediately update `KEYMAPS.md` with the change (add new entries, remove deleted mappings, or update descriptions)
4. **After decisions**: Update `LOG.md` decisions log
5. **After adding/removing/editing any keymaps**: Immediately update `README.md` with the change (add new entries, remove deleted mappings, or update descriptions)
6. Execute phases via subphases (N.x); one bullet = one implement-and-test step
7. Archive legacy files to `legacy/` instead of deleting
@ -179,5 +179,5 @@ Was caused by settings loading at wrong time; fixed by using `on_new_config` wit
## When Stuck
1. Check `MIGRATION_PLAN.md` for known issues and current phase
2. Review `AGENTS.md` for rules about what to avoid
3. Read `README.md` decisions log for context on past choices
3. Read `LOG.md` decisions log for context on past choices
4. Validate with test workspaces before modifying production config