barrett/cp.nvim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 13
No description
1018 commits 74 branches 11 tags 2.2 MiB
Find a file
Barrett Ruth 690469bd99
fix(utils): discover nix submitEnv dynamically in dev checkout 
Problem: In a dev checkout, `_nix_submit_cmd` is nil (only baked in by
the nix derivation). The uv fallback fails with code 127 on NixOS because
`uv` is not a bare system binary — it's only available via the FHS-wrapped
`cp-nvim-submit` script produced by `mkSubmitEnv`.

Solution: Add `discover_nix_submit_cmd` mirroring `discover_nix_python`:
runs `nix build #submitEnv --no-link --print-out-paths`, caches the result
in `stdpath('cache')/cp-nvim/nix-submit`, and sets `_nix_submit_cmd`.
`run_scraper` calls `setup_nix_submit_env()` before spawning submit.
2026-03-04 19:22:57 -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(credentials): promote login/logout to top-level actions 2026-03-04 13:03:40 -05:00
lua/cp fix(utils): discover nix submitEnv dynamically in dev checkout 2026-03-04 19:22:57 -05:00
plugin refactor(credentials): promote login/logout to top-level actions 2026-03-04 13:03:40 -05:00
scrapers fix(atcoder): suppress ty unresolved-import for optional deps 2026-03-04 19:04:43 -05:00
scripts ci: format 2026-03-04 19:03:54 -05:00
tests fix(ci): formatting and typing 2026-02-18 14:13:37 -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 ci: scripts + format 2026-03-04 13:51:56 -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 ci: scripts + format 2026-03-04 13:51:56 -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 ci: format 2026-03-04 19:03:54 -05:00
LICENSE fix(ci): format 2025-09-18 20:04:36 -04:00
pyproject.toml ci: format 2026-03-04 19:03:54 -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 ci: format 2026-03-04 19:03:54 -05:00
vim.yaml fix(config): add bit to ignored filetypes 2026-02-26 19:09:16 -05:00

README.md

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