public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: speakup@linux-speakup.org
Subject: Re: Anybody still use YASR
Date: Wed, 24 Aug 2016 05:58:14 -0700	[thread overview]
Message-ID: <87vayq5no9.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160824124343.GF31116@katolaz.homeunix.net> (katolaz@freaknet.org's message of "Wed, 24 Aug 2016 13:43:43 +0100")

KatolaZ <katolaz@freaknet.org> writes:

> Thanks Jude,
>
> the problem is that emacspeak pulls in ways too much for a minimal
> live distro, except we stick to emacs-nox, which might be easy to
> include and just enough for the task. Would it make sense to try to
> include emacs-nox, emacspeak, and eflite in Devuan minimal live then?
> If yes, I will put it in the todo list :)

You know what?  The Emacspeak espeak server also works with yasr, and it
can be built independently of the rest of Emacspeak.  The only
dependencies it pulls are tcl, tclx, and espeak.  I think this is like 5
or 6 megs, not including espeak.
You're already pulling in espeak,, so tcl and tclx aren't such a big
deal, I think.
Problem is, the espeak server isn't packaged separately in Debian, even
though it can be built separately.
Anyway, Emacspeak itself is just fine with emacs-nox.

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline
 ` Brian Buhrow
 ` Littlefield, Tyler
   ` Hart Larry
     ` Zachary Kline
 ` Jude DaShiell
   ` KatolaZ
     ` Jude DaShiell
       ` KatolaZ
         ` Gregory Nowak
           ` KatolaZ
             ` Gregory Nowak
         ` Jude DaShiell
           ` KatolaZ
             ` Chris Brannon [this message]
               ` Jude DaShiell
               ` KatolaZ
             ` Jude DaShiell
               ` Alonzo Cuellar
 Mike Keithley
 ` Zachary Kline

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=87vayq5no9.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.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).