fix: codechef submit fixes and atcoder cleanup (#355 )

## Problem

After the initial CodeChef implementation, submit silently swallowed
"contest not available for submission" errors, and the submit flow used
blind `wait_for_timeout` delays. AtCoder had an unnecessary 500ms settle
delay after file upload.

## Solution

Replace the initial page-load sleep in CodeChef submit with
`wait_for_selector`, replace the 3s post-click sleep with a proper
`wait_for_selector` on the result dialog, and extend the practice
fallback
check to catch both dialog variants. Remove AtCoder's
`BROWSER_SETTLE_DELAY`
and the constant from `timeouts.py`.

2026-03-06 23:40:12 -05:00

2.5 KiB

Raw Blame History

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, USACO, CSES, Kattis
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

GNU time and timeout
uv or nix for problem scraping

Quick Start

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

Basic Usage

Find a contest or problem
Set up contests locally
```
:CP codeforces 1848
```
Code and test
```
:CP run
```
Navigate between problems
```
:CP next
:CP prev
:CP e1
```
Debug and edit test cases

:CP edit
:CP panel --debug

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

2.5 KiB Raw Blame History