@@ -246,20 +246,19 @@ JSON
246
246
.. literalinclude :: ../.tmuxp.json
247
247
:language: json
248
248
249
- Run script before launch
250
- ------------------------
249
+ Bootstrap project before launch
250
+ -------------------------------
251
251
252
252
You can use ``before_script `` to run a script before the tmux session
253
- starts building.
253
+ starts building. This can be used to start a script to create a virtualenv
254
+ or download a virtualenv/rbenv/package.json's dependency files before
255
+ tmuxp even begins building the session.
254
256
255
257
It works by using the `Exit Status `_ code returned by a script. Your
256
258
script can be any type, including bash, python, ruby, etc.
257
259
258
260
A successful script will exit with a status of ``0 ``.
259
261
260
- You can use this for things like bootstrapping ruby / python environments
261
- for a project (or checking to verify their installation).
262
-
263
262
Important: the script file must be chmod executable ``+x `` or ``755 ``.
264
263
265
264
Run a python script (and check for it's return code), the script is
@@ -297,14 +296,18 @@ and panes omitted in this example)
297
296
298
297
.. _Exit Status : http://tldp.org/LDP/abs/html/exit-status.html
299
298
300
- Project configs
301
- ---------------
299
+ Per-project tmux config
300
+ -----------------------
301
+
302
+ You can load your software project in tmux by placing a ``.tmuxp.yaml `` or
303
+ ``.tmuxp.json `` in the project's config and loading it.
302
304
303
305
tmuxp supports loading configs via absolute filename with ``tmuxp load ``
304
306
and via ``$ tmuxp load . `` if config is in directory.
305
307
306
- To make a per-project config, use ``.tmuxp.yaml `` and ``.tmuxp.json `` in
307
- the root of your project directory.
308
+ .. bash ::
309
+
310
+ $ tmuxp load ~/workspaces/myproject.yaml
308
311
309
312
See examples of ``tmuxp `` in the wild. Have a project config to show off?
310
313
Edit this page.
0 commit comments