From: Kei Kebreau <kkebreau@posteo.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 42861-done@debbugs.gnu.org
Subject: bug#42861: emacspeak won't shut up about TTS sync states
Date: Wed, 21 Apr 2021 21:44:48 +0000 [thread overview]
Message-ID: <ce25a8cc-c8de-f6a3-aaa5-7e99898360a6@posteo.net> (raw)
In-Reply-To: <87czvcsq4e.fsf@nicolasgoaziou.fr>
On 4/2/21 10:44 AM, Nicolas Goaziou wrote:
> Hello,
>
> Kei <kkebreau@posteo.net> writes:
>
>> 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".
> On Debian, the voice kicks in after all the initial minibuffer
> information is displayed, i.e., it starts when it is actually ready. On
> Guix, see below.
>
>>> 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?
> It is, but I am speaking at the initial messages, when you start a fresh
> Emacs session.
>
> Regards,
I've pushed the patch as-is to master. If you are able to provide a
method to replicate the issues you speak of here, please message me and
we can open a bug report.
Thanks,
Kei Kebreau
next prev parent reply other threads:[~2021-04-21 21:46 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
2021-04-02 14:44 ` Nicolas Goaziou
2021-04-05 14:02 ` Kei
2021-04-21 21:44 ` Kei Kebreau [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce25a8cc-c8de-f6a3-aaa5-7e99898360a6@posteo.net \
--to=kkebreau@posteo.net \
--cc=42861-done@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.