using debug in conjunction with the configuration option 'ask' results in screens of information which can result in prompts scrolling off the screen

I'm a big fan of Beets but sometimes it doesn't do what I expect. When that is the case I normally run it with -vvv to get debug.

When I do that any console prompt scrolls off the screen and is lost forever and seems looks like it is frozen when it is waiting for input from 15 pages of debug ago.

I think I'm saying that because beets is multithreaded all prompts should be suppressed until all threads associated with the release have completed.

Am I making sense or being backwards ? input appreciated.

Reproduce the issue by running beets with -vvv while the `ask` configuration option triggers a console prompt. Start by tracing the prompt handling alongside the multithreaded release work. Done means prompts remain visible and usable instead of being buried under debug output.

Written by the indexing model from the issue text.