cppman
C++ manual pages for Linux, with source from cplusplus.com and cppreference.com, supporting all C++ versions provided by the sources.
Features
Supports two backends (switch it with cppman -s):
Syntax highlighting support for sections and example source code.
Usage/Interface similar to the ‘man’ command
Hyperlink between manpages (only available when pager=vim)
Press Ctrl-] when cursor is on keyword to go forward and Ctrl-T to go backward.
You can also double-click on keyword to go forward and right-click to go backward.
Frequently update to support cplusplus.com.
Demo
Using vim as pager
Installation
Install from PyPI:
$ pip install cppman
Note that cppman requires Python 3. Make sure that either pip is configured for Python 3 installation, your default Python interpreter is version 3 or just use pip3 instead.
Arch Linux users can find it on AUR or using Trizen:
$ trizen -S cppman
or install the git version
$ trizen -S cppman-git
Debian / Ubuntu: cppman is available in Debian sid/unstable and Ubuntu vivid.
$ sudo apt-get install cppman
MacOS X: cppman is available in Homebrew and MacPorts.
$ brew install cppman
or
$ sudo port install cppman
Package Maintainers
FAQ
Q: Can I use the system man command instead of cppman?
A: Yes, just execute cppman -m true and all cached man pages are exposed to the system man command. Note: You may want to download all available man pages with cppman -c.
Q: Why is bash completion is not working properly with ::?
A: It is because bash treats : like a white space. To fix this add export COMP_WORDBREAKS="${COMP_WORDBREAKS//:}" to your ~/.bashrc.
Bugs
Please report bugs / mis-formatted pages to the github issue tracker.
Contributing
Fork it
Create your feature branch (git checkout -b my-new-feature)
Commit your changes (git commit -am 'Add some feature')
Push to the branch (git push origin my-new-feature)
Create new Pull Request
Support
If you find this project useful, consider buying me a coffee! ☕
Notes
manpages-cpp is renamed to cppman since September 19, 2012
Metadata
Release files for cppman 0.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cppman-0.6.3.tar.gz | 814.4 kB | Without provenance | Details for cppman-0.6.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cppman-0.6.3-py3-none-any.whl | Python 3 | none | any | Details for cppman-0.6.3-py3-none-any.whl |
Total release size: 1.7 MB
Release files / cppman-0.6.3.tar.gz
| Download URL | cppman-0.6.3.tar.gz |
|---|---|
| Size | 814.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16a782b87b0848c5202b61965402258f8fc8260cbf0867cb876992eb3d046eb0
|
|
BLAKE2b-256 checksum How to use checksums |
a297b0c1de5b35cc4e66eb32accffd261c22d511aba964a7aed3b210a85851b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Release files / cppman-0.6.3-py3-none-any.whl
| Download URL | cppman-0.6.3-py3-none-any.whl |
|---|---|
| Size | 886.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ecbf58ff8508f734b2f9f628734665e4ab74db2291dccdcaa967ba221045239
|
|
BLAKE2b-256 checksum How to use checksums |
bc3abbf1c667f0b3a82ee701719438dc382e410e99e9aa1b88addb15f22cd838
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for cppman 0.6.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.