Editty
Editty is a terminal-based non-linear editor for terminal recordings.
Installation
Source
When installing from source, it is recommended (but not required) to install Editty in a virtualenv. To set one up:
virtualenv --python=python3 editty-env source editty-env/bin/activate
To install the latest version from pypi:
pip install editty
To install from a git checkout:
pip install .
In order to use the dissolve transition, you must run Editty in a 256-color capable terminal, such as gnome-terminal or xterm.
Usage
After installing Editty, you should be able to run it by invoking editty. If you installed it in a virtualenv, you can invoke it without activating the virtualenv with /path/to/editty-venv/bin/editty. which you may wish to add to your shell aliases. Use editty --help to see a list of command line options available.
Once running, pressing the F1 key will show help text.
Editty can load recordings in the formats produced by the script and ttyrec commands. It renders output in ttyrec format.
Editty does not modify the original source files, but rather references them by path name. Editty stores the edit decision list in its own JSON-based file format (use the .edit extension).
To exit, press CTRL-q.
Source
Git repo: http://git.inaugust.com/cgit/editty/
Contributing
To send your latest commit as a patch, run:
git send-email --to corvus@gnu.org --annotate -1
Or, if you don’t have git send-email configured, run:
git format-patch --stdout HEAD~1 > /tmp/editty.patch
And send /tmp/editty.patch to corvus@gnu.org using your email client.
License
Editty is licensed under the GPLv3 or later. Please see the COPYING file for details.
1 maintainer
Metadata
1 maintainer
Release files for editty 0.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 |
|---|---|---|---|---|
| editty-0.0.1.tar.gz | 17.8 kB | Without provenance | Details for editty-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| editty-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for editty-0.0.1-py3-none-any.whl |
Total release size: 37.1 kB
Release files / editty-0.0.1.tar.gz
| Download URL | editty-0.0.1.tar.gz |
|---|---|
| Size | 17.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bb374baf8ed6b9b2e940dab9e0815e1b8fea7bc29d9f4f8add94d89f4e4f123
|
|
BLAKE2b-256 checksum How to use checksums |
263b846317f251062d016f5df602718e655b3f739aa764d25aa163743e1ee2d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.5.2
|
Release files / editty-0.0.1-py3-none-any.whl
| Download URL | editty-0.0.1-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a96d277e6ea91e76f44507f6325427f3d53e4412d46ca0c8396bd0069112f95
|
|
BLAKE2b-256 checksum How to use checksums |
37f2df166bb804101a19ac667a392d72961e0b9c7b9013640f746c7cc482b5a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.5.2
|
Security for editty 0.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.
