public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Ricki Voyles <rvoyles@mailbox.arn.net>
To: blinux-list@redhat.com
Subject: Emacs, Eterm, and Emacspeak
Date: Tue, 23 Jun 1998 17:41:09 -0500	[thread overview]
Message-ID: <3.0.3.32.19980623174109.0079b4a0@mailbox.arn.net> (raw)

   Hello, all.  I've recently installed Slakware 3.0.4 on my new machine.
Unfortunately, I encountered the same problem I had on my old linux box.  
   I installed gnu emacs 20.2 and emacspeak 8.0.  When I pressed ctrl-e
ctrl-r to run the command emacspeak-eterm-remote-term, I was given the
error: unable to open tshell. 
   I have discovered that tshell is a part of eterm, and I assumed that
eterm was part of emacs.  However, it was not included in the package I
installed.  Can anyone tell me the relationship between eterm and emacs? 
Thanks in advance. 

Ricki

P.S.  My primary objective  is to be able to telnet in to a bash shell from
emacs and have speech there.  Am I going about this the right way?     


             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ricki Voyles [this message]
 ` T. V. Raman

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=3.0.3.32.19980623174109.0079b4a0@mailbox.arn.net \
    --to=rvoyles@mailbox.arn.net \
    --cc=blinux-list@redhat.com \
    /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).