Earlier quoted context omitted.
I can never remember which manual page contains a description of struct timespec, for example. Running apropos or man -k didn't help me. I only found out it's time.h(0p) by a lucky guess. Info is actually a quite decent idea, it's just executed poorly. Info pages are written like books, while I really miss the concise lexicon-like format of man pages. And it doesn't help that the default GNU info viewer is on one han…
Ah. Just open the libc manual with "info libc", then "i" to look something up in the index, and type "struct timespec". (You can even tab-complete the name of the struct). >And it doesn't help that the default GNU info viewer is on one hand unusable for someone who isn't already an Emacs user Yes, well, did you consider running "info info"? :) There's a tutorial accessible with "h". It's not as if there's much to lea…
Giteveryday – A useful minimum set of commands for Everyday Git
51–53 of 53 posts
Re: Giteveryday – A useful minimum set of commands for Everyday Git
#52Earlier quoted context omitted.
Ah. Just open the libc manual with "info libc", then "i" to look something up in the index, and type "struct timespec". (You can even tab-complete the name of the struct). >And it doesn't help that the default GNU info viewer is on one hand unusable for someone who isn't already an Emacs user Yes, well, did you consider running "info info"? :) There's a tutorial accessible with "h". It's not as if there's much to lea…
`info info` is useless when you don't know info and don't have emacs installed: https://news.ycombinator.com/item?id=12301491
Re: Giteveryday – A useful minimum set of commands for Everyday Git
#53Earlier quoted context omitted.
How about tldr-pages? [1] [1] https://tldr-pages.github.io/
That does look a lot better! Bit weird that the main client requires Node.JS though.