public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "Chris Peterson" <chrisp@citilink.com>
To: <blinux-list@redhat.com>
Subject: RE: emacspeak with the accent driver
Date: Mon, 29 Jun 1998 14:44:31 -0500	[thread overview]
Message-ID: <000701bda396$55e16a60$0f0962d1@newmicronpc> (raw)
In-Reply-To: <Pine.OSF.3.96.980630052128.14750B-100000@silas-2.cc.monash.edu.au>

cannot open doc string file "/usr/share/emacs/20.2/etc/DOC-20.2.1"

does anyone have any suggestions for me? I'm using redhat 5.1 if that
makes any difference.

Have you checked to varify the existance of this file?  Did you install
*all* of emacs?  Does emacs work when you run it by itself?

It sounds like the driver works just fine but you have some sort of problem
with the emacs install.

Chris


  reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nick Allan
 ` Chris Peterson [this message]
   ` wlestes
 ` Trevor Astrope
 ` wlestes
 ` James R. Van Zandt

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='000701bda396$55e16a60$0f0962d1@newmicronpc' \
    --to=chrisp@citilink.com \
    --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).