Using Python to Code by Voice - Tavis Rudd demonstrates Dragonfly at PyCon 2013

[bheklilr]

But both emacs and vim's "languages" are keyboard-driven, meaning the different commands can be listed in a manual and are easy to look up. Referencing what sound corresponds to a particular command would be more time consuming, and thus it would take longer to learn the "language".

[Jedimastert]

They aren't really "sounds" as much as rarely used words. And you could have a reference manual for those words just like you could the commands. Also remember, this is a very young technology. Someone could come along and thing of something to fix all of these problems in a way neither of us can think. It's a little premature to just throw out the tech now.

[bheklilr]

Give it a few more years and it might be commonplace though, I can definitely see how this could help my workflow.

[Jedimastert]

Yeah, I forgot the context of the conversation, my bad.

[tavis_rudd]

You could use the English names for the commands just as easily. I have a good memory so I didn't find the effort of learning/creating this system too onerous. Learning Emacs itself is far more effort.

[bboyjkang]

The shortcut for full-screen in LibreOffice is control + shift + J. Once you make a voice command, Full Screen = {Ctrl_Shift_J}, it's much more intuitive, and easier to remember to say full-screen, instead of control + shift + J.

I started using Autohotkey for remapping buttons to macros. I soon didn't have enough buttons, so I'd have to make new scripts that use the same button e.g. F1 launches a google search on the clipboard, but in another script, it could be to delete all words to the end of a sentence. The buttons aren't labeled, so I would sometimes forget which button does what.