#manpage — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #manpage, aggregated by home.social.
-
*wants to see the help page for "reboot"
*types "reboot -h" 💁
*pc immediately reboots 😑
*tries again with "man reboot" 🤪 -
*wants to see the help page for "reboot"
*types "reboot -h" 💁
*pc immediately reboots 😑
*tries again with "man reboot" 🤪 -
Is there any reason, why
curllists an example in their--headersection as follows:curl -H "User-Agent: yes-please/2000" https://example.comIs there someone a #Jazz fan, or is it some other kind of a pun? 🤔
-
Is there any reason, why
curllists an example in their--headersection as follows:curl -H "User-Agent: yes-please/2000" https://example.comIs there someone a #Jazz fan, or is it some other kind of a pun? 🤔
-
I've actually authored Unix man pages.
The best resources to get started with this 1970s dark arts from Bell Labs are these:
O'Reilly: UNIX° TEXT PROCESSING Chapter 4 nroff and troff:
https://www.oreilly.com/library/view/unixdeg-text-processing/9780810462915/Chapter04.html
At least Emacs has an nroff mode, which will make authoring man pages significantly easier.
Nroff Mode (GNU Emacs Manual):
https://www.gnu.org/software/emacs/manual/html_node/emacs/Nroff-Mode.html
More about nroff:
https://en.wikipedia.org/wiki/Nroff
Hope this helps.
-
I've actually authored Unix man pages.
The best resources to get started with this 1970s dark arts from Bell Labs are these:
O'Reilly: UNIX° TEXT PROCESSING Chapter 4 nroff and troff:
https://www.oreilly.com/library/view/unixdeg-text-processing/9780810462915/Chapter04.html
At least Emacs has an nroff mode, which will make authoring man pages significantly easier.
Nroff Mode (GNU Emacs Manual):
https://www.gnu.org/software/emacs/manual/html_node/emacs/Nroff-Mode.html
More about nroff:
https://en.wikipedia.org/wiki/Nroff
Hope this helps.
-
Learn how to convert man pages to PDF using man -t and ps2pdf. Complete guide with commands for Linux, BSD, and macOS.
Read the full guide here: https://ostechnix.com/print-export-man-pages-pdf-linux-unix/
#Manualpages #manpage #pdf #ps2pdf #Ghostscript #Postscript #mandoc #Linux #Unix #Bsd #Macos #Linuxcommands #Linuxbasics #Linuxhowto #Sysadmin #Linuxadmin
-
Learn how to convert man pages to PDF using man -t and ps2pdf. Complete guide with commands for Linux, BSD, and macOS.
Read the full guide here: https://ostechnix.com/print-export-man-pages-pdf-linux-unix/
#Manualpages #manpage #pdf #ps2pdf #Ghostscript #Postscript #mandoc #Linux #Unix #Bsd #Macos #Linuxcommands #Linuxbasics #Linuxhowto #Sysadmin #Linuxadmin
-
One Open-source Project Daily
man-page inspired Markdown viewer
https://github.com/Titor8115/mandown
#1ospd #opensource #c #cli #commandline #console #linux #man #manpage #markdown #ncurses #ncursesui #terminal #tui -
One Open-source Project Daily
man-page inspired Markdown viewer
https://github.com/Titor8115/mandown
#1ospd #opensource #c #cli #commandline #console #linux #man #manpage #markdown #ncurses #ncursesui #terminal #tui -
Today this bugged me enough to investigate it again, and it's actually a confirmed bug in the `man` command! 😂
https://gitlab.com/man-db/man-db/-/issues/40
As far as I understand it, English man pages are special since they're not in a subdirectory:
/usr/share/man/man1/tac.1.gz
—vs—
/usr/share/man/de/man1/tac.1.gzAnd somehow man's language handling doesn't consider them at all when also finding a page in the $LANGUAGE list.
Workaround: Unset $LANGUAGE when invoking `man`. 💁♂️
-
Today this bugged me enough to investigate it again, and it's actually a confirmed bug in the `man` command! 😂
https://gitlab.com/man-db/man-db/-/issues/40
As far as I understand it, English man pages are special since they're not in a subdirectory:
/usr/share/man/man1/tac.1.gz
—vs—
/usr/share/man/de/man1/tac.1.gzAnd somehow man's language handling doesn't consider them at all when also finding a page in the $LANGUAGE list.
Workaround: Unset $LANGUAGE when invoking `man`. 💁♂️
-
(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
lessthat could take an input like--unchanged-group-formatand twig that it if there's no exact match, it might be related to--GTYPE-group-formatwould be nice.Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)
-
(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
lessthat could take an input like--unchanged-group-formatand twig that it if there's no exact match, it might be related to--GTYPE-group-formatwould be nice.Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)
-
@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
-
@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
-
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 shThe 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
