Skip to content

Commit 5c72be7

Browse files
committed
Add commands for installing in various plugin managers
1 parent 8378c01 commit 5c72be7

1 file changed

Lines changed: 15 additions & 16 deletions

File tree

README.md

Lines changed: 15 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Javascript | :heavy_check_mark: | :x:
6565
PHP | :heavy_check_mark: | :heavy_check_mark:
6666
Python | :heavy_check_mark: | :heavy_check_mark:
6767
R | :heavy_check_mark: | :heavy_check_mark:
68-
Ruby | :heavy_check_mark: | :x:
68+
Ruby | :heavy_check_mark: | :heavy_check_mark:
6969
Shell | :heavy_check_mark: | :heavy_check_mark:
7070
Vim | :heavy_check_mark: | :heavy_check_mark:
7171

@@ -92,7 +92,7 @@ Default mappings are: `<Leader>ds`, `<Leader>dS` respectively.
9292

9393
### Remarks - Debugging
9494

95-
* Make sure that the filetype plugin is enabled. A line like `filetype plugin on` in
95+
* Make sure that `filetype plugin` is enabled. A line like `filetype plugin on` in
9696
your `.vimrc` should do the job.
9797

9898

@@ -106,15 +106,17 @@ debugstring depends on the following vim plugins:
106106

107107
### Using a runtimepath/package manager
108108

109-
I would personally recommend using [Pathogen](https://github.com/tpope/vim-pathogen/) for
110-
installing the plugin but any other installation method (e.g.,
111-
[Vundle](https://github.com/VundleVim/Vundle.vim)) should do the job (if not
112-
please raise an
113-
[issue](https://github.com/bergercookie/vim-debugstring/issues) on Github)
109+
| Plugin manager | How to install |
110+
| :------------- | :------------- |
111+
| [Dein][1] | `call dein#add('bergercookie/vim-debugstring')` |
112+
| [minpac][2] | `call minpac#add('bergercookie/vim-debugstring')` |
113+
| [Pathogen][3] | `git clone https://github.com/bergercookie/vim-debugstring.git ~/.vim/bundle/vim-debugstring` |
114+
| [Plug][4] | `Plug 'bergercookie/vim-debugstring'` |
115+
| [Vundle][5] | `Plugin 'bergercookie/vim-debugstring'` |
116+
| manual | copy all of the files into your `.vim` directory (or `~/.config/nvim` if you're using neovim)|
114117

115-
```bash
116-
git clone https://github.com/tpope/vim-repeat ~/.vim/bundle/vim-repeat
117-
git clone https://github.com/bergercookie/vim-debugstring.git ~/.vim/bundle/vim-debugstring
118+
119+
Plugin also utilizes [vim-repeat](https://github.com/tpope/vim-repeat) if the latter is installed.
118120

119121
```
120122
@@ -155,22 +157,19 @@ this or other vim plugins
155157
156158
## TODO
157159
158-
- [ ] Method to delete all the debugging strings in all "touched" buffers
159-
- [ ] Method to delete all the debugging strings in current buffer
160+
- [ ] Method to delete all the debugging strings in current buffer / all "touched" buffers - see far.vim
160161
- [x] Method to print name and contents of a variable
161-
- [ ] Add option for variable debugging in rest of langs
162162
- ~[ ]Make the counter buffer-specific~ Nope, we already have the filename &
163163
line for file-specific text
164164
- [ ] Escape double single quotes vimscript variable printing
165165
- [x] Append to current line if that is empty
166166
- [x] Support repeat.vim
167-
- [ ] Use an assertion module
167+
- [x] Use an assertion module - vader
168168
- [x] Use vader.vim for TDD
169-
- [ ] Extend vader support for rest of languages
169+
- [x] Extend vader support for rest of languages
170170
- [x] Use travis for CI
171171
- [x] Bug with changing the filename of the current file
172172
- [x] Make vim-repeat dependency optional
173173
- [x] Turn supported languages into a table - what do we support in which
174174
language
175175
- [x] Make vim-repeat dependency optional
176-
- [] Have .vader test filetypes use the same function as standard vim files

0 commit comments

Comments
 (0)