On 11 April 2015 at 12:27, weaselcat via Digitalmars-d <[email protected]> wrote: > On Saturday, 11 April 2015 at 10:00:45 UTC, Iain Buclaw wrote: >> >> On 10 April 2015 at 21:19, Adam D. Ruppe via Digitalmars-d >> <[email protected]> wrote: >>> >>> On Friday, 10 April 2015 at 19:08:13 UTC, Paulo Pinto wrote: >>>> >>>> >>>> - Move a method to another class located in another module, while >>>> updating >>>> all references to it, including module imports in the new file >>> >>> >>> >>> Cut the text out of one file, paste it in the new one, compile and fix >>> what >>> the compiler complains about. >>> >>> ...ditto for the others. >>> >>> >>> I admit this takes a few more minutes than an automatic ide thing might, >>> but >>> it isn't that big of a bother to me because the compiler errors combined >>> with vim's "repeat last command" hotkey makes it fairly quick and >>> painless. >>> When I run make from inside vim, it jumps to the file and line the >>> compiler >>> spits out, so I can do a quick "cwnewname" then f4 (my hotkey to go to >>> the >>> next error) and ., repeat until done. >> >> >> Anyone use abbreviations in vim? >> >> One thing that I want to do at some point in time is remap K to goto >> the documentation of a function/method. >> >> Iain. > > > if you're using vim-dutyl you could just remap K to :DUjump or one of the > split variants. > (DUddoc also shows the documentation of the symbol under your cursor.)
No one announced (to me) it's existence. Thanks! I'll be sure to check it out.
