From: Zachary Kline <klinez@onid.orst.edu>
To: speakup@braille.uwo.ca
Subject: Mutt and speech
Date: Sun, 20 Apr 2008 20:32:19 -0700 [thread overview]
Message-ID: <20080421033219.GA16420@babel.localdomain> (raw)
Hi,
I'm quickly learning to really enjoy Mutt.
It works pretty nicely with my various speech systems as is, but I was wondering
as to other people's experiences. Are there any features I should avoid for accessibility reasons?
I like being able to customize it, but the sheer number of options is daunting..
.
Any tips from more advanced users on this list?
Thanks,
Zack.
next reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline [this message]
[not found] ` <20080421052157.GA17892@clearwire.net>
` Gaijin
` Tyler Spivey
` Ralph W. Reid
` Ralph W. Reid
` Steve Holmes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080421033219.GA16420@babel.localdomain \
--to=klinez@onid.orst.edu \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).