I’ve been switching from Vim to Helix recently. I did the built-in tutor, and whenever I need to configure something, I look it up in the docs. The problem is, I only find what I already know to look for. Without reading the documentation more broadly, I don’t really know what I can configure in the first place.

So I’m curious, do you sit down and read documentation to understand a tool, or do you just search it when you hit a specific problem?

  • aev_software@programming.dev
    link
    fedilink
    arrow-up
    2
    ·
    12 hours ago

    I love documentation if it’s written well and if it’s helpful.

    I can’t say I find vim’s documentation meeting either of those criteria.

    So I reach out to other sources who figured things out and regurgitate their experiences in ways that fit how my brain likes to consume them.