Linux Note Pad lnp

lnp · linux note pad

All your notes.
None of your screen.

Linux Note Pad holds as many plain-text notes as you like, three levels deep — notebooks down one side, notes across the top, and collections above them both when one rail is no longer enough. It lives in the tray. One keystroke pops the pad, one puts it away, and while it is away it takes no screen space at all.

$ sudo apt install ./lnp.deb
GTK 3 · Cinnamon-first plain .txt files .deb package no network, ever
The Linux Note Pad window: a rail of notebooks down the left — Work, Notes, Home, Recipes, Projects, with Work selected — a row of note tabs across the top — Tuesday, Standup, Budget, Links, with Tuesday in front — and the note's text filling the rest of the window on dark paper.

notebooks down the side, notes across the top — and nothing else in the way

the whole point

Sticky notes solve the right problem the wrong way.

Fast, always-there scratch capture is worth having. Papering your desktop with it is not. Linux Note Pad keeps the immediacy and gives back the screen: a resident daemon holds your notes in memory, and the window appears only when you ask for it. There are three ways to ask.

01 · hotkey

One key, both ways

Bind lnp --toggle in your desktop's Keyboard settings. It shows the pad if it is hidden and hides it if it is showing. The app never grabs a key out from under your desktop — the binding stays yours, in the place you already manage bindings.

02 · tray

System tray

An indicator sits in your panel: show or hide, open the trash, export everything, reach preferences, quit. It stays deliberately small — it is how you reach the app, not how you navigate inside it. Tint its outline to suit your panel.

03 · cli

Command line

lnp --new "call back" captures a thought without your hands leaving the keyboard; it takes a name, a notebook, or standard input. --list prints your notebooks and notes, --export writes the lot out as .txt files.

collections

A third level, for when one rail is not enough.

Notes sit in notebooks; notebooks sit in a collection. You work in one collection at a time, so the rail stays as short as the job in front of you — which is the whole point. A dozen notebooks and finding one becomes the thing you spend your time on, and that is exactly the clutter this pad exists to remove.

Switch with the books button in the corner of the pad; the collection you are in is named in the title bar, so you always know whose notebooks you are looking at before you start typing. Nothing on disk moves when you reorganize — a collection is a level in the index and nothing more, so moving a notebook between them is a rename, not a file copy, and cannot cost you a note.

One name reaches anywhereCollection//Notebook::Note in a link, on the command line, and in an export filename. Leave the collection off and the name means the one you are in.
Find crosses them — the widest search scope reads every collection at once and takes you to the hit wherever it lives.
Deleting one requires it to be empty — no cascade. Emptying a collection is a deliberate act, not a side effect of tidying up.
The collections manager: a list with two collections, Consulting holding four notebooks and Personal holding two, beside buttons to create, rename, delete, reorder, copy a link address and sort.

the manager — the only place that shows every collection at once

find

This note, this notebook, this collection, or everything you have.

The find bar slides up from the bottom with four scopes, the widest reaching across every collection at once. Widen it and the results become a list of notes, each with its match count and a preview — pick one and the pad opens it on the match, switching collections under you if that is where it lives. Phrase, all-words or any-word, with whole-words and match-case where you need them.

The find bar open across the bottom of the pad, searching for the word rates in the All collections scope: four results listed by qualified name — Work::Tuesday, Work::Budget, Work::Links and Personal//Home::Groceries, the last one in a different collection — each with a preview and a match count, and a summary reading 4 in 4 notes.

search across every collection — results by full name, with counts and previews

your notes are files

Plain text, on your disk, readable without this app.

Every note is a .txt file in your own data directory. No database, no sync service, no account, no format to be locked into. If Linux Note Pad vanished tomorrow your notes would still open in any editor you own.

Identity loss is recoverable. Data loss is the unpardonable sin. The rule the file handling is built around. When a design choice trades one against the other, the bytes win over the name, the order, and the placement — which is why renaming and reordering never touch the filesystem, why every write that matters is atomic, why deleting goes to a trash you can undo, and why export exists.

Atomic writes — a save is a write-and-rename with a .bak kept beside it. An interrupted save cannot leave you half a note.
A trash, not a delete — deleted notes and notebooks sit in a trash you can browse and restore, pruned on a schedule you set.
Autosave you never think about — typing settles for half a second and it writes; a long stretch of typing writes anyway.
Export any time — the whole store, one notebook, or one note, out to Notebook::Note.txt files.
Undo per note — a deep undo stack that survives switching tabs and comes back where you left it.
It remembers where you were — every collection its notebook, every notebook its note, every note your place in it. Come back tomorrow and the pad opens where you stopped.
Order it once — sort notes, notebooks or collections by name, created or modified, either direction. A one-time tidy, not a mode: drag things by hand afterwards and nothing re-sorts behind you.
Tables of contents on demand — index a notebook or a whole collection into an ordinary note full of working links, generated when you ask and never behind your back.
Nothing leaves the machine — no network connections, no telemetry, no accounts. The daemon talks to one socket in your own runtime directory.
The Linux Note Pad preferences window on the Appearance tab: notebook rail left or right, rail names centered or left, note tabs top or bottom, rail width, interface text size, and a row of tray icon frame colors.

preferences — or edit the TOML by hand; your comments survive

make it yours

Put the strips where you want them.

The notebook rail goes left or right, the note tabs top or bottom, and both remember their width. Set the note font and the interface font separately, pick your own paper and ink, and rebind every accelerator in the app.

All of it lives in one commented config.toml you are welcome to edit by hand — the preferences window writes around your comments rather than over them, and the app picks up the change without a restart.

Rail and tabs — either side, either edge, your width, notebook names centered or flush left.
Fonts and colors — note text and interface text sized independently; paper, ink, tabs and link colors all yours.
Keys — every shortcut rebindable, because one of them will collide with your desktop.

install

One .deb, then apt.

Download the package and hand it to apt — GTK 3, the indicator bindings and the rest are pulled in automatically.

$ curl -O https://smisco.biz/lnp/lnp.deb
$ sudo apt install ./lnp.deb

Then bind your key. Open your desktop's Keyboard settings and give a custom shortcut the command lnp --toggle. That one key is the whole interface when the pad is hidden — and pressing it with nothing running starts the daemon and shows the pad in one go.

Requirements. A GTK 3 desktop with a system tray. Built and tested on Linux Mint / Cinnamon; other desktops generally work. Linux Note Pad depends on no display server of its own, so it is expected to run under Wayland — that is untested rather than promised.

Download the .deb latest — v1.7.4 · amd64