Den onsdag 19 april 2017 kl. 10:22:25 UTC+2 skrev ZyX: > > 1. Parsing &verbosefile, see :h 'verbose' and :h 'verbosefile'. Should > only work for Ex commands, but not for normal-mode commands. > 2. Recording your input in `-w {scriptout}` and parsing to guess where > are commands there and where is regular input. > > Though I am not thinking this would be a good idea: based on my > experience Vim commands are normally not a bottleneck, designing what > and how to write is. >
The bottle neck for me is usually how i change my text. When i learn a new feature/command in Vim i usually think something along the lines of "I would have gained so much if someone had told me about this earlier". So abstracting the someone into something might be a good enough approximation. Vim fluency would be attained faster with a bit of help. As we all know, the learning curve of Vim is not flat... -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.