Moin moin, =- Eric S. Johansson wrote on Sun 8.Jul'12 at 3:23:11 -0400 -=
> It would be super superb if I could use some form of client-side > editing for sieve filtering but, nonessential. Not supported yet, and probably never, since there are other/better ways?! > I need to turn off every single bit of command by keystroke. The > reasons is simple. If you're using speech recognition and you get > a misrecognition instead of command, think what happens your mail > buffer if three or four "random" words were dumped into mutt. Not sure how the interaction works in detail, but can't you insert some "buffer" between voice capture and passing to mutt interpretation, like have it re-read for you what you said before it sends, so you can approve it? Maybe you need another tool-layer between, which provides input-control. Could then applied with other tools, too. > So the answer is turned off single character commands either > permanently or between detection of utterance and end of > utterance. No, this would possbily be even the job of the terminal?! > The second thing I would need is the ability to query internals of > Mutt so I can construct a context dependent grammars that can be spoken. What kind of "internals"? -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
