octoscope 0.41.3 — keys act on the row you see

When a refresh made one of octoscope's lists shorter, the row it highlighted and the row your keys acted on stopped being the same one. 0.41.3 puts them back together.

How it happened: jump to the bottom of your PRs with G, then a pull request gets merged or a few review requests get answered, and the next refresh brings back fewer rows. The cursor stayed where it was, past the new end. The screen still drew the last row as selected, but enter, o, c and P did nothing until you moved the cursor yourself.

Same on Repos, Issues and Gists. And p, the public-only toggle, did it too: hiding your private rows shortens every list at once.

Now every key acts on the highlighted row, the way the Activity feed and the Inbox already did.

Also since the last post, in 0.41.2: if GitHub refused the search behind the PRs tab's "awaiting your review" section, the whole dashboard failed with it. Now the tab says in one line that it couldn't ask, and everything else loads.

The detail I enjoyed getting right: the test drives octoscope's real model through the exact sequence from the bug report (a fetch, the tab, G, a fetch with fewer rows, enter) and checks that what opens is the row the rendered screen marks as selected. Then I broke each half of the fix on purpose, eight times, and every break failed its own tab's test.

Upgrade:

brew upgrade gfazioli/tap/octoscope

Which list do you live in most: the PRs awaiting your review, your issues, or your repos? And is there a key you wish a row had?

---

Website:

Newsletter:

Discord:

2 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.