> well, vi (and ergo vim) keystrokes are > https://en.wikipedia.org/wiki/Turing_completeness (also see > https://stackoverflow.com/questions/7284/what-is-turing-complete ). As a > result, finding the minimal user input that yields a buffer with the input > falls under https://en.wikipedia.org/wiki/Code_golf
This kind of competition is not relevant to what I am not talking about. One has to spend extra effort to come up with the absolute shortest code. That effort must be considered into the cost as well. What I am talking about is "cost", which ultimately map to all programmer's time involved in typing and thinking about what to type. (But not include thinking about algorithm, data structure, etc.) > or perhaps > https://en.wikipedia.org/wiki/Kolmogorov_complexity . Also see > http://www.vimgolf.com/ for vim golf. -- Regards, Peng -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
