From: Stefan Kangas <stefankangas@gmail.com>
To: Daniel Semyonov <daniel@dsemy.com>
Cc: Richard Stallman <rms@gnu.org>,
iarchivedmywholelife@gmail.com, emacs-devel@gnu.org
Subject: Re: Vendoring code in a (Non?)GNU ELPA package
Date: Wed, 10 Jan 2024 04:07:29 -0800 [thread overview]
Message-ID: <CADwFkmkT-o7QDo1c40YKZVYggQyP=7Pe0cpeQwbfkjnfw+Ov=Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmktaVCA4bf8HXwECarAGtUCu07wsgGGiQ0WUH62j4X21w@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> Though, on the face of things, I don't think I understand why
> `play-sound` should block. Is there a good reason for that, or is it
> just an implementation accident? And are there any important reasons
> to preserve its blocking behavior?
I'm answering myself here:
Jan Djärv <jan.h.d@swipnet.se> writes:
> It would be better if all sound implementations where asynchronous and
> quittable.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3351#19
next prev parent reply other threads:[~2024-01-10 12:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 9:07 Vendoring code in a (Non?)GNU ELPA package Daniel Semyonov
2023-12-29 3:53 ` Richard Stallman
2023-12-29 4:14 ` No Wayman
2023-12-31 3:15 ` Richard Stallman
2024-01-01 3:37 ` Dmitry Gutov
2024-01-04 3:59 ` Richard Stallman
2024-01-01 12:07 ` Daniel Semyonov
2024-01-03 4:14 ` Richard Stallman
2024-01-03 6:20 ` Daniel Semyonov
2024-01-04 4:56 ` Stefan Kangas
2024-01-04 15:02 ` Daniel Semyonov
2024-01-05 20:10 ` Stefan Kangas
2024-01-06 10:52 ` Daniel Semyonov
2024-01-06 11:45 ` Stefan Kangas
2024-01-06 19:04 ` No Wayman
2024-01-08 3:46 ` Richard Stallman
2024-01-08 4:00 ` No Wayman
2024-01-10 12:07 ` Stefan Kangas [this message]
2024-01-06 4:35 ` Richard Stallman
2023-12-29 7:57 ` Daniel Semyonov
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='CADwFkmkT-o7QDo1c40YKZVYggQyP=7Pe0cpeQwbfkjnfw+Ov=Q@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=daniel@dsemy.com \
--cc=emacs-devel@gnu.org \
--cc=iarchivedmywholelife@gmail.com \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.