| Age | Commit message (Collapse) | Author |
|---|
|
Adding the plugin for real. It's been indispensable for code review.
|
|
Easily complete email addresses from the Mutt aliases file when
composing an email message.
|
|
Shows code context including the enclosing function, class, namespace,
etc.
|
|
Make Common Lisp development more fluid.
|
|
I've been using this locally on one machine since I finished writing the
plugin, but apparently forgot to add it to my .vim.
|
|
Use Vlime instead of Slimv for a Common Lisp environment.
|
|
Haven't been using this plugin. Recently started a Common Lisp project,
but am going to use Vlime instead, which seems to integrate better with
user configuration.
|
|
|
|
The JavaScript plugin I'm using does an okay job syntax highlighting
TypeScript, but some identifiers don't get highlighted.
Now that I'm doing a project in TypeScript, it's nice to have everything
highlighted correctly.
|
|
Makes it easier to reformat plain text tables.
|
|
Make it easier to write with typographers' quotes.
Depends on 'vim-textobj-user'.
|
|
|
|
|
|
|
|
Now that I'm going to be doing more Go development, switch to the full
featured Vim Go plugin.
|
|
Switching to 'vim-go'.
|
|
For Courier Maildrop `.mailfilter` syntax highlighting. Makes it a bit
more pleasant to edit my new work email filters.
|
|
Makes switching to alternate files much more efficient. Will be using
this for Objective-C implementation and header files, but it could be
useful in other contexts, even outside the C realm.
|
|
|
|
Syntax highlighting for DomeKey mapping files.
|
|
Provides a `:TabsGrep` command that enables `:tabs` output to be
filtered, making it easier to find out which tab a file is on.
|
|
Facilitates opening Rails locale files in alternate languages.
|
|
Provides completion of Git SHAs in commit messages. Super handy for
referencing other commits without having to copy-paste and use the
mouse. Was getting tired of that routine.
|
|
Was getting annoyed at having to manually split function arguments from
a single line to multiple lines. Planned on writing a little custom
plugin to do this, but this one seems more well thought out and
featureful than what I was thinking of. It also seems lighter and not as
presumptive as another alternative I found:
https://github.com/AndrewRadev/splitjoin.vim
|
|
Finally getting annoyed enough about not being able to '.'-repeat
surround.vim commands. It's really nice to have repeating just work now.
|
|
Make it more efficient to run RSpec tests right in Vim. It's been nearly
4 weeks since I started writing Rails code full time and I'd like to see
if I can have a nicer system for running only the tests I'm interested
in or working on at the moment.
|
|
This plugin has been sitting uncommitted in my .vim for many months now.
I originally hadn't added it to the repo because it wasn't published.
Now that it is, I can use the plugin's public Git link.
Helps me keep track of my to-dos.
|
|
This plugin has been in my `bundle/` directory for nearly a year
uncommitted. I think it's about time we formally inducted it, and made
my game an official part of my vimrc.
|
|
I've had the plugin disabled but uncommitted for many months now. I
think it's finally time to make the change official.
Slimv is an excellent plugin, and makes it possible to have a good Common
Lisp development environment in Vim. I'll still be using it for that
reason.
The trouble is that Slimv isn't a good plugin citizen: It overrides user
defaults. I noticed that at some point many months ago, code I was
writing was getting auto-indented. The "smart" kind of autoindent, not
`set autoindent`. I _hate_ "smart" auto-indenting. Figured out that
Slimv was the cause and immediately disabled the plugin.
We may want to create a Bash alias that we can use exclusively for CL
development that loads Slimv into the runtimepath instead of having it
auto-loaded by Pathogen.
|
|
The Rust language's Vim plugin.
|
|
Git was complaining that the tree was dirty with the `doc/tags` file.
Just ignore untracked files.
|
|
Working Emacs with Evil-mode and SLIME felt pretty slow compared to my
normal Vim speed. Trying Slimv to see if I can make it work for Common
Lisp development in Vim.
|
|
To facilitate Vim plugin development.
|
|
This will finally give me a way to repeat `G` commands. Should be useful
since I often find myself entering a `G` command only to realise that I
was in the wrong window and have to then type the whole thing again.
With this plugin all I have to do is type a quick mapping to make the
repeat happen.
|
|
Testing this plugin out. The hope is that it will allow me to quickly
open the relevant bits of code from a stack trace. This also works
without a `makeprg` so I could use if for Django stack traces for
example. Still trying to get it to work.
|
|
Big thanks to Chris Toomey for creating this plugin. Something I was
trying to achieve using my v_<leader>c mapping but which never felt
right, especially since that only ever allowed me linewise copies and no
characterwise ones.
Found out about this one at the Boston Vim meetup back on May 20 (or
maybe rediscovered, as it sounded familiar but I obviously never pursued
it).
This is something I've been wanting for a long while, as my own mapping
for it worked fine but wasn't the most ideal.
|
|
I absolutely love Command-T, and it's served me so well over the last
year and a few months. Its native Ruby C extension makes it super fast,
much faster than CtrlP.
That said, it can take 2-3 seconds to initialise if its cache is empty,
so when I start a new Vim instance or clear Command-T's cache after
adding or removing files or switching to a git branch that's very
different, I have to wait for it to do its thing.
This initialisation time really got on my nerves last week when I
constantly had to clear Command-T's cache for some reason in order for
it to list the files I was looking for, resulting in more waiting than I
would have liked.
Because of this, I went looking around at other options to test their
speed. I've settled on Thoughtbot's pick(1) after testing out different
fuzzy finder plugins.
|
|
My primary use case for Unite was as a potential replacement for
Command-T. It's pretty cool, but since it operated at about the same
speed as CtrlP on my large work project, I'm afraid I'm going to remove
it in favour of pick.
|
|
Even with ag, ctrlp has been much too slow in my huge work project.
Ctrlp actions consistenty take seconds to complete there. Settling on
pick as my new fuzzy finder.
|
|
Trying out the pick(1) fuzzy finder from Thoughtbot. Seeing how fast it
is out of the gate.
|
|
Testing out CtrlP as a Command-T alternative at the same time as
Unite.vim. Figure I might as well try all of these to see which one I
end up liking most.
|
|
Curious about other Command-T options because it's been feeling a bit
slow lately. Testing out Unite.vim to see if it might work for me.
|
|
Use the remote URL instead of a local path.
|
|
I've been using Netrw more and more after
9ec85f7fa5e118c0630e6b6457b71e80e57fa5dd. I think I'm going to switch
over and leave NERD Tree now. Haven't really been using it for anything
other than showing multiple directory levels of a project in a single
view, which I now know is something Netrw can do. Also I mostly use
Command-T opening files so haven't been using the plugin much lately.
|
|
No longer using this one. I've been using ag exclusively, mostly
directly from the console but sometimes using the plugin. For find and
replace I've gotten more adept at using the arglist, so I haven't used
EasyGrep in a long time. It can also be kind of slow, mostly because it
doesn't use ag. Not sure if there's a way to integrate the two.
|
|
So I can grep my open buffers.
|
|
|
|
Was doing a search for a class in HTML files and realised that I want
the files open in vim and in order to do so I would either have to
monkey with some shell piping or Control-Z/fg back and forth from ag
output to vim whilst remembering which filenames I wanted to open and
open them manually.
Craziness.
Finally installing Ag.vim for these instances when I want to instantly
open vim buffers for the files in my search results.
|
|
Tried tcomment which is able to recognise the code and apply the
appropriate comment instead of blindly using the comment format
specified for the current file type. Removing commentary.vim as part of
the switchover.
|
|
Trying it out to see how it compares to commentary.vim. Getting annoyed
that commentary.vim doesn't know to use JavaScript comments for a script
embedded in HTML.
|
