turbo-editors/turbo-rustpublic Fork 0
v1.0.1
Commits
Clone
git clone https://git.rickub.com/turbo-editors/turbo-rust.git
git clone ssh://git@rickub.com/turbo-editors/turbo-rust.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

tools.toml.tmpl · 81 lines · 2.5 KBCheetah Blame HistoryRaw
📦 Turbo Rust 713ea5c k33g 14h ago1# turbo-rust tools.
2#
3# Each [[tool]] becomes one line of the Rust menu, in the order they appear
4# here. name is what the menu shows; a letter between tildes is its hot key, and
5# no two tools should claim the same one.
6#
7# command goes to "sh -c", so pipes, globs and && work: one entry can be a
8# whole sequence.
9#
10# menu says which menu it appears in. Leave it out and the tool goes into the
11# Rust menu; name anything else and that menu is created for you, in the order
12# the names first appear here. A tool that has nothing to do with Rust belongs
13# in one of your own:
14#
15# [[tool]]
16# name = "~E~cho"
17# command = "echo TADA"
18# menu = "Tools"
19#
20# A {{label}} in a command is a value the editor asks for before running it, in
21# a box titled after the tool. The text between the braces is what it asks for:
22#
23# [[tool]]
24# name = "~N~ew binary"
25# command = "cargo new --bin {{crate name}}"
26#
27# The value is quoted, so a path with a space in it stays one argument. Add ...
28# inside the braces when you mean several arguments rather than one value:
29#
30# [[tool]]
31# name = "Test ~o~ne"
32# command = "cargo test {{extra flags...}}"
33#
34# Double braces, not single. Single ones appear in real commands — awk '{print
35# $1}' and find . -exec rm {} + are both ordinary things to put here — and
36# neither is asking you for anything.
37#
38# output says where what the command prints goes:
39# popup a dialog that fills in as it runs, and says the exit code (default)
40# terminal a terminal window, for anything that reads the keyboard or runs long
41# editor an editing window once it has finished, to search with Ctrl-F
42#
43# Commands run in the directory the editor was started in, which is why they
44# see the whole workspace when you start from its root.
45
46[[tool]]
47name = "~F~ormat"
48command = "cargo fmt"
49output = "popup"
50
51[[tool]]
52name = "~L~int"
53command = "cargo clippy --all-targets"
54output = "popup"
55
56[[tool]]
57name = "~B~uild"
58command = "cargo build"
59output = "popup"
60
61[[tool]]
62name = "~T~est"
63command = "cargo test"
64output = "popup"
65
66[[tool]]
67name = "~R~un"
68command = "cargo run"
69# A terminal, not a popup: a program that reads the keyboard has to be able to
70# be answered, and one that runs long has to be able to be interrupted.
71output = "terminal"
72
73# A tool naming a `menu` gets a menu of its own on the bar. Nothing above does,
74# so every tool above is in the Rust menu. This one is in a menu called Tools,
75# which appears between Rust and Help — that is the whole mechanism.
76
77[[tool]]
78name = "~E~cho"
79command = "echo 🎉 tada!"
80menu = "Tools"
81output = "terminal"