No description
Find a file
Barrett Ruth 8398f3428e
feat(race): notification tiers, drift correction, and T=0 retry (#348)
## Problem

Race countdown had three reliability issues:
- Notified every second regardless of remaining time (noisy for
hours-long waits)
- Never re-fetched start times (stale if contest rescheduled)
- No retry on setup failure at T=0 — if the scraper failed at the most
critical moment, the entire countdown was wasted

## Solution

- **Notification tiers**: >1h every 15m, >5m every 1m, >1m every 10s,
≤60s every 1s
- **Drift correction**: re-fetch contest list every 10 minutes, update
`start_time` if changed
- **T=0 retry**: `race_try_setup` calls `scrape_contest_metadata` with
the new `on_error` callback, retrying up to 15 times at 3s intervals
(~45s). Caches metadata on success, then calls `setup_contest` on the
fast (cached) path. Token guard invalidates stale retries after
cancellation.
- **`on_error` for `scrape_contest_metadata`**: optional 4th param,
backward-compatible
2026-03-06 18:43:12 -05:00
.github ci: nix config migration 2026-02-23 18:04:17 -05:00
after/ftplugin rename and simplify things 2025-10-05 11:59:24 -04:00
doc refactor(race): replace :CP race with --race flag (#347) 2026-03-06 18:33:42 -05:00
lua/cp feat(race): notification tiers, drift correction, and T=0 retry (#348) 2026-03-06 18:43:12 -05:00
plugin refactor(race): replace :CP race with --race flag (#347) 2026-03-06 18:33:42 -05:00
scrapers feat: race countdown support and language version selection (#346) 2026-03-06 18:18:21 -05:00
scripts feat(atcoder): extract submit helpers; add live status notifications (#294) 2026-03-04 19:27:29 -05:00
tests feat: race countdown support and language version selection (#346) 2026-03-06 18:18:21 -05:00
.editorconfig fix: imports 2025-09-18 20:12:01 -04:00
.gitignore fix: flake config; 2026-02-17 21:10:29 -05:00
.luarc.json feat(atcoder): extract submit helpers; add live status notifications (#294) 2026-03-04 19:27:29 -05:00
.pre-commit-config.yaml format yml too in pre-commit 2026-02-03 01:43:13 -05:00
.prettierignore some misc fixes 2025-12-07 16:09:17 -06:00
.prettierrc fix: scrapers 2025-10-05 22:10:26 -04:00
.python-version initial commit 2025-09-11 23:52:32 -05:00
.styluaignore feat(atcoder): extract submit helpers; add live status notifications (#294) 2026-03-04 19:27:29 -05:00
cp.nvim-scm-1.rockspec fix(ci): fix rockspec url 2026-02-01 17:01:29 -05:00
flake.lock try to fix the setup 2026-02-18 14:13:37 -05:00
flake.nix fix: replace curl_cffi with scrapling in codeforces metadata (#334) 2026-03-06 13:25:44 -05:00
LICENSE fix(ci): format 2025-09-18 20:04:36 -04:00
pyproject.toml fix: replace curl_cffi with scrapling in codeforces metadata (#334) 2026-03-06 13:25:44 -05:00
README.md docs: fix dependencies section in readme 2026-02-21 23:59:40 -05:00
selene.toml ci: nix config migration 2026-02-23 18:04:17 -05:00
stylua.toml fix: imports 2025-09-18 20:12:01 -04:00
uv.lock fix: remove curl_cffi 2026-03-06 15:05:42 -05:00
vim.yaml fix(config): add bit to ignored filetypes 2026-02-26 19:09:16 -05:00

cp.nvim

The definitive competitive programming environment for Neovim

Scrape problems, run tests, and debug solutions across multiple platforms with zero configuration.

https://github.com/user-attachments/assets/e81d8dfb-578f-4a79-9989-210164fc0148

Features

  • Multi-platform support: AtCoder, CodeChef, Codeforces, and CSES
  • Automatic problem setup: Scrape test cases and metadata in seconds
  • Dual view modes: Lightweight I/O view for quick feedback, full panel for detailed analysis
  • Test case management: Quickly view, edit, add, & remove test cases
  • Rich test output: 256 color ANSI support for compiler errors and program output
  • Language agnostic: Works with any language
  • Diff viewer: Compare expected vs actual output with 3 diff modes

Installation

Install using your package manager of choice or via luarocks:

luarocks install cp.nvim

Dependencies

Quick Start

cp.nvim follows a simple principle: solve locally, submit remotely.

Basic Usage

  1. Find a contest or problem

  2. Set up contests locally

    :CP codeforces 1848
    
  3. Code and test

    :CP run
    
  4. Navigate between problems

    :CP next
    :CP prev
    :CP e1
    
  5. Debug and edit test cases

:CP edit
:CP panel --debug
  1. Submit on the original website

Documentation

:help cp.nvim

See my config for the setup in the video shown above.

Motivation

I could not find a neovim-centric, efficient, dependency-free, flexible, and easily customizable competitive programming workflow that "just works"--so I made it myself. I conferenced with top competitive programmers at Carnegie Mellon Univerity and the University of Virginia and covered their (and my) pain points:

  • Scraping: contests are automatically loaded asynchronously
  • Test Case Management: test case editor (:CP edit)
  • UI: both run and panel layouts cover common formats
  • Extensibility: snippet plugins, compilation, etc. are left to the programmer

Similar Projects