57
Do you actually read documentation, or just search it when you’re stuck?
(programming.dev)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
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.