Shakedown Social

Mark T. Tomczak(Possibly relevant to <a href="https://social.jvns.ca/@b0rk" class="u-url mention" rel="nofollow noopener" target="_blank">@b0rk</a> 's interests)So I hit a flag in diff, <code>--unchanged-group-format</code>. It does not show up in the manpage. It does not show up in --help. You can search both those channels for that string and you will not find it.You know where it shows up first? If you Google it, you'll get an example in <a href="https://www.gnu.org/software/diffutils/manual/html_node/Line-Group-Formats.html" rel="nofollow noopener" translate="no" target="_blank">https://www.gnu.org/software/diffutils/manual/html_node/Line-Group-Formats.html</a>.So why doesn't it show up in the manpage? Well, it does! If you read the entire manpage. With your eyes.<pre><code> -D, --ifdef=NAME output merged file with '#ifdef NAME' diffs --GTYPE-group-format=GFMT format GTYPE input groups with GFMT --line-format=LFMT format all input lines with LFMT --LTYPE-line-format=LFMT format LTYPE input lines with LFMT These format options provide fine-grained control over the output of diff, generalizing -D/--ifdef. LTYPE is 'old', 'new', or 'unchanged'. GTYPE is LTYPE or 'changed'. </code></pre>"What do you mean it isn't documented? Of course it's documented. You did read every line and do some template-substitution in your brain, didn't you?"This isn't advocating for not reading the manpage. If you really want to understand how the tool works, you read the whole manpage. And probably the source code. 😉 ... but I don't want to understand how the tool works. I want to diff two files and not have the lines that are the same get emitted.And I think a lot of application- and solution-generating computer people, most of the time, in most of their careers, are operating on that level of depth. Problems come in too fast and with too much variety. You absolutely go deep on some things. There is no time to go deep on everything.So how do we address this (other than throw up our hands and say "Relying on Google's fuzzy search of the whole Internet and vibe-coding LLMs is the future actually")? I don't have magic bullets, but a "fuzzy search" mode in something like <code>less</code> that could take an input like <code>--unchanged-group-format</code> and twig that it if there's no exact match, it might be related to <code>--GTYPE-group-format</code> would be nice.Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)<a href="https://mastodon.fixermark.com/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://mastodon.fixermark.com/tags/manpage" class="mention hashtag" rel="nofollow noopener" target="_blank">#manpage</a> <a href="https://mastodon.fixermark.com/tags/less" class="mention hashtag" rel="nofollow noopener" target="_blank">#less</a>

gary<a href="https://bsd.network/@lattera" class="u-url mention" rel="nofollow noopener" target="_blank">@lattera</a> every line of code and new algo or what have you can have provenance and confidence rating as well as tell you exactly what is happening - all the metadata, they have the resources to own and they do interdiction and camp out for years <a href="https://infosec.exchange/tags/manpage" class="mention hashtag" rel="nofollow noopener" target="_blank">#manpage</a> <a href="https://infosec.exchange/tags/tldp" class="mention hashtag" rel="nofollow noopener" target="_blank">#tldp</a> <a href="https://infosec.exchange/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#documentation</a> <a href="https://infosec.exchange/tags/metadata" class="mention hashtag" rel="nofollow noopener" target="_blank">#metadata</a> <a href="https://infosec.exchange/tags/katie" class="mention hashtag" rel="nofollow noopener" target="_blank">#katie</a> sstam <a href="https://infosec.exchange/tags/ft" class="mention hashtag" rel="nofollow noopener" target="_blank">#ft</a> meade

OSTechNixHow To Efficiently Search Linux Manual Pages with the man -k Command <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://floss.social/tags/Manualpages" class="mention hashtag" rel="nofollow noopener" target="_blank">#Manualpages</a> <a href="https://floss.social/tags/Manpage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Manpage</a> <a href="https://floss.social/tags/Linuxcommands" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxcommands</a> <a href="https://floss.social/tags/Linuxbasics" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxbasics</a> <a href="https://floss.social/tags/Linuxtips" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linuxtips</a> <a href="https://ostechnix.com/search-linux-manual-pages/" rel="nofollow noopener" translate="no" target="_blank">https://ostechnix.com/search-linux-manual-pages/</a>

John Carlsen 🇺🇸🇳🇱🇪🇺<a href="https://social.v.st/@holly" class="u-url mention" rel="nofollow noopener" target="_blank">@holly</a> I haven't tested <a href="https://sfba.social/tags/DuckDuckGo" class="mention hashtag" rel="nofollow noopener" target="_blank">#DuckDuckGo</a> with it yet, but the other day I was pleasantly surprised when I asked <a href="https://sfba.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> for a <a href="https://sfba.social/tags/manPage" class="mention hashtag" rel="nofollow noopener" target="_blank">#manPage</a> .

Recent searches

Search options

Administered by:

Server stats:

#manpage