From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Help the Floundering Newbie!
Date: Wed, 23 May 2001 09:46:50 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0105230940070.13511-100000@ignatious> (raw)
In-Reply-To: <x7bsok5f5s.fsf@speech.braille.uwo.ca>
I think the first order of business is to put things back into
perspective.
If you want to work with the console for the development, then procure one
machine for your development activities. This is a good idea anyway. All
of the software mentioned can be installed on your development machine
with no monetary investment beyond the hardware it is running on. Then you
can code with emacspeak. You can code in pico with speakup. Or you can ask
Kirk and some others what they use for development.
The thing is that developing code for a Linux box can easily be done with
whatever you prefer to use. You could write code for your linux machine in
notepad on a windows machine.
If a person comes with a strong unix background then moving to development
on a linux machine should be an easy enough thing to do. Most of those
same tools used before can be used here.
=======
Kirk Wood
Cpt.Kirk@1tree.net
Nothing is hard if you know the answer or are used to doing it.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
w3 not working Gregory Nowak
` Victor Tsaran
` Janina Sajka
` Victor Tsaran
` Gregory Nowak
` Help the Floundering Newbie! rjc
` Kirk Wood
` Victor Tsaran
` Kirk Reiser
` Charles Hallenbeck
` speech for coding Raul A. Gallegos
` Rich Caloggero
` Geoff Shang
` Kirk Wood [this message]
` Help the Floundering Newbie! Victor Tsaran
` Geoff Shang
` w3 not working Victor Tsaran
Help the Floundering Newbie! Holmes, Steve
` Victor Tsaran
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.4.21.0105230940070.13511-100000@ignatious \
--to=cpt.kirk@1tree.net \
--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).