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

RuntimeError: Failed to beep when running Python in ConEmu #999

Open
prahladyeri opened this Issue Jan 3, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@prahladyeri

prahladyeri commented Jan 3, 2017

Hello Folks,

Wish you a belated Happy New year, and thanks a lot for building this wonderful console emulator. I faced a very small bug today, though. As it happens, I was writing a small time-tracking script in Python when I came across this bug:

Problem description

Runtime error occurs when trying to use the winsound.Beep class in the Python emulator. This only happens when using ConEmu, not the usual cmd.exe.

Steps to reproduce

  1. Start ConEmu, then start Python Emulator.
  2. Run the following code:
import winsound
winsound.Beep(400,500)

Actual results

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
RuntimeError: Failed to beep

Expected results

The beep sound must occur.

Additional Details

Here is the link to a similar issue in cmder, one of your derivative projects. I don't understand why that issue was closed, maybe it might have resolved on cmder, but still pending on ConEmu?

Python version: 3.6.0
ConEmu version: ConEmu-Maximus5

Thanks,
Prahlad

@minexew

This comment has been minimized.

Show comment
Hide comment
@minexew

minexew Jan 10, 2017

It was closed in cmder precisely because it's an upstream ConEmu issue :)

minexew commented Jan 10, 2017

It was closed in cmder precisely because it's an upstream ConEmu issue :)

@prahladyeri

This comment has been minimized.

Show comment
Hide comment
@prahladyeri

prahladyeri Jan 10, 2017

@minexew Even if its an upstream issue, its a good idea to keep the issue open until upstream resolves it, isn't it? I don't know much as I'm quite new to open source development.

BTW, has this issue been resolved in ConEmu in any recent versions or not?

prahladyeri commented Jan 10, 2017

@minexew Even if its an upstream issue, its a good idea to keep the issue open until upstream resolves it, isn't it? I don't know much as I'm quite new to open source development.

BTW, has this issue been resolved in ConEmu in any recent versions or not?

@minexew

This comment has been minimized.

Show comment
Hide comment
@minexew

minexew Jan 10, 2017

Yeah, it probably would've been better to keep it open

minexew commented Jan 10, 2017

Yeah, it probably would've been better to keep it open

@xulfir

This comment has been minimized.

Show comment
Hide comment
@xulfir

xulfir Jul 31, 2017

Seems like it's a feature. To disable: Settings > Features > In-console options > uncheck "Suppress bells"

xulfir commented Jul 31, 2017

Seems like it's a feature. To disable: Settings > Features > In-console options > uncheck "Suppress bells"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment