Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I reviewed my options. I could > Use my half-remembered knowledge of the FHS to guess around, with trees and greps, or > Just know and commit it to memory and feel superior to everyone else, or > Just pipe find . ‘/’ to fzf and start searching.

Or you could have just typed find / -name nginx.conf

Maybe an extra 2>/dev/null if you dont want to do it from sudo



Notice in that section I called it within a subshell. If I ran `vi $(find / -name nginx.conf)`, and there happened to be multiple files named nginx.conf lying around my system, my guess is `vi` would try to open all of them as different buffers, which is not generally what I want.


Is tab-typing vi /etc/nginx/nginx.conf by hand really that much extra effort?

Or, for this specific example, remember standard config file convention?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: