-------
'python-cts' adds a new executable, 'cts', which searches ctag files for your tag and then executes a command on the selected tag. By default, it executes "$EDITOR +{lineNumber} {file}", which opens the found file your default editor.
Since 'cts' is only as good as your ctag files, it is recommended running ctags with '--extra=+f' so as to index filenames as well. This will let you do 'cts Foo.java' to automatically open up Foo.java in your editor of choice.
Alternatively, one can add a new line, '--extra=+f', to ~/.ctags to set it as a default option for the ctags command. This is likely a better solution as it will also work with scripts, editors, and other out-of-band processes.
If provided a tags file with line numbers instead of patterns, 'cts' will attempt to read the line of code from the actual file.
Example 1
-------
cts bar -i -c /some/directory/tags
1. '-c /some/directory/tags' indicates cts should use that tags file rather than attempting to find one.
2. '-i' indicates that it's a case insensitive search. The resulting search query is /^bar$/i
3. Upon selecting a tag, executes "$EDITOR +{pattern} {file}.
Example 2
---------
cts Foo -p -kc -t scala,py -e "grep def {file}"
1. Since no ctag file was specified, recurse from the current directory up until a 'tags' file is found.
2. '-p' indicates a partial search, so look for a /.*Foo.*/ in the tag file.
3. '-kc'
indicates to filter out everything that isn't kind 'c', or class definitions.
4. '-t scala,py' indicates to filter out all tags that are not files with 'scala' or py as the extension.
5. '-e "grep def {file}"' indicates that after a selection has been made, to execute "grep def {file}" where {file} will be filled in with the absolute path to the reference file.
To Install (From Pip)
----------
pip install python-cts
If upgrading:
pip install python-cts --upgrade
To Install (From Source)
----------
1. Checkout the repo
2. python setup.py install
3. Profit!
Usage
-----
Type 'cts -h' to get usage information
1 maintainer
Metadata
1 maintainer
Release files for python-cts 0.1.7.8
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 | |
|---|---|---|---|---|
| python-cts-0.1.7.8.tar.gz | 6.5 kB | Without provenance | Details |
Release files / python-cts-0.1.7.8.tar.gz
| Download URL | python-cts-0.1.7.8.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
798460dbac4966bb9427f2ea74f5be19322be6341171b8c41ea432f4266917c6
|
|
BLAKE2b-256 checksum How to use checksums |
dc57ca55039c8a3981280c58e3dc6af1cc445efc7e8574f057cd798ee5a756e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for python-cts 0.1.7.8
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.
