And I said that the man pages would be a part of what you have to examine. 95 pages in the case of bash (that's after running it through troff). man pages were fine when they were three pages long, but their lack of any internal index has become a problem.
Ok, now you might have a dozen files which could contain the information, where the location of each file can be modified by environment variables. It's tolerable if you are working on something you change weekly, but a practical problem if you do it yearly or it's entirely new.
'man bash'. Type G. Press PgUp until you see the FILES heading (took one press for my terminal size). There's your list of files. Alternatively, instead of G and PgUp, type /FILES<Enter>.
Of course, this doesn't help at all when software either doesn't have manpages, or doesn't include the list of files in the manpage. Just nitpicking your bash example.
This is HN, not Reddit. You can safely assume that every single person here knows how to use man, particularly if they mention using troff to format it properly. There remains a problem.
I truly wasn't sure if they were aware of man's search and go to options, as they brought up 95 pages as being why it was hard to find configuration file locations for bash.
When I'm searching for configuration file location, I do use '/FILES' or PgUp from the bottom of the manpage, so the length of the manpages is irrelevant.
Ya'll got social media? Wish I had friends to talk to -- I'm starting to think the Dead Internet Theory has some weight to it.
I cannot find a place to talk to like-minded people anymore; it's all gamified to sell you something. All folks do on Reddit is talk at you. I'm starting to doubt half the people posting are actual people now... with so many comments that are perfectly formatted and phrased like ChatGPT.
I kind of solved it with epubs and sending it to my TV screen.. lean back like watching TV and set the font size to a comfortable size and tap arrow right on a wireless kb.
I had a similar very tiny-scale problem that was solved much quicker by awk+perl. I had a relatively large dataset across many YAML files that I needed to compute a result. Turns out that using yq / jq to performn a query was much (order of magnitudes) slower (>10m) to compute any kind of result. Outputting the data into CSV, then iterating over that was much, much faster (seconds). Of course, dumping it into SQlite and querying that was nearly instantaneous.
I know it’s not a direct 1:1 comparison, but it brings to mind that solutions that were made common decades ago are still relevant today.
I see 2FA is often misunderstood by people. The basic premise with 2FA is that you combine “something you know” with “something you have”.
You are already part of the 2FA — you’re the first factor: “something you know”.
The second factor: “something you have” — often a personal device, or an object. This is ideally something no one else can be in possession of at the same time as you are.
Except that for 99% of my passwords, I am 100% sure I do not, and never will, know them, they are 60-100+ bytes of random data, only known by my passwordmanager.
The only thing I know, is the passphrase for my passwordmanager. TOTP codes are also stored in there, but I see it more as a replay-protection for captured passwords, though this is also really a non-issue in this time of almost no plaintext protocols.
reply