Repository navigation
Conversation
…e rung After #169 merged, the opensuse tumbleweed rung went red without compiling anything. The openSUSE-Tumbleweed-Update repo timed out ("Curl error (28)") on every one of the four refresh retries. The plain install then failed, and the `zypper dup` fallback refuses outright to run while any enabled repo failed to refresh. When the retried refresh still fails, that one repo is now disabled. It only carries rare urgent patches; Tumbleweed itself ships through Oss. A plain install can live with a stale repo, and dup can now run. Other repos are untouched: one that keeps failing still fails the build.
Pulls in the scheduled_tasks.lock ignore, so the .claude submodule no longer shows as modified while Claude Code runs, plus the kit's own test, README and markdownlint fixes.
modifyrepo matches aliases; openSUSE-Tumbleweed-Update is only the display name, so the previous line disabled nothing and '|| true' hid the error.
…#140) Alt-F / Ctrl-Right take the next word of the ghost; Alt-N / Alt-P step to the next older / back to the newer distinct history match. All four go through the slot module: with no history ghost on screen, or when the user bound the key, the stock readline function (forward-word, non-incremental search) runs unchanged. The cycle keeps history indices, not copies, and is dropped when the line or the history length changes, so a bind -x widget running `history -c` mid-cycle cannot leave it pointing past the end. Tests: autosuggest_test.py W1-W6, C1-C11 on both readers. Mutants M1-M10 (slot wiring, word boundaries, cycle order, dedupe, bell ends, user-bind precedence) each turn at least one case red. M11, dropping the history-length check, leaves a ghost after `history -c` and draws an ASan heap error. The 168-byte AS_LEAKS=1 report after stock Alt-N + Ctrl-G shows up identically on develop without this change (readline's own non-incremental search).
chore(claude): bump the kit to its hygiene fixes
fix(docker): disable an unreachable Tumbleweed Update repo instead of failing the rung
feat(editor): word-accept and cycling for inline suggestions (#140)
docs: clarify print -P prompt preview caveat (#134)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Closes #
How I verified it
make re(SAFE=1 debug) builds clean, no warningsmake re OPT=1(SAFE=0 optimized) builds clean, no warningsmake testis green (libc heap)cd tests && ./verify_alloc.shgreen on both SAFE=1 and SAFE=0HELLISH_ALLOC_STATS(SAFE=0)
huge args, deep nesting)
make normclean on touched files (no in-function comments, ≤80 cols,no new globals)
Notes / trade-offs