From: Kei <kkebreau@posteo.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 42861@debbugs.gnu.org
Subject: bug#42861: emacspeak won't shut up about TTS sync states
Date: Thu, 01 Apr 2021 23:00:59 -0400 [thread overview]
Message-ID: <203c61c9a4fd32c7f663dd6cce051de69870eebb.camel@posteo.net> (raw)
In-Reply-To: <87ft0ahvk0.fsf@nicolasgoaziou.fr>
On Thu, 2021-04-01 at 17:30 +0200, Nicolas Goaziou wrote:
> Hello,
>
> Kei <kkebreau@posteo.net> writes:
>
> > Sorry it took me a while to respond. I don't actively use the openmailbox
> > email
> > account anymore. Please try this patch when you can. The sounds don't
> > quite
> > work like they do on Debian yet, but at least emacspeak doesn't go on and on
> > about the TTS sync state and such.
>
> This is much better indeed. Thank you.
>
My pleasure!
> On Debian espeak seems to be activated after loading ".emacs" file.
How are you able to tell (aside from looking at the command line arguments)?
I'm unable to distinguish the startup processes using Emacs on Debian and Guix
even if I install "etc/emacspeak.sh" as the startup script instead of "run".
> Here, the package spells out all configuration messages displayed on in
> the minibuffer.
>
Unless I'm misunderstanding you, Emacspeak seems to do the same for me on
Debian. For example, it reads "Active processes exist?..." and so on when
exiting. Is this not proper behavior?
Thanks,
Kei
next prev parent reply other threads:[~2021-04-02 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 15:47 bug#42861: emacspeak won't shut up about TTS sync states Christopher Lemmer Webber
2021-03-29 3:41 ` Kei
2021-04-01 15:30 ` Nicolas Goaziou
2021-04-02 3:00 ` Kei [this message]
2021-04-02 14:44 ` Nicolas Goaziou
2021-04-05 14:02 ` Kei
2021-04-21 21:44 ` Kei Kebreau
2021-04-21 23:39 ` Nicolas Goaziou
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=203c61c9a4fd32c7f663dd6cce051de69870eebb.camel@posteo.net \
--to=kkebreau@posteo.net \
--cc=42861@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).