Cursorless – A spoken language for structural code editing • Hacker News Board

Re: Cursorless – A spoken language for structural code editing

#71

Post by foerbert » Tue, Sep 06, 2022, 8:08 AM UTC

Xevi wrote: post #48

foerbert wrote: post #35

Earlier quoted context omitted.

I have some very mixed feelings about talon. I looked into it a decent bit when I started having hand issues as well, and never got anywhere useful with it. For one, it needs to be programmed to do anything. This gets you all the options, which is wonderful, but also is a bit of a problem when you're looking into because you can't, ya know, program. And it's not a simple thing to interact with. Lots of moving parts a…

It sounds like Serenade.ai would be more useful to you. It is more of a complete product, with the ability to add custom commands on top of it. Plus it's open source. I'm not trying to steal the spotlight from Talon/Cursorless though, they are amazing and super useful. But it is definitely a much more fragmented ecosystem which requires more work.

I think I looked at that briefly at one point. I passed by it quickly because it lacked support for both my usual editor and language.

But I've recently revisted VS Code and found it improved enough to be usable for me. My hands have also improved enough that I can do a reasonable amount of typing now too, so perhaps adding language support would be an option. Hm...

Thanks for the suggestion!

Re: Cursorless – A spoken language for structural code editing

#72

Post by lunixbochs » Wed, Sep 07, 2022, 7:55 AM UTC

foerbert wrote: post #70

lunixbochs wrote: post #50

Earlier quoted context omitted.

I agree the non programmer use of Talon is still unpolished. That was an intentional prioritization as I work to solidify the underlying tech. Note that your best option for documentation right now is the Slack, where I am very active. I have a clear vision for easier customization and adaptation in the long term. Maybe check back every now and then, it's a labor of love and I plan to continue improving it for a long…

Well, I am a programmer, I just wasn't able to do much programming due to physical limitations. Admittedly I'm not much of a Python programmer, and I wouldn't be surprised if a deeper understanding of not-just-a-shell-script Python idioms helped me get a little more out of the REPL poking. But uh, still. As for Slack, I don't really consider that documentation. It's not really usable in the same way. It's more akin t…

> unofficially not much more than a few paragraphs

There's a lot more than a few paragraphs on the wiki (which is linked right after the setup instructions in the official docs), including ~30 pages about the scripting system alone: https://talon.wiki/unofficial_talon_docs/

> As for Slack, I don't really consider that documentation

I think you should try asking questions on this particular Slack before you write it off and recommend that I do something else. It is my official support channel and I am extremely active and helpful there.

> Having the option to try to figure things out by looking at the code could be very helpful

One thing to try - Talon has good Python type annotation coverage and the type information is shipped with Talon. If you point VSCode at Talon's Python interpreter (at `~/.talon/bin/python` on Linux/Mac or `%appdata%\talon\.venv\scripts\python` on Windows), the language tooling in your editor should then know about Talon's API and types.

Re: Cursorless – A spoken language for structural code editing

#73

Post by foerbert » Thu, Sep 08, 2022, 10:34 AM UTC

lunixbochs wrote: post #72

foerbert wrote: post #70

Earlier quoted context omitted.

Well, I am a programmer, I just wasn't able to do much programming due to physical limitations. Admittedly I'm not much of a Python programmer, and I wouldn't be surprised if a deeper understanding of not-just-a-shell-script Python idioms helped me get a little more out of the REPL poking. But uh, still. As for Slack, I don't really consider that documentation. It's not really usable in the same way. It's more akin t…

> unofficially not much more than a few paragraphs There's a lot more than a few paragraphs on the wiki (which is linked right after the setup instructions in the official docs), including ~30 pages about the scripting system alone: https://talon.wiki/unofficial_talon_docs/ > As for Slack, I don't really consider that documentation I think you should try asking questions on this particular Slack before you write it o…

> There's a lot more than a few paragraphs on the wiki

You're right, I wasn't very fair to the wiki. I would have failed out way quicker without it. It wasn't intentional, it's just been a bit since I was looking at all this. My memory had dropped the details and left me with just my overall impressions.

That said, the wiki still was a bit short on some of the deeper details. I remember a fair number of places I'd feel like the wiki had just enough to tantalize the possibilities but not provide some of the important pieces to put it together into something useful.

And being community driven, I was a little wary of taking it as gospel. Even popular and stable software often has some niggling issues with community documentation.

> I think you should try asking questions on this particular Slack before you write it off

I'm not writing it off. I have no doubt it - and you - would be very helpful. I just don't consider it documentation, in the same way I don't consider a knowledgeable friend documentation.

Part of the reason I didn't pop in was that I was stuck doing a slow one-finger hunt-and-peck on a blank keyboard at the time. Searching the web was more than frustrating enough to make it real tempting to ignoring the cost of typing, never mind Slack. And partly I admit I just don't like asking questions in that format unless it seems like a reasonably complex/detailed/weird question.

> point VSCode at Talon's Python interpreter

Yeah, that probably would have helped. My setup at the time didn't have much for Python, so I was mostly using the REPL and basic searching.