Copies the contents of a saved register, a file, or stdin to the clipboard, or manipulates the registry.
Installing it
To install from pypi:
pip install snipco
From source, there are two ways:
If you have make, run:
make install
Otherwise, run:
./setup.py install --user
Usage
snipco [-h] [-g [name_or_path]] [-s [name]] [-x [name]] [-l]
[-p [name]] [-f [path]] [-t [text]] [-v]
snipco [-h] [-g [name_or_path]] [-s [name]] [-x [name]] [-l]
[-p [name]] [-f [path]] [-v]
For command-line help, just run:
snipco --help
Arguments
All arguments are optional; if no arguments are provided, then snipco will copy the contents of stdin to the clipboard. If –file or –text is the sole argument given, then the contents of the file or quoted text, respectively, will be copied to the clipboard.
-h, –help |
show help and exit |
-g [name_or_path], –get [name_or_path] |
Copy the contents of the saved register. The named key must exist. |
-s [register_name], –set [register_name] |
Save the input to a named register. Uses stdin as input unless either –file or –text is specified. |
-f [path], –file [path] |
Specify a file to use instead of stdin for –set. If no other arguments are supplied, copies the contents of the given file directly to the clipboard. |
-t “text to save”, –text “text to save” |
Specify quote-delimited text on the command-line instead of stdin. If no other arguments are supplied, copies the text directly to the clipboard. |
-l, –list |
List the existing registers |
-p [name], –print [name] |
Print the contents of the named register. The registry key must exist. |
-x [register_name], –unset [register_name] |
Unset the named register. |
-v, –version |
show program’s version number and exit |
Examples
Save text from a file dirctly to the clipboard:
snipco --file path/to/file.txt
or:
cat path/to/file.txt | snipco
Save text to a named register:
snipco --set myregister --text "Hello, world!"
Copy text from the register to the clipboard:
snipco --get myregister
Print text in the register to stdout:
snipco --print myregister
Unset the register:
snipco --unset myregister
List the registers you’ve saved:
snipco --list
1 maintainer
Metadata
1 maintainer
Release files for snipco 0.2.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 |
|---|---|---|---|---|
| snipco-0.2.1.tar.gz | 4.1 kB | Without provenance | Details for snipco-0.2.1.tar.gz |
Release files / snipco-0.2.1.tar.gz
| Download URL | snipco-0.2.1.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fcb7b4672abdafb06a9da0085faf8fcc56de6803069c91527fd319086a114a7
|
|
BLAKE2b-256 checksum How to use checksums |
dc9e1740de2215e3061ea258886cfafe05d8b47a72ab8e3cfe42e4d93328e85c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.40.1 CPython/3.7.5
|
Security for snipco 0.2.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.
