Timeline for Explanation of % directives in find -printf
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2023 at 8:14 | comment | added | lesolorzanov | If anyone needs explanations of commands take a look at this page where you write the command and explains every part, explainshell.com/… | |
| Jan 26, 2021 at 14:56 | comment | added | peterh |
man find|wc -c results about 78 kByte, this is why your answer is useful.
|
|
| Jun 11, 2020 at 12:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Oct 26, 2018 at 15:24 | comment | added | Jim | I should also add that, in addition to overwhelming and often inscrutable output of man pages for relatively inexperienced users, as a programmer/power user I'm usually looking for novel solutions that man pages don't cover. For example (just now), specific date format for 'find' command output. The man page doesn't tell you to put "%T" in front of each variable--at least not that I found even looking for that specifically. You could spend all day trying to figuring it out. (Or just give.) Whereas a search on Stack Exchange will yield that answer, clearly explained, in the first result. | |
| Oct 26, 2018 at 4:15 | comment | added | Jim | @don_crissti I can think of several reasons. For starters, man pages are usually written with every feature explained, in whatever order makes sense to the programmer. That's not usually helpful at all to normal users. I've been scripting for 35 years, and these days I search stackexchange first, then worst-case (almost never) fall back to man page. | |
| Feb 16, 2018 at 16:16 | comment | added | Hennes | My manual page tend to be from FreeBSD though. Unless I happen to have a Linux VM within reach. And I have the impression that most questions are GNU/Linux based. | |
| Feb 15, 2018 at 12:10 | comment | added | runlevel0 | @don_crissti Or they are on a server that has no manpages installed which is rather frequent. | |
| Nov 17, 2017 at 12:52 | comment | added | don_crissti | @Kusalananda - Well, I can think of one scenario in which people would include a link to a web page instead of a quote from the documentation installed on their system: they're not on a linux machine at the time of writing the post... However, the link should point (imo) to the official docs (hence my comment above, which, for some unknown reason, was deleted by the mods...). That aside, I fully agree with you: the OP should consult the manual page installed on their system. | |
| Nov 17, 2017 at 9:53 | comment | added | Kusalananda♦ | @don_crissti I'll never understand why people prefer random web documentation to the documentation installed on their systems (which has the added benefit of actually being relevant to their system). | |
| Nov 17, 2017 at 9:31 | history | edited | fedorqui | CC BY-SA 3.0 |
include text instead of image; quote instead of code
|
| S Mar 27, 2017 at 14:09 | history | suggested | Jonathan H | CC BY-SA 3.0 |
replace dead link
|
| Mar 27, 2017 at 13:36 | review | Suggested edits | |||
| S Mar 27, 2017 at 14:09 | |||||
| Jul 11, 2015 at 7:01 | vote | accept | Sandjaie Ravi | ||
| Jul 11, 2015 at 6:34 | history | answered | Hennes | CC BY-SA 3.0 |