Skip to content

Commit c4c189b

Browse files
committed
Another small update on README
1 parent cb3e3db commit c4c189b

File tree

1 file changed

+18
-6
lines changed

1 file changed

+18
-6
lines changed

README.md

Lines changed: 18 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,23 @@ It was originally based on [vim-slime](https://github.com/jpalardy/vim-slime).
1111

1212
## Getting Started ##
1313

14-
You can start livecoding with Vim simply by running:
14+
1. Start livecoding with Vim by simply running:
1515

1616
$ tidalvim
1717

1818
This creates a tmux session with Vim and Tidal running on different panes.
1919

20-
Then, you can write something and press `<c-e>` (Control + E) to evaluate that
21-
piece of code.
20+
2. Write something like this:
2221

23-
When you do this you should see Vim select it for a second and a chunk of text
24-
appear on your Tidal interpreter. If you already have SuperDirt or other synth
25-
running, you should hear something now...
22+
```haskell
23+
d1 $ sound "bd sn"
24+
```
25+
26+
3. While being on that line, press `<c-e>` (Control + E) to evaluate it.
27+
28+
You should see Vim flash that line for a second and a chunk of text appear on
29+
your Tidal interpreter. If you already have SuperDirt or other synth running,
30+
you should hear a kick and a snare :)
2631

2732

2833
## Install ##
@@ -136,6 +141,13 @@ tidal> :t density 2 $ n "0 1"
136141
density 2 $ n "0 1" :: Pattern ParamMap
137142
```
138143

144+
So, in case you don't want to use `tidalvim`, just run the following on another
145+
terminal:
146+
147+
```bash
148+
tmux new-session -s tidal tidal
149+
```
150+
139151
What `tidal` does is actually run `ghci` with the argument `-ghci-script
140152
Tidal.ghci`. [Tidal.ghci](Tidal.ghci) is found at the root of the repository,
141153
and is responsible for bootstraping Tidal. See Configure section for more on

0 commit comments

Comments
 (0)