Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/moustacheful/myrmidon
A rofi task / command executor
https://github.com/moustacheful/myrmidon
bash command-line-tool configuration i3 linux rofi task-runner
Last synced: 2 months ago
JSON representation
A rofi task / command executor
- Host: GitHub
- URL: https://github.com/moustacheful/myrmidon
- Owner: moustacheful
- License: mit
- Created: 2018-12-12T03:38:26.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2020-09-03T19:53:08.000Z (over 4 years ago)
- Last Synced: 2023-12-13T13:32:48.211Z (about 1 year ago)
- Topics: bash, command-line-tool, configuration, i3, linux, rofi, task-runner
- Language: Shell
- Homepage:
- Size: 11.7 KB
- Stars: 91
- Watchers: 6
- Forks: 8
- Open Issues: 8
-
Metadata Files:
- Readme: readme.md
- License: LICENSE
Awesome Lists containing this project
README
# Myrmidon
A dead-simple, tiny task executor for Rofi.
## What
Myrmidon executes tasks for you, displaying something similar to modern text editor's command palette. You define the task names and commands, and let myrmidon make a fuzzy search list to select and execute tasks.
## Why
I've been looking for something like this for a while since I started using i3. Sometimes not everything merits yet another keybinding to remember, nor a bunch of shell files laying around.
## Requirements
Myrmidon currently depends on:
- [Rofi](https://github.com/DaveDavenport/rofi)
- [jq](https://stedolan.github.io/jq/)
## Installation / defining tasks
Copy both shell scripts in the same directory (e.g: ~/bin)
Define your tasks in a json file. The default location of the json file will be `$HOME/.myrmidon-tasks.json`, but you can pass an optional argument as a custom path for the configuration file (e.g: `./myrmidon.sh ~/my-custom-path/tasks.json`).
Each task is comprised of a `name`, `command` and whether or not it needs a confirmation screen (`confirm`):
Example:
```json
[
{
"name": "Area screenshot",
"command": "gnome-screenshot -a"
},
{
"name": "Window screenshot",
"command": "gnome-screenshot -w"
},
{
"name": "Power off",
"confirm": true,
"command": "systemctl poweroff"
},
{
"name": "Reboot",
"confirm": true,
"command": "systemctl reboot"
},
{
"name": "Suspend",
"confirm": true,
"command": "systemctl suspend"
}
]
```
After configuring your tasks file, you would have to set up a keybinding, if needed, to make it work.
For example, in `i3`:
```
bindsym $mod+p exec --no-startup-id ~/bin/myrmidon.sh
```
## Multiple config files
As it is possible to provide an optional location of the config file, you can keep multiple keys for different task "categories", for example:
```
bindsym $mod+p exec --no-startup-id ~/bin/myrmidon.sh ~/common-tasks.json
bindsym $mod+Esc exec --no-startup-id ~/bin/myrmidon.sh ~/power-tasks.json
bindsym $mod+Print exec --no-startup-id ~/bin/myrmidon.sh ~/screenshot-tasks.json
```
This way, for example, $mod+Esc will now only show tasks related to power (Power off, restart, suspend, etc), as to not pollute the task pool.
## Contribute
If you feel there's any missing feature you'd like to see in Myrmidon, feel free to propose it or open a pull request!