You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -176,6 +177,39 @@ The following statusline elements can be configured:
176
177
177
178
[^2]: You may also have to activate them in the language server config for them to appear, not just in Helix. Inlay hints in Helix are still being improved on and may be a little bit laggy/janky under some circumstances. Please report any bugs you see so we can fix them!
178
179
180
+
### `[editor.inline-blame]` Section
181
+
182
+
Inline blame is virtual text that appears at the end of a line, displaying information about the most recent commit that affected this line.
-`"cursor-line"`: Inline blame is only on the line of the primary cursor.
193
+
-`"hidden"`: Inline blame is hidden.
194
+
195
+
With `auto-fetch` set to `false`, blame for the current file is fetched only when explicitly requested, such as when using `space + B` to display the blame for the line of the cursor. There may be a little delay when loading the blame.
196
+
197
+
When `auto-fetch` is set to `true`, blame for the file is fetched in the background; this will have no effect on performance, but will use a little bit extra resources in the background. Directly requesting the blame with `space + B` will be instant. Inline blame will show as soon as the blame is available when loading new files.
198
+
199
+
When opening new files, even with `show` set to `"all-lines"` or `"cursor-line"`, the inline blame won't show. It needs to be fetched first in order to become available, which can be triggered manually with `space + B`.
200
+
201
+
#### `format`
202
+
203
+
Change the `format` string to customize the blame message displayed. Variables are text placeholders wrapped in curly braces: `{variable}`. The following variables are available:
0 commit comments