ledgerkit-editor
A keyboard-driven terminal editor for hledger plain-text accounting journals.
Early beta — use with caution. This software is under active development and may corrupt your journal files. Always keep a backup before editing. Do not use on irreplaceable data without a recovery plan.
Built with Textual and ledgerkit.
Features
- Full-screen text editor with hledger syntax highlighting (dates, payees, accounts, amounts, commodities, comments, directives)
- Monokai Pro default theme; runtime theme switching supported
- Incremental search with match highlighting (
Ctrl+F,Shift+PgUp/Down) - View filter — show all / cleared-only / unreconciled-only transactions (
Ctrl+L) - Transaction block selection and duplication (
Ctrl+T,Ctrl+G) - Cleared status toggle — single transaction (3-state cycle) and bulk selection (
Ctrl+R) - Insert today's date at cursor (
Ctrl+D) - Date shifting with
Shift+Up/Shift+Down(cursor-position-aware) - Save with date-sort and whitespace re-alignment (
Ctrl+S) - Undo / Redo (
Ctrl+Z/Ctrl+Y) - Command palette (
Ctrl+P)
Planned / In Progress
- Transaction filter popup (
Ctrl+O) — UI stub only; criteria filtering not yet implemented - BalanceSidebar — account balance tree (wired up, threaded refresh on save)
- RegisterPanel — account transaction register (wired up, last 500 rows)
- Reconciliation mode
Installation
From PyPI
pip install ledgerkit-editor
ledgerkit-editor path/to/my.journal
Development setup
git clone https://github.com/ctosullivan/ledgerkit-editor.git
cd ledgerkit-editor
python -m venv .venv
.venv\Scripts\activate # Windows
# source .venv/bin/activate # macOS / Linux
pip install --upgrade pip
pip install -e ".[dev]"
# Run tests
pytest --tb=short
# Launch
ledgerkit-editor path/to/my.journal
Journal File Resolution
The editor resolves the journal file in this order:
- Path passed as a command-line argument
$LEDGER_FILEenvironment variable~/.hledger.journaldefault- Interactive prompt on launch (if none of the above resolve)
Keyboard Shortcuts
See docs/shortcuts.md for the full reference.
Requirements
- Python 3.9+
- textual 8.2.5
- ledgerkit 1.0.0.dev1
Development
See CONTRIBUTING.md for setup instructions and the ledgerkit dependency update workflow.
Roadmap
See ROADMAP.md for planned features and current development status.
This repository was previously named
PyLedger-editor. GitHub redirects old URLs automatically.
Metadata
Release files for ledgerkit-editor 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ledgerkit_editor-1.0.2.tar.gz | 76.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ledgerkit_editor-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 135.3 kB
Release files / ledgerkit_editor-1.0.2.tar.gz
| Download URL | ledgerkit_editor-1.0.2.tar.gz |
|---|---|
| Size | 76.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ee320117445d48a4bf19ba4e6fe022e312c95895ce928af0569755f883d49f7
|
|
BLAKE2b-256 checksum How to use checksums |
f6df8a498248ab4add9af605321173d3297e3cde68df4475e9b824d4c5e8ee76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / ledgerkit_editor-1.0.2-py3-none-any.whl
| Download URL | ledgerkit_editor-1.0.2-py3-none-any.whl |
|---|---|
| Size | 59.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cafe9e9a697e5f0e8cf3008cb752ba398f5ff1d65b96aa6076c29b58c0e141c7
|
|
BLAKE2b-256 checksum How to use checksums |
c1b54483c10b8daf4aa6e79f62f03c4993cd2ed29e07a01cfd4951070047ce79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log