From: "Tyler Spivey" <tspivey8@softhome.net>
To: speakup@braille.uwo.ca
Subject: bug in cvs speakup
Date: Mon, 15 Sep 2003 13:14:40 -0700 [thread overview]
Message-ID: <000f01c37bc5$ffc8cf70$5c1917cf@130SetBC01> (raw)
hey. there is a minor bug in cvs speakup, i just got it a few days ago. the
double-say-line function (i believe it's called speakup_say_indennt)
is off by one space. if there is not indent, for example on the line:
this is a test
it will say "1 this is a test." i believe this is caused by a +1 in the
code, and it just seems weird. i believe the expected behaviour is to say
"0" for no indent.
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000f01c37bc5$ffc8cf70$5c1917cf@130SetBC01' \
--to=tspivey8@softhome.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).