From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: Looking for Emacspeak users
Date: Tue, 4 Feb 2020 18:13:43 -0600 [thread overview]
Message-ID: <2912b235-d91d-7e9e-7f20-67c96e0b77fe@gmail.com> (raw)
In-Reply-To: <bc9ce353-0b50-f93e-345f-c9d53da80968@gmail.com>
I'm an Emacspeak user, so ask away or join the Emacspeak list. BTW, I
use the same TTS for Emacspeak that I use for Orca, which is eSpeak. I
don't have a separate TTS just for Emacspeak.
On 2/4/20 10:01 AM, Linux for blind general discussion wrote:
> Hello
>
>
> I have Several years curious about emacspeak.
>
> I tried it out in a raspberry pi, but regarding it needs its own TTS
> engine whuich I was not able to configure in those times.
>
>
> I would like to contact emacspeak users in linux to discuss about what
> can I do in that environment and how versatile it is.
>
>
> Thanks
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
--
Christopher (CJ)
Chaltain at Gmail
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
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=2912b235-d91d-7e9e-7f20-67c96e0b77fe@gmail.com \
--to=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).