No description
Find a file
2025-09-20 04:48:09 +02:00
.github/workflows fix(ci): run as modukle 2025-09-19 21:20:31 -04:00
after fix(ci): format 2025-09-18 20:04:36 -04:00
doc feat(hl): better hl 2025-09-19 22:23:01 -04:00
ftdetect fix(ci): format 2025-09-18 20:04:36 -04:00
lua/cp feat(hl): better hl 2025-09-19 22:23:01 -04:00
plugin feat: base testing files 2025-09-18 22:25:40 -04:00
scrapers fix(ci): run as modukle 2025-09-19 21:20:31 -04:00
spec feat(hl): better hl 2025-09-19 22:23:01 -04:00
tests/scrapers fix(test): fix the scrapers 2025-09-19 20:32:58 -04:00
.busted fix(ci): revamp 2025-09-18 19:59:07 -04:00
.editorconfig fix: imports 2025-09-18 20:12:01 -04:00
.gitignore fix(ci): unused vars 2025-09-18 23:51:59 -04:00
.luarc.json fix(ci): proper luarc runtime 2025-09-18 19:44:38 -04:00
.pre-commit-config.yaml feat(ci): pre-commit 2025-09-19 16:01:17 -04:00
.python-version initial commit 2025-09-11 23:52:32 -05:00
cp.nvim-scm-1.rockspec remove; 2025-09-18 20:17:51 -04:00
LICENSE fix(ci): format 2025-09-18 20:04:36 -04:00
pyproject.toml feat(ci): pre-commit 2025-09-19 16:01:17 -04:00
README.md feat(hl): better hl 2025-09-19 22:23:01 -04:00
selene.toml fix(ci): fix the tests 2025-09-19 18:46:00 -04:00
stylua.toml fix: imports 2025-09-18 20:12:01 -04:00
uv.lock feat(ci): pre-commit 2025-09-19 16:01:17 -04:00
vim.toml fix(ci): some type errors 2025-09-19 14:04:37 -04:00

cp.nvim

neovim plugin for competitive programming.

https://github.com/user-attachments/assets/cb142535-fba0-4280-8f11-66ad1ca50ca9

video config

Sample test data from codeforces is scraped via cloudscraper. Use at your own risk.

Features

  • Support for multiple online judges (AtCoder, Codeforces, CSES)
  • Language-agnostic features
  • Automatic problem scraping and test case management
  • Integrated running and debugging
  • Enhanced test viewer
  • Templates via LuaSnip

Requirements

  • Neovim 0.10.0+
  • uv: problem scraping (optional)
  • LuaSnip: contest-specific snippets (optional)

Documentation

:help cp.nvim

Philosophy

This plugin is highly tuned to my workflow and may not fit for you. Personally, I believe there are two aspects of a cp workflow:

  • local work (i.e. coding, running test cases)
  • site work (i.e. problem reading, submitting)

Namely, I do not like the idea of submitting problems locally - the experience will never quite offer what the remote does. Therefore, cp.nvim works as follows:

  1. Find a problem
  • Browse the remote and find it
  • Read it on the remote
  1. Set up your local environment with :CP ...
  • test cases and expected output automatically scraped
  • templates automatically configured
  1. Solve the problem locally
  • easy to run/debug
  • easy to diff actual vs. expected output
  1. Submit the problem (on the remote!)

Similar Projects