Skip to content
This repository has been archived by the owner on Aug 2, 2020. It is now read-only.

Hadrian triggers annoying bell/urgency terminal signals #467

Open
hvr opened this issue Nov 16, 2017 · 2 comments
Open

Hadrian triggers annoying bell/urgency terminal signals #467

hvr opened this issue Nov 16, 2017 · 2 comments

Comments

@hvr
Copy link
Contributor

hvr commented Nov 16, 2017

I've been running hadrian/build.sh in a terminal now, and the terminal where it's running keeps requesting my attention since hadrian annoyingly seems to emit bell/urgency hints every couple of seconds while the build runs, which cause my terminal to flash & make sounds in order to get my attention; this is very distracting and seems rather useless. I'm not sure what causes this signals to be emitted, but I think it's quite obvious to everyone this is a very undesirable default setting to have the build process ring the bell frequently to let you know it's still running... ;-)

PS: This reminds me of GHC's GC feature which would ring a bell everytime a major(?) GC was performed... for some reason people didn't want that enabled by default either ;-)

@ndmitchell
Copy link
Collaborator

It will be a mistake in the progress reporting piece almost certainly. Does his happen for everyone or does @hvr have special terminal settings.

For info, I once caused a floor of 40 machines in an open plan office to beep every 1s for 40 minutes. That was a screw up in shake progress reporting that didn’t go down well...

@snowleopard
Copy link
Owner

@hvr That sounds annoying!

Does his happen for everyone or does @hvr have special terminal settings.

I did notice that the MSYS terminal window occasionally flashes to require my attention. I was wondering why this happens too.

PS: This reminds me of GHC's GC feature which would ring a bell everytime a major(?) GC was performed... for some reason people didn't want that enabled by default either ;-)

For info, I once caused a floor of 40 machines in an open plan office to beep every 1s for 40 minutes. That was a screw up in shake progress reporting that didn’t go down well...

🌶️

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants