From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Eli Zaretskii <eliz-mXXj517/zsQ@public.gmane.org>
Cc: 18563-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#18563: 24.3.93; Sound support on W32 Emacs
Date: Fri, 26 Sep 2014 11:35:07 +0200 [thread overview]
Message-ID: <867g0qohbo.fsf@somewhere.org> (raw)
In-Reply-To: <83tx3uu3oe.fsf-mXXj517/zsQ@public.gmane.org> (Eli Zaretskii's message of "Fri, 26 Sep 2014 12:33:21 +0300")
Eli Zaretskii wrote:
>> From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
>> Date: Fri, 26 Sep 2014 09:50:44 +0200
>>
>> When using the Tomatinho package, I had no sound after 25 minutes, as
>> expected.
>>
>> Trying to launch the sound file myself, I got:
>>
>> --8<---------------cut here---------------start------------->8---
>> Debugger entered--Lisp error: (error "This Emacs binary lacks sound support")
>> signal(error ("This Emacs binary lacks sound support"))
>> error("This Emacs binary lacks sound support")
>> play-sound((sound :file "tick.wav"))
>> play-sound-file("tick.wav")
>> eval((play-sound-file "tick.wav") nil)
>> eval-expression((play-sound-file "tick.wav") nil)
>> --8<---------------cut here---------------end--------------->8---
>>
>> Is this a limitation of Emacs on Windows, or a limitation in this binary?
>
> It's a regression that crept into the Windows build during development
> of v24.4. It is already fixed in the repository, so the next pretest
> will be able to play sound on Windows again.
OK, thanks for the information!
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-09-26 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 7:50 bug#18563: 24.3.93; Sound support on W32 Emacs Sebastien Vauban
2014-09-26 9:33 ` Eli Zaretskii
[not found] ` <83tx3uu3oe.fsf-mXXj517/zsQ@public.gmane.org>
2014-09-26 9:35 ` Sebastien Vauban [this message]
2014-09-26 9:34 ` Eli Zaretskii
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=867g0qohbo.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=18563-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
--cc=eliz-mXXj517/zsQ@public.gmane.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.