From: Chuck Hallenbeck <chuckh@ftml.net>
To: pj@pjb.com.au,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: Progress reports
Date: Wed, 1 Dec 2010 06:30:26 -0500 [thread overview]
Message-ID: <20101201113026.GA6540@rx.localhost> (raw)
In-Reply-To: <99j320$5lpj17@ipmail06.adl2.internode.on.net>
On Wed, Dec 01, 2010 at 03:41:45PM +1000, pj@pjb.com.au wrote:
> True. But, being a newbie, naively reasoning that since this is
> a computer it might as well do it automatically, I've written
> a little Perl script: http://www.pjb.com.au/blin/free/quiet
> Documentation: http://www.pjb.com.au/blin/quiet.html
>
Very nice. I haven't tried it yet, but it does look interesting. Is the
default for ln to make hard links or soft? Would either style work in
this setup?
Chuck
--
The Moon is Waning Crescent (22% of Full)
Website: hallenbeck.ftml.net, Jabber ID: chuckh1@jabber.org
--------
You're not an alcoholic unless you go to the meetings.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
pj
` Chuck Hallenbeck [this message]
` Gregory Nowak
` Zachary Kline
-- strict thread matches above, loose matches on Subject: below --
pj
pj
` Chuck Hallenbeck
` Frost
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=20101201113026.GA6540@rx.localhost \
--to=chuckh@ftml.net \
--cc=pj@pjb.com.au \
--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).