cursorless
cursorless copied to clipboard
cursorless-dev
Don't let the cursor slow you down
Right now the setter and getter for clipboard uses the `*` register, where as the `paste()` function in `utils.lua` uses the `+` register. Although both are clipboard associated, I don't...
This doesn't handle all uses of key and value. Missing still are assignment statements (name, value), function signatures (name, value), and possibly other places (perhaps type declarations?). It does handle...
When bringing multiple tokens to the commandline the default output target type doesn't seem to be line-based. So far example: ```bash ❯ echo foo\\nbar foo bar ``` If you say...
I bumped into this while working on Kotlin support. Here is what triggered it: ```scm (jump_expression "return@" . (label) . (_) @value ) @_.domain ``` This triggers an "invalid capture"...
atm the show logs task is: ``` { "label": "Neovim: Show logs", "type": "process", "command": "tail", "args": [ "-f", "${workspaceFolder}/packages/cursorless-neovim/out/nvim_node.log" ] }, ``` I get an error from that task...
Currently the documentation for running and testing the extension states: ```markdown ## Running / testing extension locally In order to test out your local version of the extension or to...
## Checklist - [ ] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) - [ ] I have updated the [docs](https://github.com/cursorless-dev/cursorless/tree/main/docs) and [cheatsheet](https://github.com/cursorless-dev/cursorless/tree/main/cursorless-talon/src/cheatsheet) - [ ] I have not broken the cheatsheet
Revives #872. It might be a good idea to enable [`import/no-duplicates`] first though. [`import/no-duplicates`]: https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-duplicates.md https://typescript-eslint.io/rules/consistent-type-imports/ ## 🥞 - #1829 ## Checklist - [ ] I have added [tests](https://www.cursorless.org/docs/contributing/test-case-recorder/) -...
for voice discussion. definitely work in progress.
I had the thought that with our compositional pipelines, `"funk name"` and `"class name"` should just be equivalent to `"name funk"` and `"name class"`, respectively, as the latter would just...
