Code Opener CLI ⌨️
The command line interface to add any project as favorite and open it from anywhere using just one command. Use copen add to add and copen open <project_name> to open and . See commands to get idea on more things supported by Code Opener CLI
Commands
See Lists of Projects Added
copen see
Add a Project
-
Method 1 :
- Adding Project just requires you to go to project using
cdfor the first time and type command
copen add
cd path/to/your/project copen add- This will ask for project name, give any nick name to project which is handy to you and press Enter.
Done :smile:, now you can open this project from anywhere . - Adding Project just requires you to go to project using
-
Method 2 : You can also directly add using one of the following single command :
- Using short name
-pn:copen add -pn <project_name> - Using defualt Option name :
copen add --project-name <project_name>
- Using short name
Open a Project
After a project is added , you can easily open it from anywhere using this command . Remember that project_name is the name/nick name that you gave to your project .
copen open <project_name>
Remove a Project
-
Method 1 :
- Removing Project is very easy using
copen remove- This will ask you for the project name and confirmation.
-
Method 2 : You can also directly remove using one of the following single command :
- Using short name
-pn:copen remove -pn <project_name> - Using defualt Option name :
copen remove --project-name <project_name>
- Using short name
Other handy commands
copen: Will display welcome messagecopen --help: Provides list of commandscopen <add/remove/see/open> --help: Provides you help for particular commandcopen --version: Provides you the version of code-opener-cli
Contributing to Project
Let's take this project to next level together 🎉 You can find the guidelines to contribute to this project here.
Changelogs
All notable changes to this projects can be found in CHANGELOG.md . Currently, this CLI supports on VSCode, but support for other code editors/IDE's will be added soon 😄 .
Metadata
Release files for code-opener-cli 1.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 | |
|---|---|---|---|---|
| code-opener-cli-1.0.1.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| code_opener_cli-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.3 kB
Release files / code-opener-cli-1.0.1.tar.gz
| Download URL | code-opener-cli-1.0.1.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e56f62be2e60fd8ada8843d84546b2238bb9b13e94aa22fd7f44909eaab5764a
|
|
BLAKE2b-256 checksum How to use checksums |
db701c31c59d74228f783958df983ae801a08d66758ee86beb1b788440812b4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.6.7 Linux/4.15.0-38-generic
|
Release files / code_opener_cli-1.0.1-py3-none-any.whl
| Download URL | code_opener_cli-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc8981d384972e9b45c8085b5ff39af18f27cb2be7b896bf3570d5c867e8fdbf
|
|
BLAKE2b-256 checksum How to use checksums |
d2639f305ab41a00009ee9bd0615afd25dc04c50c0f931b4c79c6e235c2c9525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.4 CPython/3.6.7 Linux/4.15.0-38-generic
|
Security for code-opener-cli 1.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.