Skip to content

Commit 4e38009

Browse files
committed
Use references instead of inline links in README
1 parent a4147d3 commit 4e38009

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Snippet engines supporting vim-snippets
2020
There are different forks of snippet engines which allow the user to insert
2121
snippets by typing the name of a snippet hitting the expansion mapping.
2222

23-
- [github.com/SirVer/ultisnips](https://github.com/SirVer/ultisnips):
23+
- [github.com/SirVer/ultisnips][7]:
2424
python, supports all snippets in this repo.
2525
- [github.com/garbas/vim-snipmate](https://github.com/garbas/vim-snipmate):
2626
VimL, snipmate-snippets, engine sometimes behaves strange. Supports
@@ -39,9 +39,8 @@ UltiSnips has additional features such as high speed, nesting snippets,
3939
expanding snippets in snippets and offers powerful transformations on text in
4040
snippets (like visual selections or placeholder texts).
4141

42-
Which one to use? If you have python give
43-
[SirVer/ultisnips](https://github.com/SirVer/ultisnips) a try because its fast
44-
and has the most features.
42+
Which one to use? If you have python give [SirVer/ultisnips][7] a try because
43+
its fast and has the most features.
4544

4645
If you have VimL only (vim without python support) your best option is using
4746
[garbas/vim-snipmate](https://github.com/garbas/vim-snipmate) and cope with the

0 commit comments

Comments
 (0)