v0.7.83

The first time you open a problem on a given day, its solution file goes back to the starter code — from either tab, due or not, and whether or not you have ever solved it. Only a due problem opened from Review used to do this; everywhere else handed back the answer you wrote last time, so re-practising began by reading your own solution.

Opening it again the same day keeps the attempt you are writing, and a problem you already submitted today is left alone as well. The reset keeps the language and file the problem was picked in, and lc edit on the command line still reopens an answer unchanged.

Grading two problems in a row no longer fails a sync. Each grade starts one, they shared a single git clone, and git's own index and ref locks made one of them die — Unable to create index.lock, cannot lock ref 'HEAD', or the baffling git commit: On branch main. Syncs now run one at a time, across processes too, so a \s in Vim and the TUI no longer collide. The deck was never at risk; the errors were.

"Nothing to commit" is reported as nothing to do rather than a failed sync.

A git lock left behind by something outside lc is now explained, with the reminder that the clone is disposable.

v0.7.82

The TUI Review table now has a coloured Diff column for Easy, Medium and Hard instead of encoding difficulty only in the problem id's colour. Its title budget shrinks at the pane floor so the new column remains visible without horizontal scrolling.

v0.7.81

A judge request rejected with Cloudflare's HTTP 499 / HTML 403 response now loads the problem page, replaces the stale duplicate CSRF cookies with the fresh token LeetCode issued, and retries once. Account reads could still pass with LEETCODE_SESSION, leaving whoami green while every run failed and printed a page of HTML.

v0.7.80

Browser login now reports when macOS denied access to Safari's cookies and offers p to switch directly to manual cookie entry. It previously swallowed the permission error and repeated “press Enter to retry” even when the user was already signed in and another retry could not reveal the session.

v0.7.79

Every actual review-level change now automatically syncs the configured review repo, including TUI grades, lc review level, and autograde verdicts. Same-level/clamped operations do not start needless network work; sync failures report themselves without undoing the safely recorded local grade.

Built-in-editor submits no longer emit a false bookkeeping warning after the verdict was already recorded; an old duplicate result-display call referred to judge-local data outside its scope.

v0.7.78

The first time a due problem is opened from Review each day, its previous answer is now replaced with starter code in the language already selected. Reopening it later that day preserves the new attempt; Problems-tab and lc edit opens still preserve existing files as before.

v0.7.77

A newly opened Vim or Neovim statement pane now starts at the question heading. Its terminal previously followed lc show's output cursor and settled on the final page; lc now resets the view after that job exits.

v0.7.76

The Review mark now keeps the day's first submitted verdict. A failed first attempt remains red after a successful retry instead of being repainted green; grading still clears the mark, and a new day starts fresh.

v0.7.75

The built-in editor now explicitly resets the question pane to the top when it opens. Some terminal/layout paths could previously settle with a long statement already scrolled to its bottom.

A failed Vim \t test now leaves its case details visible until Enter is pressed instead of immediately redrawing the edit page over the result.

v0.7.74

New solution files and the built-in editor's explicit Reset now contain only LeetCode's starter code, without a generated title/URL comment above it. Existing solution files remain untouched, and legacy headers still strip safely before judging.