Ubuntu 24.04 LTS: Forgot Package Name for Graphical Manpage Viewer #manpage
(Possibly relevant to @b0rk 's interests)
So I hit a flag in diff, --unchanged-group-format. 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 https://www.gnu.org/software/diffutils/manual/html_node/Line-Group-Formats.html.
So why doesn't it show up in the manpage? Well, it does! If you read the entire manpage. With your eyes.
-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'.
"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 less that could take an input like --unchanged-group-format and twig that it if there's no exact match, it might be related to --GTYPE-group-format would be nice.
Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)
Mi domando se sono l'unico che rimpiango i cari e vecchi #howto
I #Linux howto e #manpage dove era perfettamente SCRITTO come fare qualcosa da A-Z.
Solitamente un wiki, lo leggevi ed il tuo cervello si metteva in moto.
Adesso si và avanti a video, reels, reddit, 30 post X, e pure ChatGPT, e alla fine non si capisce una mazza, è questo lo sviluppo?
And finally, the last piece of #documentation: An actual #README, which you can read directly on github:
https://github.com/Zirias/swad
This is probably the most important part, because it should be the first thing anyone reads who might be interested in using the software. Together with a #manpage and a fully commented example #configuration file, I'd say documentation is finally complete! 
Probably time to craft a first (preview) release of #swad 
And even more #documentation: Now #swad has a #manpage (I still think #man is the nicest documentation system for CLI tools and daemons).
To keep it in sync with help output (-h flag), I use my own tool to generate it:
https://github.com/Zirias/mkclidoc
@lattera 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 #manpage #tldp #documentation #metadata #katie sstam #ft meade
Another "Tech notes to myself" blog post: Adding color to man pages
I'm still trying to figure out a decent workflow of getting my MarkDown documents converted over to HTML and getting them to render decently. I feel like I may be struggling with publishing to Blogspot than I need to be. Or, I just need more practice.
https://suburbanalities.blogspot.com/2025/02/adding-color-to-man-pages.html
Wow Michael, wat een werk en wat een boel nuttige info! Rustig uitgelegd en helder verwoord.
Ik heb zelfs geleerd dat alle package managers TODO heten 
Maar alle gekheid op een stokkie, kudo's voor al je werk! Ik ga er zeker zelf nog van leren en zeker naar verwijzen bij mijn geïnteresseerde leerlingen!
When I need docs I do
`man command'
When I pressed F1 in a gui program it did the following
* Request a helper running in my DE to parse a html page
* Ask the helper to open my default html parser
* __Without asking me__ the helper opened a __massive browser__ ravaging ram just to show me what I could find with
`man command`
* I wonder why instead the Ui program did not do the following
* request a helper open a (ba)sh
* parse >man command to the helper
* have the helper display the manpage in the sh
The results would be
* Much less resources used
* No assumption on my current internet connection would be made
* That method has worked for 60 years
<IRC>
/m shakes head and looks at the massive browser showing the equivalence of a manpage
</IRC>
#bash #sh #zsh #ksh #csh #qBittorrent #torrent #manpage #man1 #F1 #F1Help #WomenWhoCode #640daysofcode #301daysofcode #730daysofcode #100DaysOfCode #1000DaysOfCode #Linux #POSIX #Programming #DEVCommunity #RetroComputing
https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions
Please put examples in your #manpage.
It tells more then words.
I've learned something wonderfull again from my POSIX OS workstation.
I was looking for 7zip and did not bother to type 7z then tab. I was so delighted the name is **just** 7z. Of course Im reading the man page!
#bash #man #manpage #7z #sh #zsh #ksh #csh #sockets #freeBSD #netBSD #openBSD #Linux #POSIX
On this day in 1971 the first edition of the Unix Programmer's Manual was published, with the first man pages.
