pinfo
pinfo copied to clipboard
baszoetekouw
Console-based info reader
Man and info pages often contain file paths and sometimes URLs. It would be handy if these could be recognized such that they could be cycled through and followed. Files...
Apparently `u` is fixed at going a node up, regardless of what I bind it to...
Hey, I'd really like to use this instead of info, but some things hold me back: `info` has a `--vi-keys` option which I much prefer, handbinding all of `pinfo`'s keys...
Compilation error on _macOS Catalina 10.15.5_: ``` utils.c:372:62: error: unused parameter 'completions' [-Werror,-Wunused-parameter] getstring_with_completion(char *prompt, const char * const * completions) ^ 1 error generated. ``` The error seems happen...
Compilation error on _Red Hat Enterprise Linux Workstation release 7.5 (Maipo)_: ``` manual.c: In function 'add_highlights': manual.c:1866:16: error: 'uint64_t' undeclared (first use in this function); did you mean 'u_int64_t'? else...
First of all, congratulations for what you have done with `pinfo`! Using `VERBOSE=false` in `/etc/pinforc` is very valuable because it saves readings, little nuisances (and finally time) to people, although...
pinfo currently only supports Node hyperlinks and not Anchors (see https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Info-Format-Tag-Table.html for the difference between those). Specifically, pinfo assumes all links are to Nodes, and so after seeking to the...
Defining _XOPEN_SOURCE on its own hides definitions in other headers (which is already mentioned in commit f49941a89d82ac1329). One way to deal with this is to define _DEFAULT_SOURCE in addition to...
That also follows the design principle of "silence is golden" (from the Unix philosophy).