From: <cpt.kirk@1tree.net>
Cc: speakup@braille.uwo.ca
Subject: Re: braille input
Date: Fri, 10 Mar 2000 17:44:10 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10003101742340.3489-100000@rocky> (raw)
In-Reply-To: <Pine.LNX.4.21.0003101821410.1795-100000@sajka.bellatlantic.net>
I agree that it would be easy to flip the braille. But often times the
obvious gets left out of software. The list of easy to implement options
that were left out is too long as it is. i am just stating up front, that
I feel it best to implement the option. I wouldn't care to hear from the
guy who is peeved at not having such an easy to implement option.
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Your fly might be open (but don't check it just now).
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
cpt.kirk
` Janina Sajka
` cpt.kirk [this message]
` Janina Sajka
` cpt.kirk
` scott howell
` Janina Sajka
` cpt.kirk
` craig martin
` craig martin
` Buddy Brannan
` Janina Sajka
` Buddy Brannan
` scott howell
` cpt.kirk
` Chuck Hallenbeck
` cpt.kirk
` Chuck Hallenbeck
` Janina Sajka
` craig martin
[not found] <00c901bf8b7b$d262ecc0$7778f5cd@n6m3o7>
` Janina Sajka
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=Pine.LNX.4.10.10003101742340.3489-100000@rocky \
--to=cpt.kirk@1tree.net \
--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).