Terminology flood on terminal should be limited #2
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: enlightenment/terminology#2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sometimes my terminology triggers a kind of bottlenecked state, for example; if you run "diff" between two binary files it will trigger a ton of "bells", bottlenecking a bit your computer (even your playing music stops for a few seconds) I assume because of the amount of jobs started to run this code
I think it should have a limit of amounts of bells per microsecond or something like that