Good videos, with context.
"Cursorless: A spoken language for editing code" by Pokey Rule (Strange Loop 2023)

"Cursorless: A spoken language for editing code" by Pokey Rule (Strange Loop 2023)

Strange Loop Conference
2 HN recommenders · discussed 2023–2026
Open YouTube ↗

About this video

Pokey Rule presents Cursorless, a spoken language designed for editing code by voice, built on tree-sitter parsing with smart structural and simple token-level primitives. The talk is from Strange Loop 2023.

Why it appears in the archive

HN recommends it as the best overview of Cursorless, likened to vim with your voice, and relevant to accessibility and voice coding discussions.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

citruscomputing · 2023-11 · rec

If you want a general overview of cursorless, along with seeing what it looks like in practice, the talk from Strange Loop this year was great: [VIDEO]

Read original comment ↗
chamomeal · 2026-05 · rec

Kinda related, but this reminded me of the guy who made a voice controlled text editing language. It's kinda like vim with your voice. Super cool talk here: [VIDEO]

Read original comment ↗
pokeyrule · 2023-10 · reference

Ok awesome thanks I kept waiting for someone to call me on this one and I was starting to worry that no one would :). I don't believe it's Turing complete yet, so I think you may be right to call me on it. Kind of depends how you define "programming language", I guess. For what it's worth, I talk a bit about Cursorless from the perspective of programming language paradigms starting at 31:30 ( [VIDEO] )

Read original comment ↗
sargstuff · 2023-10 · reference

=== unicorn[0] fits in the 'easy to keep everything in memory' mental model language department without loosing expressiveness/power. language documentation page[3]. --- very high level / 6th generation level language. Makes extensive use of generators for doing goal directed programming. === Cursorless is spoken editor[1]. Throat mike useful in cubical office.[2] --- type one thing. speak another. X2 productivity. === [0] : [LINK] --- [1] : [VIDEO] --- [2] : [LINK] --- [3] : [LINK] --- ===

Read original comment ↗
sargstuff · 2023-10 · reference

Traditional physical keyboard options: * Spend $$ for apl specific keyboard [0] * Standard keyboard modifications: use macros/insert unicode chacters via keyboard[1]; stickers[2], change keycaps. --- " ... another way?" : Most things in life can be approached in different ways (doesn't mean it's practical / realistic for given situation). "setting up keyobard layout": No, but do need to pick a specific method/approach to use. Some examples: a) Cursorless[3] uses spoken language to edit code. b) Using and IDE/editor that does apl auto complete [4] c) Pick from on-screen keyboard doesn't require a physical keyboard setup. Knowing the layout of the virutal screen keyboard may help to quickly find/narrow down the key(s) for selection (eyeball, mouse) --------- Above results found with basic web search. --------- [0] : [LINK] [1] :a) [LINK] :b) [LINK] :c) [LINK] :d) [LINK] [2] : [LINK] [3] : cursorless (audio editor) : [VIDEO] [4] : [LINK] ***

Read original comment ↗
sargstuff · 2023-12 · reference

treesitter[1] is one behind the scenes approach to 'blocking' text to reduced/hi-light what is under review. VSCode is one program that makes use of treesitter. Related alternate discussions of editors using treesitter aerial.neovim[2] / outline.vim[3]. One can setup voice equivalents of macro's to do the verbal equivalent of regular expression(s) to search/sound out tagged list of sections of interest to further voice in detail. Cursorless[4][5][6] AI assistant with jetbrains[7] speach related editing sources: "Ask HN: What are the best / most accessible languages for blind programmers?" covers some ideas.[0] ---- [0] : [LINK] [1] : [LINK] [2] : [LINK] [3] : [LINK] [4] : Cursorless talk : [VIDEO] [5] Cursorless : [LINK] [6] : cursorless examples : [LINK] / [LINK] [7] : [LINK]

Read original comment ↗