Re: [NonGNU ELPA] New package: tabspaces
Colin McLear <[email protected]> Sat, 01 Aug 2026 10:43:52 -0400
| Newsgroups | gmane.emacs.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Philip, thanks again for the quick reply. On 2026-08-01 at 13:59 UTC, Philip Kaludercic <[email protected]> wrote... > Out of curiosity, since I don't know much about this, your > commit > message ends with > > Claude-Session: > https://claude.ai/code/session_019AtEULWCQRLrDCkm7p8KyU > > but the link doesn't give me anything when I open it. Is this > supposed > to be a public URL? (Also, your usage of AI precludes the > package from > being added to GNU ELPA for now, so I'll regard that as a > suitable > explanation for choice of NonGNU ELPA over GNU ELPA.) The Claude-Session trailer comes from Claude Code, which I use primarily for bug-hunting and for testing (I've never really had the patience to create a proper test suite before, so LLMs are a real saviour for me there). The link points at the session that produced the commit, but sessions are private to my account, so the URL resolves to nothing for anyone else. It is an audit trail for me rather than a public reference. I totally understand about the LLM-->GNU Elpa issue. I should have thought of that myself (Codeberg has also recently implemented a fairly strict no LLM policy). >> key-sequence: the option's value is a kbd-syntax string handed >> to kbd >> when the keymap is built. [...] Correct me if I'm wrong, but >> NonGNU >> ELPA ships with Emacs 28.1 and later, so every user who >> installs >> tabspaces from the archive is on 28+ by definition. The only >> people a >> bump to 28.1 could strand are MELPA users still on 27 [...] > > Ah, my bad. But in that case, why not just change the user > option to be > an actual key binding, ie. the default value is (kbd "C-c TAB"), > instead > of a string that denotes a binding? The key binding is a good idea, and much simpler! Done in commit 92cd5ba, refined in 043c030. >> file-equal-p: pr-dir is compared against the sentinel >> completion >> entry "... (choose a dir)" rather than a file name, so equal is >> the >> right test here (this mirrors project-prompt-project-dir in >> project.el). > > OK, I missed that context. Adding a comment might help other > readers in > the future from making that mistake. > The equal vs. file-equal-p comment is added in the same commit. Thanks again. Regards, Colin -- Colin McLear colinmclear.net