Chrome Edit Server
This application is an “edit server” supporting one of the many Chrome plugins (including TextAid and Edit with Emacs) allowing you to edit text area fields displayed in your browser using your editor-of-choice.
Getting Started
First, install this package from PyPI:
pip install chrome-edit-server
Second, run the server by running:
chrome-edit-server
Then, install either the TextAid or Edit with Emacs Chrome extensions. Follow the extension’s instructions regarding how to open up an editor window.
Configuration
By default, the edit server will run on port 9292, and will use GVim (gvim -f) as your editor, but you can configure each of those parameters by either setting environment variables or providing arguments from the command line.
To see a brief overview of what settings can be provided from the command-line run:
chrome-edit-server --help
Environment Variables
EDIT_SERVER_EDITOR: Sets the editor command to run when editing a file. Defaults to gvim -f. Note that you will want this application to return only once your file edits have been completed! Example settings include:
OSX:
MacVim: open -aW MacVim
Linux:
GVim: gvim -f (default)
EDIT_SERVER_PORT: Set the port that the edit server will run on. Defaults to 9292.
EDIT_SERVER_DELETE_DELAY: Sets the amount of time (in minutes) to wait before deleting created temporary files. Defaults to 5.
EDIT_SERVER_TEMP: Sets the path to where temporary files should be stored. Defaults to your system’s temporary files directory.
EDIT_SERVER_INCREMENTAL: Sets whether incremental editing will be enabled; your chrome editor plugin must support this feature for it to have an effect. By default this is turned on.
EDIT_SERVER_USE_FILTERS: Sets whether filters are enabled. By default this is turned on.
Contributors
This is an unofficial (but endorsed) fork of @gfxmonk’s edit-server repository that follows common Python style conventions, and is packaged for distribution on PyPI.
If you have any thanks to give for this application’s existence – you owe them to that gentleman.
1 maintainer
Metadata
1 maintainer
Release files for chrome-edit-server 0.3.4
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 |
|---|---|---|---|---|
| chrome-edit-server-0.3.4.tar.gz | 7.8 kB | Without provenance | Details for chrome-edit-server-0.3.4.tar.gz |
Release files / chrome-edit-server-0.3.4.tar.gz
| Download URL | chrome-edit-server-0.3.4.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02c49a680a3eb7fa015d6580cb77d709e0f9a19df1e8deb2c1dd3b33dff2f662
|
|
BLAKE2b-256 checksum How to use checksums |
6affba3f4b4229dbbb65321360991edc689c6cdc2151740387733c93c9335076
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for chrome-edit-server 0.3.4
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.
