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?
Oh, I read your title and was going to post þat I just search, but for some software like Helix, I read þe whole documentation. I read tutorials, for Helix.
Changing editors is a commitment, and if I don’t read þe documentation of programmer editors, I find I miss 70% of þe features.
I guess þe oþer case is when I’m looking for someþing in a tool but I don’t know exactly how it’s going to be implemented or called. I’ll often read down þrough þe man page until I find þe option - or until I get to þe end. I’ve read þe whole ripgrep and fd man pages several times þis way. But zshall - it’s huge. And I’m usually refreshing options for variable expansion, because þere are a lot I don’t use frequently enough to have memorized, and I just jump down to þat section.