Skip to content

Commit dc2850b

Browse files
committed
docs: update migration guide
1 parent f177902 commit dc2850b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

migrate_to_v2.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Migration to v2.0
22
This is a guide for users that want to migrate to version `2.0` of `live-command`.
3-
If you want to stay on version `1.0`, you can also pin the plugin to the tag `v1.0`.
3+
If you want to stay on the previous major version, you can pin the plugin to the tag [`1.x`](https://github.com/smjonas/live-command.nvim/releases/tag/1.x).
44

55
## What has changed in version 2.0?
66
Version 2.0 is a rewrite of the plugin for better maintainability and future extensibility.
77
It simplifies the user-facing API while improving the architecture of the plugin and adding a new `:Preview` command.
88

99
**Breaking change**:
1010
- Custom command specifications now only consist of a `cmd` value (a string); `args`
11-
and `range` have been removed. See
11+
and `range` have been removed. See [next section](#how-can-i-migrate-from-older-versions).
1212

1313
**New feature**:
1414
- New generic `:Preview` command that allows to preview any command without having to
@@ -31,8 +31,8 @@ local commands = {
3131
},
3232
}
3333
```
34-
In `v2.0`, you have two options:
35-
1. Define a command `Norm = { cmd = "norm" }` and use it as `:Norm <count>@<register>` (e.g., `:Norm 5@a` to apply macro stored in register `a` five times)
34+
In version `2.0`, you have two options:
35+
1. Define a command `Norm = { cmd = "norm" }` and use it as `:Norm <count>@<register>` (e.g., `:Norm 5@a` to apply macro stored in register `a` five times).
3636
2. Define a custom `:Reg` user command like this that works just like the old version:
3737

3838
<details>

0 commit comments

Comments
 (0)