Vault is a tiny(under 2.5MB) note management tool made in rust, the idea came from how I personally store my notes, which happens to be in a directory called "the_vault". This is compatible with all editors, and I am starting to implement more features. Like creating links to projects READMEs and other forms of documentation.
please note that there will be name change coming "notebones" will be the new name of this project soon. I feel that vault is a very forget-able name. also "linking" can be called "ligaments" and that is just so cool. Cheers-
Feedback Wanted. If this is something you are interested in or if this is something you have used & have feedback. Please shoot me a message either by email nreed@linux.com or you can create a issue that will be marked feedback or a respective tag.
# valid path has a forward slash at the end of the path
# set a valid path to your vault
export VAULT_PATH=/path/to/vault/
# set a valid path to your editor
export VAULT_EDITOR=/path/to/your/editor
# the path to your editor should not have a leading forward slash
# after cloning the repo and cd'ing into it.Just run cargo build --release
cargo build --releasewindows:
cmd:
# set a valid path to your vault
set VAULT_PATH "C:/path/to/vault"
# set a valid path to your editor
set VAULT_EDITOR "C:/path/to/your/editor"
# after cloning the repo and cd'ing into it.Just run cargo build --release
cargo build --release
# you can access the binary in /target/release/vaultpowershell:
# set a valid path to your vault
$env:VAULT_PATH = "C:/path/to/vault"
# set a valid path to your editor
$env:VAULT_EDITOR = "C:/path/to/your/editor"
# clone the repo cd the_vault/vault then run the cargo build like below
cargo build --release
# you can access the binary in /target/release/vault- Open the start menu
- Open the option
Edit the system environment variables - Click
Environment variables...button - in
System variablesfind path - Click
Edit - click
new - Put the path to your vault.exe - recommended to put it in C:/Program Files
- Please do not include the file name in the path on the env var you just added
- close your command_prompt or powershell and reopen it.
# this should run fine as long as your defined VAULT_PATH/VAULT_EDITOR
$ vault# note name with spaces. this is normal
$ vault great new note nameYou may notice something cool here. You can type in the note name with no quotes and with spaces. This will also create the file and attach your note title in the file
# listing all the vault files
vault list
# be careful here because you can not recover removed notes
vault rm great-new-note-name# This will rename foo -> bar
vault rename foo bar
# this will also rename foo -> bar
vault mv foo bar# search is by keyword, given a keyword vault will return every file that contains that keyword
vault search note-keyword# this would create a link called "foo" in vault -> this would then edit your project file
vault link /path/to/project-file foo
# to edit your project file you would then just execute this
vault foo=======
#### Removing a note
```bash
# be careful here because you can not recover removed notes
vault rm great-new-note-name
# This will rename foo -> bar
vault rename foo bar
# this will also rename foo -> bar
vault mv foo bar# search is by keyword, given a keyword vault will return every file that contains that keyword
vault search note-keyword# this would create a link called "foo" in vault -> this would then edit your project file
vault link /path/to/project-file foo
# to edit your project file you would then just execute this
vault foo# pulling off of our example above. Lets say you forget where this link goes to
vault view foo
# this ^^ will return "" Linked to: /path/to/project-file ""