Timeline for How to grep in ex command output?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 21, 2015 at 15:31 | comment | added | Sato Katsura |
Are you suggesting that NERDTree should put all its functions in a single file, in order to keep the output of :scriptnames short? Would that make it a better written plugin?
|
|
| Oct 21, 2015 at 14:21 | comment | added | romainl | @AlBerger, a list too long means too many plugins and/or plugins too large or poorly written. 13 files for a single plugin is way too much. | |
| Oct 21, 2015 at 13:39 | comment | added | Sato Katsura |
If the output of your :scriptnames is longer than Magna Carta you might consider installing Tim Pope's scriptease. It provides a function :Scriptnames that puts all that junk in a quickfix list. There you can search it to your heart's content, save it to a file, or go to the corresponding scripts.
|
|
| Oct 21, 2015 at 12:53 | vote | accept | Al Berger | ||
| Oct 21, 2015 at 12:57 | |||||
| Oct 21, 2015 at 12:52 | comment | added | Al Berger | Sorry, don't see what you mean about too long list. E.g. syntastic has in that list 10 files, nerdtree another 13 files, etc. | |
| Oct 21, 2015 at 10:10 | comment | added | Wildcard | Agree with your last sentence. If the output is that long, the filtering should be done directly from the command line, not from within ex. | |
| Oct 21, 2015 at 8:08 | history | answered | romainl | CC BY-SA 3.0 |