From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: making speakup speed up
Date: Thu, 21 Aug 2008 12:54:11 -0700 [thread overview]
Message-ID: <20080821195411.GA25895@localhost.localdomain> (raw)
In-Reply-To: <20080821193759.GB6830@clearwire.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Aug 21, 2008 at 12:37:59PM -0700, Gaijin wrote:
> Thought there was only a changelog file available, and only if
> you did a git pull of the source. <grins>
No, there is also the speakup user's guide available under
doc/spkguide.txt in the speakup directory, provided you do a git-clone
first. I do stand corrected though, I should have taken a look at
the user's guide on the site, though I still think it was reasonable
to assume that the user's guide from git, and the one on the site
would be the same. While spkguide.txt on
linux-speakup.org, and spkguide.txt in the doc directory of the
speakup tree both have the same last modified date, the spkguide.txt
in the speakup tree is updated to reflect the changes made in speakup
from git. Michael already gave you what you need to know, so I'm not
going to paste the info from the updated spkguide.txt here.
> This, Gregory, is an example of helpful information, and not
> useless, wasted bandwidth that doesn't even provide a URL for this
> "Users Guide" you assume everyone knows about.
Tyler has been on this list long enough, that he should have seen
linux-speakup.org being mentioned here more than once. Even if someone
doesn't know where to start looking for the user's guide,
linux-speakup.org is a good place to start, and at least the
slightly out-dated copy would have been discovered as the 4th link on
that page. In the case of a newby, there is a chance that they would
have heard of linux-speakup.org, though if someone posting here for
the first time had asked what Tyler had asked, I would have given a
quick overview, like you had done, in addition to telling them where
to find the user's guide.
So, I think that in Tyler's case, as someone who has been here for a
while, the information you termed as being unhelpful, was a valid
starting point.
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkitx+MACgkQ7s9z/XlyUyBK/gCglpT/XahEM5r5vOGnngusxPwd
U68AoKPHKKKZkKgCOfuys56yLypGqdot
=0MNX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Littlefield
` Tyler Littlefield
` Tony Baechler
` Gregory Nowak
` Tyler Littlefield
` Gregory Nowak
` Gaijin
` Tyler Littlefield
` Gregory Nowak [this message]
` Tony Baechler
` Samuel Thibault
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=20080821195411.GA25895@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).