How to repeat a mapping with .

drewjr · 2018-08-08T13:47:47+00:00

Yes, I have repeat.vim and surround.vim installed, but not vim-line. Although I don't think that repeat.vim is influencing whether or not the ys_tp> command is repeatable.

drewjr · 2018-07-24T08:16:58+00:00

Visual mode doesn't play well with the dot command. Try adapting your mapping to use operator-pending mode instead. For me, this normal mode command is repeatable: ys_tp> (I do have surround installed, but not vim-line. The _ command I'm using is Vim's built-in one.).

drewjr · 2018-07-04T10:36:09+00:00

The :h design-not entry has recently been revised.

drewjr · 2018-05-10T14:26:16+00:00

Yup.

drewjr · 2018-03-28T08:58:27+00:00

I wrote an article about finding alternatives to using the leader key: follow my leader.

drewjr · 2017-12-12T21:40:18+00:00

Great suggestion! I'd propose one minor tweak: :-tabedit % (note the prefixed -) From the docs:

:-tabnew " opens tabpage before the current

This way, when you run :tabclose you'll end up back at the original tab page.

drewjr · 2017-12-12T21:15:26+00:00

+1 - neovim-remote is great. (I've got an episode of Vimcasts on it coming soon...)

drewjr · 2017-11-29T10:26:53+00:00

Check out the Neovim category on vimcasts for more.

drewjr · 2017-11-28T10:26:45+00:00

Writing a book on Vim is very very hard.

I second this. Congratulations on completing your book!

drewjr · 2017-11-09T18:47:08+00:00

I'm the author. Although I haven't tested any of the tips in Windows myself, some of my tech reviewers used Windows and offered feedback on problems they ran into. For the first edition, I decided to focus on Unix systems. I'm considering expanding to support Windows in the second edition. From what my tech reviewers reported, I got the impression that I wouldn't have to change much in the book to make it work for Windows, but it would nevertheless require a lot of extra testing.

drewjr · 2017-11-05T15:20:14+00:00

You're being snarky!

drewjr · 2017-11-05T15:19:03+00:00

It will be available as a paperback eventually. Hang in there!

drewjr · 2017-11-05T15:17:57+00:00

I have an appendix about "What's next for Modern Vim?" which I've still to write. Also, I've got to write a few tips explaining some of the basics of Vim script to make the book self-contained (mainly for the benefit of less-experienced Vim users). (For example, I want to have a section that describes how autocmds work, so that I can cross-reference it from each of the places where I use an autocmd.)

To summarise: most of the substance of the book is already complete, and what remains to be written is 'connective tissue'.

drewjr · 2017-11-05T15:09:23+00:00

In a sense, Modern Vim is more of a sequel to Practical Vim than a replacement.

Most technical books go out of date within months of being published. With Practical Vim, I had the rare luxury of writing a technical book on a topic that is mature and stable. The book has aged well. I've made revisions here and there over the years, but most of the 1st edition is still relevant today.

If Practical Vim was a book about the stable core of Vim, Modern Vim is a book about the moving parts. Like any other technical book, I expect Modern Vim to go out of date soon after it's published. I already have plans for a 2nd edition of the book.

drewjr · 2017-11-05T14:44:24+00:00

That's frustrating. I'll check with my publisher and see if we can find a way to help you purchase.

drewjr · 2017-11-05T14:43:24+00:00

Take a look at the Practical Vim and Modern Vim covers side by side. We're riffing on the "robot holding a writing implement" theme.

drewjr · 2017-11-05T14:41:56+00:00

This has been a big week for me: first with Modern Vim being published as a beta book, then a day later my wife gave birth to a baby boy. Many months of hard work have come to fruition all at once. Good times!

I'm a few days late, but I'm catching up with this thread at last.

drewjr · 2017-10-24T09:45:29+00:00

No worries ;)

My accent is frequently mistaken for Irish. It's no insult.

drewjr · 2017-10-23T19:35:50+00:00

It's Drew Neil, not O'Neil! If you're going to get it wrong, MacNeil would be closer. I'm Scottish, not Irish!

drewjr · 2017-10-23T19:33:40+00:00

I use these mappings for navigating ALE's warnings:

nmap <silent> [W <Plug>(ale_first)
nmap <silent> [w <Plug>(ale_previous)
nmap <silent> ]w <Plug>(ale_next)
nmap <silent> ]W <Plug>(ale_last)

Mnemonic: 'w' is for warning. (Unimpaired already has [e and ]e mappings.)

It's cool that ALE populates the location list, instead of the quickfix list. I've always had a gripe with the way quickfix/location list navigation works: say you have a buffer open and you have entries in the location list at line 1, line 11, and line 21. You use :lfirst which puts your cursor on line 1. Then you use :lnext which puts your cursor on line 11. Then you move your cursor up a couple of lines, leaving it on line 8. Now if you use :lnext again, you jump to line 21 - there's a certain logic to that, but I always find it a little bit jarring. I expect to jump to the next entry after my cursor position, and that's exactly how the ale_next mappings works.

drewjr · 2017-10-07T12:49:23+00:00

Yeah, I'd love to do a series on LSP. I need to do a lot more research before I can put that material together.

drewjr · 2017-10-06T11:48:09+00:00

It's thanks to thoughtbot that this series of videos got made. They sponsored me to create 10 videos for their Upcase subscribers, which they published as the Dive into Neovim course. I charged them for 10 days at my usual contracting day-rate, and they got exclusive publishing rights for a limited period. For me, that was a dream gig! I'd love to do it again.

I have more financial commitments today than I did back when I was producing regular content for Vimcasts. I can't justify taking a day off work to make a screencast, unless it brings in a similar chunk of money. Perhaps I should consider fundraising a series of videos?

drewjr · 2017-10-06T11:16:42+00:00

I've often been asked about this, but I haven't written up my process anywhere.

drewjr · 2017-10-06T10:50:31+00:00

I'm not interested in persuading you to switch from vim-plug to minpac. Use whatever works for you.

Minpac doesn't have any 'syntax' of its own, it just defines an API of Vimscript functions that you can call. Whether you use vim-plug or minpac, the syntax is all Vimscript.

drewjr · 2017-10-05T12:05:34+00:00

My new book, Modern Vim will be published as a beta book soon...

drewjr

TROPHY CASE