tmux-control
configure and control tmux
setup
sudo apt-get install \
cmus \
elinks \
htop \
nvtop \
ranger \
tmux
sudo pip install tmux_control
configurations
analysis mode
This mode is designed to be ergonomic for running an analysis. The bottom terminal runs the main analysis code while ranger allows for quick viewing of ongoing analysis output files.
----------------------- | | | ranger | | | | | |---------------------| | | | terminal | | | | | -----------------------
badass mode
----------------------- | ranger | | |----------| | | terminal | | |----------| | | htop | ranger | |----------| | | arXiv | | |----------| | | cmus | | -----------------------
detail mode
This mode is designed to be a less fun version of badass mode.
----------------------- | | | | ranger | | |----------| | | terminal | | |----------| ranger | | htop | | |----------| | | arXiv | | | | | -----------------------
edit mode (default)
This mode is designed to be ergonomic for coding.
----------------------- | | | | | | | | | | | | | terminal | ranger | | | | | | | | | | | | | -----------------------
Nvidia mode
This mode is designed to display system resource usage for a system featuring Nvidia hardware.
----------------------- | | | htop | | | | | |---------------------| | | | nvtop | | | | | -----------------------
run mode
This special mode launches all of the scripts at a defined directory in separate windows. It is used by engaging the option --run, optionally together with the --directory option used to set the directory with a full or relative path (by default, the directory “scripts” at the working directory) and the --extension option used to define the extension of the scripts (by default, “sh”, and which can be set to “none” for any extensions).
For example, the following command should run all files, regardless of extensions, at the directory /home/user/run_scripts:
tmux-control.py --run --directory=/home/user/run_scripts --extension=none
----------------------- | | | | | | | | | scripts | | | | | | | | | -----------------------
work mode
This mode is designed to be a compromise between analysis, edit and badass modes.
----------------------- | | | ranger | |---------------------| | | | terminal | |---------------------| | | | | ranger | cmus | | | | -----------------------
Metadata
Release files for tmux-control 2024.5.8.1442
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 |
|---|---|---|---|---|
| tmux-control-2024.5.8.1442.tar.gz | 17.4 kB | Without provenance | Details for tmux-control-2024.5.8.1442.tar.gz |
Release files / tmux-control-2024.5.8.1442.tar.gz
| Download URL | tmux-control-2024.5.8.1442.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf5f8162eafe12cd99af56d7d0997c7d4c15eba63a18e210e9d73f8948679b72
|
|
BLAKE2b-256 checksum How to use checksums |
f7b4988262ad8f3b0dd7a6430553b3ce2f44965d8573217ac6f946879c032770
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.12
|
Security for tmux-control 2024.5.8.1442
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.