From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup and hald conflict in Slackware 12.2
Date: Mon, 15 Dec 2008 20:04:22 -0700 [thread overview]
Message-ID: <20081216030422.GA25596@localhost.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.0812152042520.3119@dell.bellsouth.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Dec 15, 2008 at 08:49:13PM -0600, Adam Myrow wrote:
> Also, I noticed that speakupconf doesn't work correctly. The command
> "speakupconf save" gives an error "cp: omitting directory `.'" Running
> speakupconf load, returns "cat: write error: Invalid argument."
Yes, I noticed this too when trying to use the speakupconf in the
contrib directory from the git tree. I had a look at the speakupconf
file from git, and the one I used to use, but saw no obvious
differences, other than the copyright line 2008 by Steve in the newer
speakupconf. So, I went back to the speakupconf I used to use. It
loads fine, but has a problem with saving.
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)
iEYEARECAAYFAklHGrYACgkQ7s9z/XlyUyBeugCgpKUML97pr96L064rtr+MVXpj
cmgAn3aa0tvfxKuBtBMtPZWn4EunhGbq
=hbS9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` Igor Gueths
` Gregory Nowak
` Michael Whapples
` Adam Myrow
` Adam Myrow
` Gregory Nowak [this message]
` Zachary Kline
` Gregory Nowak
` Zachary Kline
` Garrett Klein
` Gregory Nowak
` Alex Snow
` Zachary Kline
` Alex Snow
` Zachary Kline
` Alex Snow
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=20081216030422.GA25596@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).