## CDHISTORY
[](https://travis-ci.org/jdowner/cdhistory)
This package is used to record the frequency of visits to particular directories through the ‘cd’ function. The goal is to use this information to provide a way to quickly navigate to commonly visited directories.
To incorporate this functionality, install the package in the usual way,
python setup.py install
This will add the cdhistory packacge to your python install area, and a cdhistory script to /usr/local/bin. To incorporate cdhistory into your normal ‘cd’ use, there is a bash script installed in /usr/local/share called cdhistory.bash that provides an function to wrap ‘cd’.
The cdhistory.bash snippet replaces the existing ‘cd’ function in bash with a wrapped version. The function behaves like the builtin cd command normally, but records the directories that are visited. However, if you prepend the first argument to ‘cd’ with a colon it will go to the best match using cdhistory, e.g.
cd :repos
will ‘cd’ to the path that best matches the string ‘repos’. In effect, this is like creating aliases for commonly visited directories.
1 maintainer
Metadata
1 maintainer
Release files for cdhistory 0.1
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 |
|---|---|---|---|---|
| cdhistory-0.1.tar.gz | 5.3 kB | Without provenance | Details for cdhistory-0.1.tar.gz |
Release files / cdhistory-0.1.tar.gz
| Download URL | cdhistory-0.1.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e2f32352373b0517938bcb5d0a485bf8b6d97cd3fa6201f6719c17ea08925a1
|
|
BLAKE2b-256 checksum How to use checksums |
90ffecf83216544ee093157a359156b4e0769910ee8cc3928b42aedff1ea3cff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cdhistory 0.1
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.
](https://travis-ci.org/jdowner/cdhistory){kind=link}