Go through the steps you have to take for every piece of code you write,
and create scripts to do as much as possible automatically.
You have to open a file in Vim, give it a name that is not already in use,
put in some boilerplate, (#! line, description of the code's purpose, &c,
depending on language and code type, and make it executable. All that can
be done with skeleton files and shell or Vim scripts. Keeping code under a
source control program, (e.g Git) can be automated in the same way.
Think about what you're doing, then how to get the computer to do it gor
you. Don't expect to get it right first rimw. Build up step by step, and
be prepared to scrap and start over. Just don't let the pleasure of
plating with the tools divert you from producing code useful for others.
If you want to see what can be done, watch Damian Conway's videos, e.g.
https://www.youtube.com/watch?v=oka4wcsrg0c where he uses Vim for
everything, including the presentation tool. Just don't expect tp attain a
similar level of proficiency for a decade or so.
--
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/6f13b3f60f5f0e20c1cb9a85be16405c.squirrel%40webmail.vybenetworks.com.
No comments:
Post a Comment