From bafd7c51e0c921f403cb1c76835cd6652d1dd78a Mon Sep 17 00:00:00 2001 From: Stefan Huber Date: Sat, 15 May 2021 22:03:12 +0200 Subject: [PATCH] README: Name the recommended ctags impl first (#761) Clearly steer users away from Exuberant Ctags and be more explicit that it is less well supported and will be deprecated. Rephrase sentence on additional providers because an exemplary enumeration (such as) does not redundantly need to add (or others). --- README.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 49ed56a..d2d8e64 100644 --- a/README.md +++ b/README.md @@ -23,13 +23,16 @@ creates the tags it needs on-the-fly in-memory without creating any files. * [Vim](http://www.vim.org/) >= 7.3.1058 or any version of [NeoVim](https://neovim.io/). -* [Exuberant Ctags](http://ctags.sourceforge.net/) >= 5.5, - or (**highly recommended**) any version of [Universal - Ctags](https://ctags.io) which is a currently maintained fork of Exuberant - Ctags with many bugfixes, support for many more formats, and proper Unicode - support. Some additional formats can also be handled by other providers such - as [jsctags](https://github.com/sergioramos/jsctags), - [phpctags](https://github.com/vim-php/phpctags), or others. +* A ctags implementation: We _highly recommend_ any version of [Universal + Ctags](https://ctags.io). It is a maintained fork of Exuberant Ctags with + many bugfixes, support for many more formats, and proper Unicode support. + + [Exuberant Ctags](http://ctags.sourceforge.net/) 5.5 or higher works to some + degree but will be deprecated eventually. + + Some additional formats can also be handled by other providers such as + [jsctags](https://github.com/sergioramos/jsctags) or + [phpctags](https://github.com/vim-php/phpctags). ## Installation