1. 34
  1. 3

    The items in the “general” section should be caught by linters. But overall this is a good list because it’s terse, and thus usable. If it grows into a giant FAQ or guide then it will be ignored as usual :)

    Actually, this post should be in :help.

    More generally, I wish that @sjl accepted PRs or at least corrections for http://learnvimscriptthehardway.stevelosh.com/ , so that the community could continue to iterate on it. Instead of continuing the sprawl of random tutorials/guides/vim-101 blogs.

    1. 2

      If it grows into a giant FAQ or guide then it will be ignored as usual :)

      This post was inspired by Effective Go, which is exactly the sort of “giant guide” that you mention, but I still think it has value because it’s quite detailed and in-depth (you can almost learn most of Go from just this guide alone). I think both approaches have value; I opted for a more concise post because I’m lazy and wanted to actually finish this in 2019, and not 2023 or whatever because:

      $ ls -l ~/arp242.net/_drafts/*.markdown | wc -l
      233
      
      1. 1

        This post was inspired by Effective Go, which is exactly the sort of “giant guide” that you mention

        For long-form it would make more sense to iterate on http://learnvimscriptthehardway.stevelosh.com .

        1. 1

          Learn VimScript The Hard Way is great, and I regularly refer people to it, but it’s also written in a certain format that doesn’t work well for everyone. I don’t think it should be the only resource for all things VimScript related.