Skip to content

Commit

Permalink
chore: updating readme instructions for config settings
Browse files Browse the repository at this point in the history
  • Loading branch information
wllfaria authored Aug 16, 2024
1 parent 58b5b74 commit 3ddf73e
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,8 @@ to your liking.
- The `completion` field controls which completion engine is used for account and
commodities completion. Right now, we only support nvim-cmp, but this will expand
soon. You can disable completion by setting the enabled value to false.
- Note: if you enable completion through nvim-cmp, you must have nvim-cmp installed
and available.
- The `snippets` field defines which snippet engine you want to use. Currently, we
support native, cmp, and luasnip, with cmp being the default.
- `cmp`: This sets up snippets as a completion source in nvim-cmp, offering snippet
Expand All @@ -88,6 +90,7 @@ to your liking.
the keymaps field. It’s a bit clunky, but it’s an option if you prefer it.
- `luasnip`: This integrates with luasnip to add snippets to Ledger files. It also
works smoothly alongside nvim-cmp.
- Note: this requires luasnip to be installed and available.
- The `keymaps` field defines key mappings for different parts of the plugin:
- The `snippets` section defines keymaps or triggers for snippets. If you're using
native as your snippet engine, this will set the actual keymap in Neovim. You can
Expand Down

0 comments on commit 3ddf73e

Please sign in to comment.