command-t 1.9.1 → 1.10
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/LICENSE +1 -1
- data/README.txt +241 -101
- data/doc/command-t.txt +241 -101
- data/doc/tags +11 -0
- data/plugin/command-t.vim +2 -22
- data/ruby/command-t/Makefile +21 -22
- data/ruby/command-t/controller.rb +49 -28
- data/ruby/command-t/depend +2 -22
- data/ruby/command-t/ext.bundle +0 -0
- data/ruby/command-t/ext.c +2 -22
- data/ruby/command-t/ext.h +2 -22
- data/ruby/command-t/extconf.rb +2 -22
- data/ruby/command-t/finder.rb +2 -22
- data/ruby/command-t/finder/buffer_finder.rb +2 -22
- data/ruby/command-t/finder/file_finder.rb +2 -22
- data/ruby/command-t/finder/jump_finder.rb +2 -22
- data/ruby/command-t/finder/mru_buffer_finder.rb +2 -22
- data/ruby/command-t/finder/tag_finder.rb +6 -22
- data/ruby/command-t/match.c +6 -23
- data/ruby/command-t/match.h +3 -22
- data/ruby/command-t/match_window.rb +8 -27
- data/ruby/command-t/matcher.c +11 -25
- data/ruby/command-t/matcher.h +2 -22
- data/ruby/command-t/mru.rb +2 -22
- data/ruby/command-t/prompt.rb +18 -22
- data/ruby/command-t/ruby_compat.h +2 -22
- data/ruby/command-t/scanner.rb +2 -22
- data/ruby/command-t/scanner/buffer_scanner.rb +2 -22
- data/ruby/command-t/scanner/file_scanner.rb +2 -22
- data/ruby/command-t/scanner/file_scanner/find_file_scanner.rb +2 -22
- data/ruby/command-t/scanner/file_scanner/ruby_file_scanner.rb +2 -22
- data/ruby/command-t/scanner/file_scanner/watchman_file_scanner.rb +2 -22
- data/ruby/command-t/scanner/jump_scanner.rb +2 -22
- data/ruby/command-t/scanner/mru_buffer_scanner.rb +2 -22
- data/ruby/command-t/scanner/tag_scanner.rb +8 -23
- data/ruby/command-t/settings.rb +2 -22
- data/ruby/command-t/stub.rb +2 -22
- data/ruby/command-t/util.rb +2 -22
- data/ruby/command-t/vim.rb +2 -22
- data/ruby/command-t/vim/path_utilities.rb +2 -22
- data/ruby/command-t/vim/screen.rb +2 -22
- data/ruby/command-t/vim/window.rb +2 -22
- data/ruby/command-t/watchman.c +2 -22
- data/ruby/command-t/watchman.h +2 -22
- metadata +17 -17
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 12d8531502158d735acade5b00128048555140f7
|
4
|
+
data.tar.gz: a344dfa12e20fc81e159531b2e4623e0f8625642
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: d242333088628804ddd1dada59c44b3237e2c3448a2c3aaf8a9295c2f01375e5f99a3f1cebb42e6dee45e4abbc1901e26f507380290cccaf1ea86f9e50e6538a
|
7
|
+
data.tar.gz: 3172d42364bf309754fe8cfdb766f3df78b313186549cdec8a0ce523d8581a0cf2dc53452773063db7b2a1e4a8dd35645393c7015ff8b6f3dec10543d61218bd
|
data/LICENSE
CHANGED
data/README.txt
CHANGED
@@ -5,7 +5,6 @@ CONTENTS *command-t-contents*
|
|
5
5
|
1. Introduction |command-t-intro|
|
6
6
|
2. Requirements |command-t-requirements|
|
7
7
|
3. Installation |command-t-installation|
|
8
|
-
3. Managing using Pathogen |command-t-pathogen|
|
9
8
|
4. Trouble-shooting |command-t-trouble-shooting|
|
10
9
|
5. Usage |command-t-usage|
|
11
10
|
6. Commands |command-t-commands|
|
@@ -16,9 +15,8 @@ CONTENTS *command-t-contents*
|
|
16
15
|
11. Authors |command-t-authors|
|
17
16
|
12. Development |command-t-development|
|
18
17
|
13. Website |command-t-website|
|
19
|
-
14.
|
20
|
-
15.
|
21
|
-
16. History |command-t-history|
|
18
|
+
14. License |command-t-license|
|
19
|
+
15. History |command-t-history|
|
22
20
|
|
23
21
|
|
24
22
|
INTRODUCTION *command-t-intro*
|
@@ -94,11 +92,15 @@ On OS X Snow Leopard, Lion and Mountain Lion, the system comes with Ruby 1.8.7
|
|
94
92
|
and all recent versions of MacVim (the 7.2 snapshots and 7.3) are linked
|
95
93
|
against it.
|
96
94
|
|
97
|
-
On OS X Mavericks, the default system
|
98
|
-
link against 1.8.7,
|
95
|
+
On OS X Mavericks, the default system Ruby is 2.0, but MacVim continues to
|
96
|
+
link against 1.8.7, as does the Apple-provided Vim. Ruby 1.8.7 is present on
|
97
|
+
the system at:
|
99
98
|
|
100
99
|
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
|
101
100
|
|
101
|
+
On OS X Yosemite, the default system Ruby is 2.0, and the Vim that comes with
|
102
|
+
the system links against it.
|
103
|
+
|
102
104
|
On Linux and similar platforms, the linked version of Ruby will depend on
|
103
105
|
your distribution. You can usually find this out by examining the
|
104
106
|
compilation and linking flags displayed by the |:version| command in Vim, and
|
@@ -140,26 +142,128 @@ folder.
|
|
140
142
|
|
141
143
|
INSTALLATION *command-t-installation*
|
142
144
|
|
143
|
-
You
|
144
|
-
extension.
|
145
|
-
|
145
|
+
You install Command-T by obtaining the source files and building the C
|
146
|
+
extension.
|
147
|
+
|
148
|
+
The recommended way to get the source is by using a plug-in management system.
|
149
|
+
There are several such systems available, and my preferred one is Pathogen
|
150
|
+
(https://github.com/tpope/vim-pathogen) due to its simplicity and robustness.
|
151
|
+
|
152
|
+
Other plug-in managers include:
|
153
|
+
|
154
|
+
- Vundle: https://github.com/gmarik/Vundle.vim (see |command-t-vundle|)
|
155
|
+
- NeoBundle: https://github.com/Shougo/neobundle.vim (see
|
156
|
+
|command-t-neobundle|)
|
157
|
+
- VAM: https://github.com/MarcWeber/vim-addon-manager (see |command-t-vam|)
|
158
|
+
|
159
|
+
The following sections outline how to use each of these managers to download
|
160
|
+
Command-T, and finally |command-t-compile| describes how to compile it.
|
161
|
+
|
162
|
+
*command-t-pathogen*
|
163
|
+
Obtaining the source using Pathogen ~
|
164
|
+
|
165
|
+
Pathogen is a plugin that allows you to maintain plugin installations in
|
166
|
+
separate, isolated subdirectories under the "bundle" directory in your
|
167
|
+
|'runtimepath'|. The following examples assume that you already have
|
168
|
+
Pathogen installed and configured, and that you are installing into
|
169
|
+
`~/.vim/bundle`.
|
170
|
+
|
171
|
+
If you manage your entire `~/.vim` folder using Git then you can add the
|
172
|
+
Command-T repository as a submodule:
|
173
|
+
|
174
|
+
cd ~/.vim
|
175
|
+
git submodule add git://git.wincent.com/command-t.git bundle/command-t
|
176
|
+
git submodule init
|
146
177
|
|
147
|
-
|
148
|
-
installed by opening it in Vim and then sourcing it:
|
178
|
+
Or if you just wish to do a simple clone instead of using submodules:
|
149
179
|
|
150
|
-
|
151
|
-
|
180
|
+
cd ~/.vim
|
181
|
+
git clone git://git.wincent.com/command-t.git bundle/command-t
|
152
182
|
|
153
|
-
|
154
|
-
|
183
|
+
Once you have a local copy of the repository you can update it at any time
|
184
|
+
with:
|
155
185
|
|
156
|
-
|
186
|
+
cd ~/.vim/bundle/command-t
|
187
|
+
git pull
|
157
188
|
|
158
|
-
|
159
|
-
use a typical |'runtimepath'| then the files were installed inside ~/.vim and
|
160
|
-
you can build the extension with:
|
189
|
+
Or you can switch to a specific release with:
|
161
190
|
|
162
|
-
cd ~/.vim/
|
191
|
+
cd ~/.vim/bundle/command-t
|
192
|
+
git checkout 1.10
|
193
|
+
|
194
|
+
To generate the help tags under Pathogen it is necessary to do so explicitly
|
195
|
+
from inside Vim:
|
196
|
+
|
197
|
+
:call pathogen#helptags()
|
198
|
+
|
199
|
+
For more information about Pathogen, see:
|
200
|
+
|
201
|
+
https://github.com/tpope/vim-pathogen
|
202
|
+
|
203
|
+
*command-t-vundle*
|
204
|
+
Obtaining the source using Vundle ~
|
205
|
+
|
206
|
+
Anywhere between the calls to `vundle#begin` and `vundle#end` in your
|
207
|
+
`~/.vimrc`, add a `Plugin` directive telling Vundle of your desire to use
|
208
|
+
Command-T:
|
209
|
+
|
210
|
+
call vundle#begin()
|
211
|
+
Plugin 'wincent/command-t'
|
212
|
+
call vundle#end()
|
213
|
+
|
214
|
+
To actually install the plug-in run `:PluginInstall` from inside Vim. After
|
215
|
+
this, you can proceed to compile Command-T (see |command-t-compile|).
|
216
|
+
|
217
|
+
For more information about Vundle, see:
|
218
|
+
|
219
|
+
https://github.com/gmarik/Vundle.vim
|
220
|
+
|
221
|
+
*command-t-neobundle*
|
222
|
+
Obtaining the source using NeoBundle ~
|
223
|
+
|
224
|
+
Anywhere between the calls to `neobundle#begin` and `neobundle#end` in your
|
225
|
+
`~/.vimrc`, add a `NeoBundle` directive telling NeoBundle of your desire to use
|
226
|
+
Command-T:
|
227
|
+
|
228
|
+
call neobundle#begin(expand('~/.vim/bundle/'))
|
229
|
+
NeoBundle 'wincent/command-t'
|
230
|
+
call neobundle#end()
|
231
|
+
|
232
|
+
To actually install the plug-in run `:NeoBundleInstall` from inside Vim. After
|
233
|
+
this, you can proceed to compile Command-T (see |command-t-compile|).
|
234
|
+
|
235
|
+
For more information about NeoBundle, see:
|
236
|
+
|
237
|
+
https://github.com/Shougo/neobundle.vim
|
238
|
+
*command-t-vam*
|
239
|
+
Obtaining the source using VAM ~
|
240
|
+
|
241
|
+
After the call to `vam#ActivateAddons` in your `~/.vimrc`, add Command-T to
|
242
|
+
the `VAMActivate` call:
|
243
|
+
|
244
|
+
call vam#ActivateAddons([])
|
245
|
+
VAMActivate github:wincent/command-t
|
246
|
+
|
247
|
+
After VAM has downloaded Command-T, you can proceed to compile it (see
|
248
|
+
|command-t-compile|).
|
249
|
+
|
250
|
+
For more information about VAM, see:
|
251
|
+
|
252
|
+
https://github.com/MarcWeber/vim-addon-manager
|
253
|
+
|
254
|
+
*command-t-compile*
|
255
|
+
Compiling Command-T ~
|
256
|
+
|
257
|
+
The C extension must be built, which can be done from the shell. If you use a
|
258
|
+
typical Pathogen, Vundle or NeoBundle set-up then the files were installed inside
|
259
|
+
`~/.vim/bundle/command-t`. A typical VAM installation path might be
|
260
|
+
`~/.vim/vim-addons/command-t`.
|
261
|
+
|
262
|
+
Wherever the Command-T files were installed, you can build the extension by
|
263
|
+
changing to the `ruby/command-t` subdirectory and running a couple of commands
|
264
|
+
as follows:
|
265
|
+
|
266
|
+
cd ~/.vim/bundle/command-t/ruby/command-t
|
163
267
|
ruby extconf.rb
|
164
268
|
make
|
165
269
|
|
@@ -175,7 +279,7 @@ Note: If you are on OS X Mavericks and compiling against MacVim, the default
|
|
175
279
|
system Ruby is 2.0 but MacVim still links against the older 1.8.7 Ruby that is
|
176
280
|
also bundled with the system; in this case the build command becomes:
|
177
281
|
|
178
|
-
cd ~/.vim/ruby/command-t
|
282
|
+
cd ~/.vim/bundle/command-t/ruby/command-t
|
179
283
|
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby extconf.rb
|
180
284
|
make
|
181
285
|
|
@@ -198,50 +302,6 @@ repository with:
|
|
198
302
|
|
199
303
|
su -c 'yum install vim-command-t'
|
200
304
|
|
201
|
-
MANAGING USING PATHOGEN *command-t-pathogen*
|
202
|
-
|
203
|
-
Pathogen is a plugin that allows you to maintain plugin installations in
|
204
|
-
separate, isolated subdirectories under the "bundle" directory in your
|
205
|
-
|'runtimepath'|. The following examples assume that you already have
|
206
|
-
Pathogen installed and configured, and that you are installing into
|
207
|
-
~/.vim/bundle. For more information about Pathogen, see:
|
208
|
-
|
209
|
-
http://www.vim.org/scripts/script.php?script_id=2332
|
210
|
-
|
211
|
-
If you manage your entire ~/.vim folder using Git then you can add the
|
212
|
-
Command-T repository as a submodule:
|
213
|
-
|
214
|
-
cd ~/.vim
|
215
|
-
git submodule add git://git.wincent.com/command-t.git bundle/command-t
|
216
|
-
git submodule init
|
217
|
-
|
218
|
-
Or if you just wish to do a simple clone instead of using submodules:
|
219
|
-
|
220
|
-
cd ~/.vim
|
221
|
-
git clone git://git.wincent.com/command-t.git bundle/command-t
|
222
|
-
|
223
|
-
Once you have a local copy of the repository you can update it at any time
|
224
|
-
with:
|
225
|
-
|
226
|
-
cd ~/.vim/bundle/command-t
|
227
|
-
git pull
|
228
|
-
|
229
|
-
Or you can switch to a specific release with:
|
230
|
-
|
231
|
-
cd ~/.vim/bundle/command-t
|
232
|
-
git checkout 0.8b
|
233
|
-
|
234
|
-
After installing or updating you must build the extension:
|
235
|
-
|
236
|
-
cd ~/.vim/bundle/command-t/ruby/command-t
|
237
|
-
ruby extconf.rb
|
238
|
-
make
|
239
|
-
|
240
|
-
While the Vimball installation automatically generates the help tags, under
|
241
|
-
Pathogen it is necessary to do so explicitly from inside Vim:
|
242
|
-
|
243
|
-
:call pathogen#helptags()
|
244
|
-
|
245
305
|
|
246
306
|
TROUBLE-SHOOTING *command-t-trouble-shooting*
|
247
307
|
|
@@ -358,7 +418,7 @@ The following is also available on terminals which support it:
|
|
358
418
|
<Esc> cancel (dismisses file listing)
|
359
419
|
|
360
420
|
Note that the default mappings can be overriden by setting options in your
|
361
|
-
|
421
|
+
`~/.vimrc` file (see the OPTIONS section for a full list of available options).
|
362
422
|
|
363
423
|
In addition, when the file listing has focus, typing a character will cause
|
364
424
|
the selection to jump to the first path which begins with that character.
|
@@ -424,7 +484,7 @@ By default Command-T comes with only two mappings:
|
|
424
484
|
<Leader>b bring up the Command-T buffer window
|
425
485
|
|
426
486
|
However, Command-T won't overwrite a pre-existing mapping so if you prefer
|
427
|
-
to define different mappings use lines like these in your
|
487
|
+
to define different mappings use lines like these in your `~/.vimrc`:
|
428
488
|
|
429
489
|
nnoremap <silent> <Leader>t :CommandT<CR>
|
430
490
|
nnoremap <silent> <Leader>b :CommandTBuffer<CR>
|
@@ -432,7 +492,7 @@ to define different mappings use lines like these in your ~/.vimrc:
|
|
432
492
|
Replacing "<Leader>t" or "<Leader>b" with your mapping of choice.
|
433
493
|
|
434
494
|
Note that in the case of MacVim you actually can map to Command-T (written
|
435
|
-
as <D-t> in Vim) in your
|
495
|
+
as <D-t> in Vim) in your `~/.gvimrc` file if you first unmap the existing menu
|
436
496
|
binding of Command-T to "New Tab":
|
437
497
|
|
438
498
|
if has("gui_macvim")
|
@@ -448,8 +508,8 @@ overriding the mappings are listed below under OPTIONS.
|
|
448
508
|
|
449
509
|
OPTIONS *command-t-options*
|
450
510
|
|
451
|
-
A number of options may be set in your
|
452
|
-
the plug-in. To set an option, you include a line like this in your
|
511
|
+
A number of options may be set in your `~/.vimrc` to influence the behaviour of
|
512
|
+
the plug-in. To set an option, you include a line like this in your `~/.vimrc`:
|
453
513
|
|
454
514
|
let g:CommandTMaxFiles=20000
|
455
515
|
|
@@ -566,7 +626,7 @@ Following is a list of all available options:
|
|
566
626
|
|g:CommandTScanDotDirectories| affects the behaviour at scan-time.
|
567
627
|
|
568
628
|
Note also that even with this setting off you can still use Command-T to
|
569
|
-
open files inside a "dot-directory" such as
|
629
|
+
open files inside a "dot-directory" such as `~/.vim`, but you have to use
|
570
630
|
the |:cd| command to change into that directory first. For example:
|
571
631
|
|
572
632
|
:cd ~/.vim
|
@@ -615,10 +675,78 @@ Following is a list of all available options:
|
|
615
675
|
|
616
676
|
See also |command-t-wildignore|.
|
617
677
|
|
678
|
+
*g:CommandTIgnoreCase*
|
679
|
+
|g:CommandTIgnoreCase| boolean (default: 1)
|
680
|
+
|
681
|
+
Ignore case when searching. Defaults to on, which means that searching
|
682
|
+
is case-insensitive by default. See also |g:CommandTSmartCase|.
|
683
|
+
|
684
|
+
*g:CommandTSmartCase*
|
685
|
+
|g:CommandTSmartCase| boolean (default: none)
|
686
|
+
|
687
|
+
Override the |g:CommandTIgnoreCase| setting if the search pattern
|
688
|
+
contains uppercase characters, forcing the match to be case-sensitive.
|
689
|
+
If unset (which is the default), the value of the Vim |'smartcase'|
|
690
|
+
setting will be used instead.
|
691
|
+
|
692
|
+
*g:CommandTAcceptSelectionCommand*
|
693
|
+
|g:CommandTAcceptSelectionCommand| string (default: 'e')
|
694
|
+
|
695
|
+
The Vim command that will be used to open a selection from the match
|
696
|
+
listing (via |g:CommandTAcceptSelectionMap|).
|
697
|
+
|
698
|
+
For an example of how this can be used to apply arbitrarily complex
|
699
|
+
logic, see the example in |g:CommandTAcceptSelectionTabCommand| below.
|
700
|
+
|
701
|
+
*g:CommandTAcceptSelectionTabCommand*
|
702
|
+
|g:CommandTAcceptSelectionTabCommand| string (default: 'tabe')
|
703
|
+
|
704
|
+
The Vim command that will be used to open a selection from the match
|
705
|
+
listing in a new tab (via |g:CommandTAcceptSelectionSplitMap|).
|
706
|
+
|
707
|
+
For example, this can be used to switch to an existing buffer (rather
|
708
|
+
than opening a duplicate buffer with the selection in a new tab) with
|
709
|
+
configuration such as the following:
|
710
|
+
|
711
|
+
set switchbuf=usetab
|
712
|
+
|
713
|
+
function! GotoOrOpen(...)
|
714
|
+
for file in a:000
|
715
|
+
if bufexists(file)
|
716
|
+
exec "sb " . file
|
717
|
+
else
|
718
|
+
exec "tabe " . file
|
719
|
+
endif
|
720
|
+
endfor
|
721
|
+
endfunction
|
722
|
+
|
723
|
+
command! -nargs=+ GotoOrOpen call GotoOrOpen("<args>")
|
724
|
+
|
725
|
+
let g:CommandTAcceptSelectionTabCommand = 'GotoOrOpen'
|
726
|
+
|
727
|
+
*g:CommandTAcceptSelectionSplitCommand*
|
728
|
+
|g:CommandTAcceptSelectionSplitCommand| string (default: 'sp')
|
729
|
+
|
730
|
+
The Vim command that will be used to open a selection from the match
|
731
|
+
listing in a split (via |g:CommandTAcceptSelectionVSplitMap|).
|
732
|
+
|
733
|
+
For an example of how this can be used to apply arbitrarily complex
|
734
|
+
logic, see the example in |g:CommandTAcceptSelectionTabCommand| above.
|
735
|
+
|
736
|
+
*g:CommandTAcceptSelectionVsplitCommand*
|
737
|
+
string (default: 'vs')
|
738
|
+
|g:CommandTAcceptSelectionVSplitCommand|
|
739
|
+
|
740
|
+
The Vim command that will be used to open a selection from the match
|
741
|
+
listing in a vertical split (via |g:CommandTAcceptSelectionVSplitMap|).
|
742
|
+
|
743
|
+
For an example of how this can be used to apply arbitrarily complex
|
744
|
+
logic, see the example in |g:CommandTAcceptSelectionTabCommand| above.
|
745
|
+
|
618
746
|
As well as the basic options listed above, there are a number of settings that
|
619
747
|
can be used to override the default key mappings used by Command-T. For
|
620
748
|
example, to set <C-x> as the mapping for cancelling (dismissing) the Command-T
|
621
|
-
window, you would add the following to your
|
749
|
+
window, you would add the following to your `~/.vimrc`:
|
622
750
|
|
623
751
|
let g:CommandTCancelMap='<C-x>'
|
624
752
|
|
@@ -669,6 +797,9 @@ Following is a list of all map settings and their defaults:
|
|
669
797
|
*g:CommandTClearMap*
|
670
798
|
|g:CommandTClearMap| <C-u>
|
671
799
|
|
800
|
+
*g:CommandTClearPrevWordMap*
|
801
|
+
|g:CommandTClearPrevWordMap| <C-w>
|
802
|
+
|
672
803
|
*g:CommandTRefreshMap*
|
673
804
|
|g:CommandTRefreshMap| <C-f>
|
674
805
|
|
@@ -758,7 +889,7 @@ Why doesn't the Escape key close the match listing in terminal Vim? ~
|
|
758
889
|
|
759
890
|
In some terminals such as xterm the Escape key misbehaves, so Command-T
|
760
891
|
doesn't set up a mapping for it. If you want to try using the escape key
|
761
|
-
anyway, you can add something like the following to your
|
892
|
+
anyway, you can add something like the following to your `~/.vimrc` file:
|
762
893
|
|
763
894
|
if &term =~ "xterm" || &term =~ "screen"
|
764
895
|
let g:CommandTCancelMap = ['<ESC>', '<C-c>']
|
@@ -871,7 +1002,8 @@ kind of ongoing calibration will come quite naturally.
|
|
871
1002
|
Finally, it is important to be on a relatively recent version of Command-T to
|
872
1003
|
fully benefit from the available performance enhancements:
|
873
1004
|
|
874
|
-
- version 1.
|
1005
|
+
- version 1.9 (May 2014) tweaked memoization algorithm for a 10% speed boost
|
1006
|
+
- version 1.8 (March 2014) sped up the Watchman file scanner by switching its
|
875
1007
|
communication from the JSON to the binary Watchman protocol
|
876
1008
|
- version 1.7 (February 2014) added the |g:CommandTInputDebounce| and
|
877
1009
|
|g:CommandTFileScanner| settings, along with support for the Watchman file
|
@@ -884,22 +1016,23 @@ fully benefit from the available performance enhancements:
|
|
884
1016
|
|
885
1017
|
AUTHORS *command-t-authors*
|
886
1018
|
|
887
|
-
Command-T is written and maintained by
|
1019
|
+
Command-T is written and maintained by Greg Hurrell <greg@hurrell.net>.
|
888
1020
|
Other contributors that have submitted patches include (in alphabetical
|
889
1021
|
order):
|
890
1022
|
|
891
|
-
Andy Waite
|
892
|
-
Anthony Panozzo
|
893
|
-
|
894
|
-
|
895
|
-
|
896
|
-
|
897
|
-
|
898
|
-
|
899
|
-
|
900
|
-
|
901
|
-
|
902
|
-
|
1023
|
+
Andy Waite Matthew Todd Seth Fowler
|
1024
|
+
Anthony Panozzo Mike Lundy Shlomi Fish
|
1025
|
+
Artem Nezvigin Nadav Samet Steven Moazami
|
1026
|
+
Daniel Hahler Nate Kane Sung Pae
|
1027
|
+
Felix Tjandrawibawa Nicholas Alpi Thomas Pelletier
|
1028
|
+
Gary Bernhardt Noon Silk Ton van den Heuvel
|
1029
|
+
Ivan Ukhov Ole Petter Bang Victor Hugo Borja
|
1030
|
+
Jacek Wysocki Paul Jolly Vít Ondruch
|
1031
|
+
Jeff Kreeftmeijer Pavel Sergeev Woody Peterson
|
1032
|
+
Kevin Webster Rainux Luo Yan Pritzker
|
1033
|
+
Lucas de Vries Roland Puntaier Yiding Jia
|
1034
|
+
Marcus Brito Ross Lagerwall Zak Johnson
|
1035
|
+
Marian Schubert Scott Bronson
|
903
1036
|
|
904
1037
|
As this was the first Vim plug-in I had ever written I was heavily influenced
|
905
1038
|
by the design of the LustyExplorer plug-in by Stephen Bach, which I understand
|
@@ -936,10 +1069,10 @@ per hour from the authoritative repository:
|
|
936
1069
|
Patches are welcome via the usual mechanisms (pull requests, email, posting to
|
937
1070
|
the project issue tracker etc).
|
938
1071
|
|
939
|
-
As many users choose to track Command-T using Pathogen, which often
|
940
|
-
running a version later than the last official release, the intention is
|
941
|
-
the "master" branch should be kept in a stable and reliable state as much
|
942
|
-
possible.
|
1072
|
+
As many users choose to track Command-T using Pathogen or similar, which often
|
1073
|
+
means running a version later than the last official release, the intention is
|
1074
|
+
that the "master" branch should be kept in a stable and reliable state as much
|
1075
|
+
as possible.
|
943
1076
|
|
944
1077
|
Riskier changes are first cooked on the "next" branch for a period before
|
945
1078
|
being merged into master. You can track this branch if you're feeling wild and
|
@@ -966,18 +1099,9 @@ Bug reports should be submitted to the issue tracker at:
|
|
966
1099
|
https://wincent.com/issues
|
967
1100
|
|
968
1101
|
|
969
|
-
DONATIONS *command-t-donations*
|
970
|
-
|
971
|
-
Command-T itself is free software released under the terms of the BSD license.
|
972
|
-
If you would like to support further development you can make a donation via
|
973
|
-
PayPal to win@wincent.com:
|
974
|
-
|
975
|
-
https://wincent.com/products/command-t/donations
|
976
|
-
|
977
|
-
|
978
1102
|
LICENSE *command-t-license*
|
979
1103
|
|
980
|
-
Copyright 2010-2014
|
1104
|
+
Copyright 2010-2014 Greg Hurrell. All rights reserved.
|
981
1105
|
|
982
1106
|
Redistribution and use in source and binary forms, with or without
|
983
1107
|
modification, are permitted provided that the following conditions are met:
|
@@ -1002,6 +1126,22 @@ POSSIBILITY OF SUCH DAMAGE.
|
|
1002
1126
|
|
1003
1127
|
HISTORY *command-t-history*
|
1004
1128
|
|
1129
|
+
1.10 (15 July 2014)
|
1130
|
+
|
1131
|
+
- improve tag finder performance by caching tag lists (patch from Artem
|
1132
|
+
Nezvigin)
|
1133
|
+
- consider the |'autowriteall'| option when deciding whether to open a file in
|
1134
|
+
a split
|
1135
|
+
- make selection acceptance commands configurable (patch from Ole Petter Bang)
|
1136
|
+
- add <C-w> mapping to delete previous word of the match prompt (patch from
|
1137
|
+
Kevin Webster)
|
1138
|
+
- try harder to always clear status line after closing the match listing
|
1139
|
+
(patch from Ton van den Heuvel)
|
1140
|
+
- don't allow MRU autocommands to produce errors when the extension has not
|
1141
|
+
been compiled
|
1142
|
+
- add |g:CommandTIgnoreCase| and |g:CommandTSmartCase| options, providing
|
1143
|
+
support for case-sensitive matching (based on patch from Jacek Wysocki)
|
1144
|
+
|
1005
1145
|
1.9.1 (30 May 2014)
|
1006
1146
|
|
1007
1147
|
- include the file in the release vimball archive that was missing from the
|