- Rust 97.9%
- C 1.5%
- C++ 0.3%
- Objective-C++ 0.3%
|
All checks were successful
CI / build (macos) (push) Successful in 1m4s
CI / lint (macos) (push) Successful in 52s
CI / build (linux) (push) Successful in 4m42s
CI / fmt (push) Successful in 4s
CI / build (windows) (push) Successful in 6m31s
CI / lint (linux) (push) Successful in 3m28s
CI / cargo-deny (push) Successful in 8s
CI / lint (windows) (push) Successful in 3m33s
32 buttons in 10 separator-delimited groups, the same layout and the same assets/icons/ artwork ui_win32 blits and ui_gtk decodes, so all three bars are button-for-button identical. NSToolbar is deliberately not used: it lives in the titlebar and owns its own item model, overflow and customisation UI, whereas Code++'s toolbar is a content-area bar above the tab strip. Placement is not something macOS mandates, so the m1 convention decision keeps Notepad++'s. Wired: the file group, clipboard, undo/redo, zoom, and the three view toggles. Greyed: search and print, the panel toggles, sync-scroll, monitoring and the macro group. Greying is an explicit setEnabled(false), which is not how the menu does it — the menu relies on AppKit's automatic menu enabling, where an item whose action has no implementor greys for free. There is no equivalent for a control, and the first version of this file assumed there was: driving the app reported all 32 buttons isEnabled() == true, so two-thirds of the bar looked live and did nothing on click. The toggles are PushOnPushOff, so AppKit has already flipped the button's state by the time the action fires; the handlers apply that state rather than inverting the model, which would fight the button and land wrong every other click. Toolbar and View menu cannot drift: every View-setting mutation ends in one refresh_toolbar_toggles, and the menu resolves its own marks on open. The gate caught one blocker and one thing worse. set_toolbar_hidden returned true rather than the previous hidden state, which is the trait's contract and what a plugin sees as NPPM_HIDETOOLBAR's return value — plugin-host has a test pinning exactly that. Fixing it surfaced that hiding a strip left a blank band: autoresizing masks handle a window resize, but a hidden view keeps its frame. Win32 relayouts after its ShowWindow; a comment of mine claimed it did not, which was wrong. relayout_chrome recomputes all four bands from scratch, and is a method on CocoaUi rather than a free function: every UiPlatform method already runs inside a with_state borrow, so a nested one is declined and the first version silently never ran. Measured both ways — the editor's frame did not move on any of four hide/show calls before, and afterwards gains exactly the toolbar's 30pt then the tab strip's 26pt and restores. That also closes the same gap the tab strip carried since m3a. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .forgejo/workflows | ||
| assets | ||
| crates | ||
| docs | ||
| plugins | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| deny.toml | ||
| LICENSE | ||
| README.md | ||
| rust-toolchain.toml | ||
| THIRD_PARTY_LICENSES.md | ||
Code++
A 1:1, cross-platform clone of Notepad++ — written in Rust, powered by Scintilla, fast on every OS.
What It Is
Code++ is what Notepad++ would be if it shipped on Linux and macOS without compromising on what made it great on Windows: a fast cold start, instant typing, modest memory use, and a thriving plugin ecosystem.
The promise is concrete:
- Same UX as Notepad++. Tabs, sessions, encoding control, EOL control, find-in-files, syntax highlighting via Scintilla's lexers — the keyboard shortcuts and menus you already know.
- Same plugin ecosystem. Existing Notepad++ plugin DLLs load into Code++ on Windows unchanged. The same plugin source compiles to
.so/.dylibon Linux and macOS. - Same performance class. Cold start under 80 ms, keystroke latency under 5 ms p99, empty-buffer footprint under 25 MB. These are not aspirations — they are constraints enforced at every phase boundary.
- Truly cross-platform. Native Win32, GTK 3, and Cocoa front-ends over a single Rust core. No Electron. No browser engine. No GC runtime.
Why Build This
Notepad++ is excellent and Windows-only. Every "cross-platform Notepad++ alternative" trades performance for portability — usually by wrapping a web view, embedding a JavaScript runtime, or layering a heavy framework. Code++ rejects that trade.
The thesis: performance is an architectural property, not a tuning result. You get Notepad++-class speed by making the right choices up front — a headless core, statically linked Scintilla, the direct-call API for hot paths, lazy plugin loading, and zero startup work that isn't strictly required to paint the first frame. Once those decisions are in place, the speed follows. Once they are violated, no amount of profiling brings it back.
Core Ideas
- Scintilla does what Scintilla does best. We use Scintilla 5.x and Lexilla 5.x for the editing surface, undo/redo, search, and syntax highlighting. We do not reimplement them. We compile them statically into the binary so there is no DLL hell and no loader-time penalty.
- The core is headless.
crates/coreknows about sessions, files, encodings, and EOL — and nothing about windows, HWNDs, GTK widgets, or Scintilla. It is unit-testable without an OS event loop. UI crates depend oncore;coredepends on no one. - Direct-call on every hot path. Scintilla's
SCI_GETDIRECTFUNCTIONreturns a function pointer that bypasses the window message pump. Code++ captures it once per editor and routes every keystroke, insert, and selection through it.SendMessageis reserved for setup and cross-thread one-shots. - Zero work at startup that isn't on the visible-frame critical path. No directory scans. No plugin DLL loads. No project indexing. No AST construction. The session file is read; windows are created; threads are spawned for whatever needs to happen later. That's it.
- Plugins load when they are first used, not before. A user with 40 installed plugins pays no startup cost for the 39 they don't touch this session.
- Notepad++ plugin compatibility from the ground up. The six plugin entry points, the
NppDatastruct, and theNPPM_*/NPPN_*message families are implemented to match Notepad++'s public ABI. A binary plugin that works in Notepad++ on Windows works in Code++ on Windows. - End-to-end demos at every phase. Every implementation phase (see DESIGN.md §7) ends with a runnable demo against real Scintilla, real OS events, real disk I/O, and real plugin DLLs. No phase ships on stubs. This rule exists to stop architectural drift before it starts.
Project Status
Phase 0 — Scaffolding is the current phase. The repository contains the design and developer-environment documentation; the workspace, crates, and submodule pins land next. See DESIGN.md §7.2 for the full phase plan and end-of-phase demo for each.
| Phase | Theme | Demo |
|---|---|---|
| 0 | Workspace + CI green | Empty Win32 window opens and closes |
| 1 | Scintilla shell | Real Scintilla control, type/undo/redo work |
| 2 | Core: session, files, encoding | Open/save/restore real files, no UI freeze |
| 3 | Multi-tab + plugin host | Real N++ plugin DLL loads and runs |
| 4 | Lexers, search, find-in-files | Highlighting + search at scale |
| 4.5 | Per-language keyword + theme wiring | Colour-correct highlighting across ~88 languages |
| 4.6 | User Defined Languages (UDL) | Load N++ UDL XML, preinstalled Markdown UDL, in-app editor modal |
| 5 | Linux (GTK) and macOS (Cocoa) | Same binary builds and runs natively |
Getting Started
For setup instructions on Windows, Linux, and macOS, see DEVELOPMENT.md.
The short version, once your toolchain is in place:
git clone --recurse-submodules https://git.fiedler.live/tux/code-plus-plus.git
cd code-plus-plus
cargo build --workspace
cargo run -p codepp-app
The canonical repository is hosted on Forgejo at https://git.fiedler.live/tux/code-plus-plus. A read-only mirror is pushed to GitHub.
Documentation
- DESIGN.md — full architecture, dependency graph, crate responsibilities, plugin ABI, performance budgets, and the phase plan. Read this if you want to understand any decision in the codebase.
- DEVELOPMENT.md — platform-by-platform setup for Windows, Linux, and macOS, plus common development tasks and troubleshooting.
- CLAUDE.md — operational rules and project conventions used by the AI development assistant.
License
Code++ is licensed under the MIT License. See LICENSE for the full text and THIRD_PARTY_LICENSES.md for the notices required by upstream components (Scintilla and Lexilla under HPND, plus bundled Rust crates).
The Notepad++ plugin compatibility layer under plugins/nppcompat-headers/ is an independent clean-room reimplementation of the public ABI — message numbers, struct layouts, behavior contracts. No source has been copied from Notepad++; the ABI itself is not copyrightable.
Acknowledgements
Code++ stands on the work of two communities:
- Notepad++ by Don Ho and contributors — for two decades of proving that a small, fast text editor is worth caring about.
- Scintilla and Lexilla by Neil Hodgson and contributors — for the editing engine that makes any of this possible.
Code++ is an independent project and is not affiliated with either.