-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beeps? in this day and age? #158
Comments
I don't hear any beeps on Windows 7 in cmd.exe or powershell. |
Update: for the original reporter:
|
@200sc do you get a beep if you run |
No, it didn't beep for me cmd output if it matters:
|
False alarm, I had some bars in my audio mixer turned to zero-- I do get the single "should beep" beep from the test program. (also, butler upgrade dropped off a .gz file in my GOBIN but didn't extract the exectuable from it, so it looked like butler was broken, but that's on head, so) |
That sounds like what an older butler would've done - I've changed the upgrade mechanism at some point (it uses .zip now, as you can see from the output!). @200sc so beeptest beeps once, and |
That's correct. I can try other versions of butler if you'd like. |
Here's a test executable that, for me, on Windows 10:
The third beep is never heard - this is what butler uses as a prefix for tasks.
Attached is beeptest.exe, signed with our certificate. I'm curious how it behaves on Windows 7!
beeptest.zip
The text was updated successfully, but these errors were encountered: