From: "Victor Tsaran" <vtsaran@nimbus.ocis.temple.edu>
To: <speakup@braille.uwo.ca>
Subject: Re: new user with slackware questions
Date: Sun, 10 Sep 2000 19:32:12 -0700 [thread overview]
Message-ID: <000101c01bb6$0b169100$70e5f79b@wang> (raw)
In-Reply-To: <20000910152503.A7381@flite.net>
Actually, you might want to leave the TCL packages if you will plan later on
trying Emacspeak.
Regards,
Vic
----- Original Message -----
From: "Tommy Moore" <stp@odysseus.yi.org>
To: <speakup@braille.uwo.ca>
Sent: Sunday, September 10, 2000 12:25 PM
Subject: Re: new user with slackware questions
> Actually just check the a ap d e f k and n sections of the slackware
install.
> The t and tcl and y sets aren't really needed uless you want them.
>
> Tommy.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Reinhard Stebner
` Victor Tsaran
` Reinhard Stebner
` Victor Tsaran
` Tommy Moore
` Victor Tsaran [this message]
` Reinhard Stebner
` Victor Tsaran
` Reinhard Stebner
` Tommy Moore
` Scott Howell
` Reinhard Stebner
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='000101c01bb6$0b169100$70e5f79b@wang' \
--to=vtsaran@nimbus.ocis.temple.edu \
--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).