@@ -325,6 +325,11 @@ behaviour of the ledger filetype.
325
325
326
326
let g:ledger_fillstring = ' -'
327
327
328
+ * If you want account completion based on fuzzy matching instead of the
329
+ default sub-level completion, include the following line:
330
+
331
+ let g:ledger_fuzzy_account_completion = 1
332
+
328
333
* If you want the account completion to be sorted by level of detail/depth
329
334
instead of alphabetical, include the following line:
330
335
@@ -447,8 +452,8 @@ Omni completion is currently implemented for account names only.
447
452
448
453
### Accounts
449
454
450
- Account names are matched by the start of every sub-level. When you
451
- insert an account name like this:
455
+ By default, account names are matched by the start of every sub-level. When
456
+ you insert an account name like this:
452
457
453
458
Asse<C-X><C-O>
454
459
@@ -460,6 +465,16 @@ Go ahead and try something like:
460
465
461
466
When you have an account like this, 'Assets:Bank:Checking' should show up.
462
467
468
+ If fuzzy matching based account completion is enabled, the matches are
469
+ loaded based on string similarity and without regard for the sub-levels.
470
+
471
+ In the previous example, with fuzzy matching enabled, you could load up
472
+ matches by doing something like:
473
+
474
+ Chec<C-X><C-O>
475
+
476
+ Notice that we did not need to write the initial account components.
477
+
463
478
When you want to complete on a virtual transaction, it's currently best
464
479
to keep the cursor in front of the closing bracket. Of course you can
465
480
insert the closing bracket after calling the completion, too.
0 commit comments