From: "T's Mailing Lists" <tpo2@spin.ch>
To: Kerry Hoath <kerry@gotss.ml.org>
Cc: blinux-list@redhat.com
Subject: Re: Emacspeak and w3
Date: Mon, 6 Jul 1998 17:18:37 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980706171240.30727A-100000@mail.spin.ch> (raw)
In-Reply-To: <19980706174404.48963@gotss1>
Emacspeak is in Debian-hamm!
I really can't tell you what you'll -exactly- need to have it runing, but
I guess you'll have to grab yourself libc6 from -bo- and maybe will have
to update all the emacs* stuff. Installing libc from bo shouldn't destroy
your system as libc5 and libc6 will be used in parallel.
But all the same, I have a system here somewhere between bo and hamm, and
it doesn't work -really- well any more - I had to backup several times. So
installing emacspeak from hamm -could- make your life easier, as other
people have sorted installation problems probably out for you, but be
cautious!
Good luck,
*
t
------------------------------------------------------------------------------
Tomas Pospisek - Freelance: Linuxing, Networking
http://spin.ch/~tpo/freelance
www.SPIN.ch - Internet Services in Graubuenden/Switzerland
WANTED: sysadmin-> http://spin.ch/~tpo/joboffer
------------------------------------------------------------------------------
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Kerry Hoath
` T. V. Raman
` T's Mailing Lists [this message]
` wlestes
` Dave Hunt
[not found] ` <Hkeo10r1JkIR089yn@ccs.covici.com>
` John Covici
` wlestes
` wlestes
` James R. Van Zandt
` wlestes
-- strict thread matches above, loose matches on Subject: below --
emacspeak " Tyler Spivey
screader : emacs speek : festival L. C. Robinson
` Jude Dashiell
` Emacspeak and W3 Bryan Smart
` Brian L. Sellden
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.3.96.980706171240.30727A-100000@mail.spin.ch \
--to=tpo2@spin.ch \
--cc=blinux-list@redhat.com \
--cc=kerry@gotss.ml.org \
/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).