notes

Simple delightful note taking, with none of the lock-in.

This demo uses zsh, vim and dropbox, but don't panic, that's just me. notes will work just fine with whatever other text editor, shell and syncing solution you feel like.

Why do I want this?

You already have a tool that backs up and syncs your data (be it Dropbox, iCloud, Seafile or whatever). You already have a text editor on your desktop, your laptops, your phone and that tablet you've forgotten about.

You want to take notes.

You could use a web X.0 note taking app that reimplements all of that from scratch (poorly). You could tie yourself to a tool that holds all your data for you in its own brand-new format, locks you into its (often bloated) UI, and then steadily removes features unless you start paying (hey Evernote). You don't have to.

Instead, you could have a simple folder full of simple text files, synced with your sync-thing of choice, edited with your edit-thing of choice. It's easy to understand, easy to use, and accessible from a million other new tools too whenever you next fancy a change. You can do this with little more than windows explorer and notepad, but it's nice to have a specialised tool to add on top and make this a little neater where you can.

That's where notes comes in. Bring your own data syncing, bring your own text editor, put your notes in good old fashioned files, and notes will give you a CLI tool to neatly glue it all together.

This is just one tool in the chain. notes is a command line tool, and some people will want a proper UI, or a web interface, or something that works on mobile. You can use this in one place and solve every other step in that chain any other way you like though — there's no shortage of simple file browsers and text editors that'll get the job done on any platform you like.

How do I install this?

Download notes, chmod +x, put it in your $path. This will probably do it:

curl https://cdn.rawgit.com/pimterry/notes/v0.1.2/notes > /usr/local/bin/notes && chmod +x /usr/local/bin/notes

By default your notes live in ~/notes, but you can change that to anywhere you like by setting the $NOTES_DIRECTORY environmental variable.

How do I use it?

notes new <note-name>

Opens your $EDITOR of choice for a new note, with the given name. The name can include slashes, if you want to put your note in a subfolder. Shorthand alias also available with notes n.

notes find <part-of-a-note-name>

Searches note filenames and paths for the given string, and returns all the matches. Shorthand alias also available with notes f.

notes grep <part-of-some-note-content>

Searches all note content for the given string and returns all the matches. Shorthand alias also available with notes g.

notes open

Opens your notes folder in your default configured file explorer. Shorthand alias also available with notes o.

notes open <note-name>

Opens a given note in your $EDITOR. Name can be an absolute path, or a relative path in your notes (.md suffix optional). Shorthand alias also available with notes o.

notes rm [-r | --recursive] <note-name>

Remove the given note if it exists. If -r or --recursive is given, delete the folders/notes recursively.

notes grep/find <pattern> | notes open

Combine these together! This opens each matching note in your $EDITOR in turn.

Tell me of the future

All the above works. Here's what's coming next:

• Combining find and grep, to match either one
• More interesting and nicer looking file/grep search result formatting (...only when not piping?)
• Make the file extension optional
• Bash/zsh command autocompletion
• Bash/zsh note name autocompletion
• Interactive mode? notes could open a scrollable list of notes, open your editor when you pick one, and reappear after you close it.
• Tree view.
• Easy way to see short notes snippets in find/grep/tree? Could be option (--snippets) or by piping to a command (notes find | notes snippets). Maybe call it head?
• Version control - probably by finding an easy (optional) way to integrate this automatically with Git.

I want to help

Great! Jump in. Feel free to play around, open an issue with new feature ideas or open PRs for fixes (although check with an issue first if you want to do anything substantial).

If you want to get the code locally you'll need to:

git clone <your fork>
git submodule update --init --recursive
./test.sh # Check the tests work before you make any changes

If you submit a PR, please make sure it:

• Doesn't break existing tests
• Adds new tests, if appropriate
• Adds new documentation, if appropriate