cursorless icon indicating copy to clipboard operation
cursorless copied to clipboard

Don't let the cursor slow you down

Results 419 cursorless issues
Sort by recently updated
recently updated
newest added

Is a bit more intuitive than effectively having two cursors For cases where you want a separate cursor that doesn't move your existing cursor (eg for "bring" or "chuck"), you...

keyboard

in this map: https://github.com/cursorless-dev/cursorless/blob/5f94e084af3f67e07a6d6f68e478365e7a691d31/packages/cursorless-vscode/src/keyboard/keyboard-config.fixture.json#L85-L100 we would eg change `wb` to `{`

good first issue
keyboard

I have `fk` bound to `makeRange` and `ff` bound to `combineColorAndShape`. In the following contrived example, when targeting from `bolt s` to `green fox )`, I run into a series...

bug
keyboard

In newer versions of tree-sitter-python, it uses `string_start` and `string_end` as the type for string delimiter tokens. This will break all of our surrounding pairs in python. We should fix...

bug

It can be either `"test"`, `"develop"`, or unset. If it is unset, it means production, because we don't have an easy way to set it in production and prob best...

code quality

following this issue https://github.com/saidelike/cursorless/pull/2#issuecomment-2163093831 It would be nice if we could see that error message directly on ci using one of the following: * we could run nvim twice, once...

app-neovim

If I have a URL in the terminal and target it with `click second paint row ` it doesn't open the link, like it would in vscode. It prints the...

good first issue
app-neovim

"take round air" on `$($a)` selects `$($a)`, but it should select `($a)`.

- saying `take first token row one`/`take token` works fine in normal or insert mode (in text editor) - however, in normal terminal mode, saying `take token` when in the...

app-neovim

In the following code: ```latex \begin{lstlisting}[language=Python] aaa \end{lstlisting} ``` Saying `"take inside environment air"` selects instead we'd expect Unfortunately we can't do much about this until https://github.com/latex-lsp/tree-sitter-latex/issues/108#issuecomment-2161268087 is resolved

bug
lang-latex