Update README.md

This commit is contained in:
Spencer Gouw 2023-06-22 05:31:58 -07:00 committed by GitHub
parent f3d5309f44
commit c80fe93e57
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -76,13 +76,13 @@ It's since been incorporated back into [julia.vim](https://github.com/JuliaEdito
## Future Improvements/TODO ## Future Improvements/TODO
- Control characters in snippets (e.g. whitespace, particularly newlines? currently snippets are trimmed on both ends; should probably not trim spaces) -[ ] Control characters in snippets (e.g. whitespace, particularly newlines? currently snippets are trimmed on both ends; should probably not trim spaces)
- Semantic symbols in snippets (e.g. where does cursor go afterwards? a snippet with braces might benefit from placing the cursor inside...) -[ ] Semantic symbols in snippets (e.g. where does cursor go afterwards? a snippet with braces might benefit from placing the cursor inside...)
- Regex capabilities -[ ] Regex capabilities
- Bugfixes and auditing? -[ ] Bugfixes and auditing?
- Add newline option for snippet definition to make simple snippets easy rather than cumbersome -[x] Add newline option for snippet definition to make simple snippets easy rather than cumbersome
- Do the things liamcain suggested in my plugin PR to the Obsidian plugin repo. (one half done) -[ ] Do the things liamcain suggested in my plugin PR to the Obsidian plugin repo. (one half done)
### Other caveats ### Other caveats
- The lhs of a snippet cannot have newlines in it. Snippets of that sort will simply fail to work; they'll register but never trigger. The reason why is because I only search from cursor to start of line for snippet text; this is efficient and simple. To fix, we'd have to look backwards from the cursor position and match with the lhs of the snippet. Probably not a hard update, but given that this use case is somewhat rare (imo), I have neglected it. Do submit an issue. - The lhs of a snippet (currently) cannot have newlines in it. Snippets of that sort will simply fail to work; they'll register but never trigger. The reason why is because I only search from cursor to start of line for snippet text; this is efficient and simple. To fix, we'd have to look backwards from the cursor position and match with the lhs of the snippet. Probably not a hard update, but given that this use case is somewhat rare (imo), I have neglected it. Do submit an issue. EDIT: the issue was submitted. Time to get to work.