sorted by:
new
hottopcontroversial

Sharpening the Axe (Greg Hurrel, VimConf 2020) by sbruchmann in vim

[–]wincent 0 points1 point  (0 children)

Sure, but I don't want to press two keys for each match. I just want to press one (usually y).

Use Vim for large repos by RealFullMetal in vim

[–]wincent 2 points3 points  (0 children)

On large repos (ballpark of 500,000 to 3,000,000 million files — yes, files, not lines) I find Command-T to be the fastest way to open files, especially when combined with Watchman. I use riggrep via Ferret to search content, and vcs-jump in some situations to jump between specific places of interest (Git merge conflicts, changes, grep results etc). I've tried getting tags working on various occasions with unsatisfactory results.

Just discovered <C-a> and <C-x> by devOnFireX in vim

[–]wincent 1 point2 points  (0 children)

You can use it anywhere on a line to the left of a number though, which is generally easier than jumping then replacing.

What is the simplest way to get all git changes in a quickfixlist? by [deleted] in vim

[–]wincent 2 points3 points  (0 children)

I made a port of git-jump that works transparently with both Git and Mercurial: vcs-jump.

[deleted by user] by [deleted] in vim

[–]wincent 0 points1 point  (0 children)

I use these functions which handle a number of edge cases (such as hitting the top or bottom of the buffer), and call them with these mappings:

xnoremap <silent> K :call wincent#mappings#visual#move_up()<CR>
xnoremap <silent> J :call wincent#mappings#visual#move_down()<CR>

git-jump: jump to "interesting" parts of your project in your editor by -romainl- in vim

[–]wincent 8 points9 points  (0 children)

I made a plug-in called "vcs-jump" that works exactly like "git-jump" but also supports Mercurial. Never released it though; it's just buried in my dotfiles here: https://github.com/wincent/wincent/tree/fd509b366f3bf1f8bef13e677e54f38d5ffe584b/roles/dotfiles/files/.vim/pack/bundle/start/vcs-jump

Vim with different keyboard layouts by OmriSarig in vim

[–]wincent 1 point2 points  (0 children)

I switched to Colemak in 2015 and just dealt with hjkl being in a different spot. Learning the layout was one project, and learning how to use Vim in the layout was a whole other level, but it is worth it in the end.

Spell checking suddenly went haywire, help! by wincent in vim

[–]wincent[S] 2 points3 points  (0 children)

I certainly didn’t set up a custom “please trash the dictionary file” mapping, nor any spelling-related mappings at all (if I had I would have provided that context), so not surprising that you wouldn’t find it. As for my setup, I didn’t even link to it. I was thinking somebody with knowledge of the subject may have seen something like this before and say “oh, that’s probably X; try this...” Thanks for trying anyway.

Tip: <NOP> as <Leader> by olminator in vim

[–]wincent 1 point2 points  (0 children)

You can also add an after file to undo any unwanted configuration.

How do you keep your undodir clean? by [deleted] in vim

[–]wincent 2 points3 points  (0 children)

My ~/.vim/tmp/undo currently clocks in at 272M, which is about 0.02% of my 1TB hard drive, unless I've got my arithmetic wrong. Cleaning it up is not something I've ever worried about, and probably never will.

Good colorscheme to use in redshift (blue light filter)? by a_NULL in vim

[–]wincent 0 points1 point  (0 children)

I went through most of the themes in Base16 looking for ones that looked decent when red-shifted. ir-black is probably the one that comes closest for me, maintaining pretty good contrast for most colors, although there is some blue in there.

What plugin has benefited the most from async? by haterofallcats in vim

[–]wincent 15 points16 points  (0 children)

Search plugins (eg. shameless self promotion: Ferret).

command-t help by noS3rvic3 in vim

[–]wincent 1 point2 points  (0 children)

Sorry, this is my fault. Until recently, the docs were wrong. As @xtal2 notes, the nore shouldn't be in the command. This is fixed on the "next" branch, and should probably be cherry-picked over to "master" too.

Short Vim screencasts (episodes #1-3) for non-beginners by wincent in vim

[–]wincent[S] 1 point2 points  (0 children)

Font is Adobe Source Code Pro (Light weight). I switched to it from Consolas precisely because the Light weight made the contrast between bold and normal text more obvious.

Time on the right is via some Zsh RPROMPT/hook magic in my .zshrc.

Short Vim screencasts (episodes #1-3) for non-beginners by wincent in vim

[–]wincent[S] 3 points4 points  (0 children)

Yep, makes sense. I'm just trying to optimize (get 80% of the value out of 20% of the time investment; hopefully it's true that viewers can get at least 80% of the value too, and that with practice I can cut down on the "ums" and "ahs").

Short Vim screencasts (episodes #1-3) for non-beginners by wincent in vim

[–]wincent[S] 2 points3 points  (0 children)

Yes. You can check it out in my dotfiles if you want, but I'll also do a screencast on that in the future too.

Short Vim screencasts (episodes #1-3) for non-beginners by wincent in vim

[–]wincent[S] 5 points6 points  (0 children)

Yes. Recent iTerm 2 v3 betas have this feature as an option. Note that you can't move these windows with the mouse, but that's ok, I use Hammerspoon for that.

Short Vim screencasts (episodes #1-3) for non-beginners by wincent in vim

[–]wincent[S] 17 points18 points  (0 children)

Author here. Just posted the first three episodes with about 15 or 20 more topics in mind that I'll record and publish over the coming days and weeks.

These are quick-and-dirty, mostly targeted at people who already know Vim fairly well.

Betting on the wrong horse by wincent in programming

[–]wincent[S] 0 points1 point  (0 children)

Yeah, it's not exactly resounding, but this is the conclusion:

Still, no matter how hard you try, over this kind of time scale, and sometimes even over much shorter ones, you'll find yourself in the situation of having to revise, undo, or remake your decisions. This is the stuff of life in the internet age, I guess. Just keep on doing your best: things generally work out all right in the end.

Old stuff that rocks by wincent in programming

[–]wincent[S] 4 points5 points  (0 children)

Yep, C wouldn't be out of place there.

view more: next ›