bug: notifications spam #106
Labels
No labels
bug
ci
documentation
duplicate
enhancement
feature
good first issue
help wanted
invalid
performance
priority
P0
priority
P1
priority
P2
question
refactor
size
L
size
M
size
S
size
XL
size
XS
tests
trivial
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
noe.trevino/paso#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Did you check docs and existing issues?
Paso version (paso -v)
N/A
Operating system/version
Arch Linux
Describe the bug
Rapid key-repeat at a boundary (e.g., holding left arrow at column 0) now fires addNotification on every key event, spawning a new tea.Tick timer each time and pushing duplicate notifications into the stack (capped at 3, then evicting). The previous Clear() on each keypress made this idempotent. Consider deduplicating: skip adding if the top notification has the same message, or check before calling addNotification.
Steps To Reproduce
hold left or right
Acceptanced Criteria
notifications should be added and handled more gracefully in general.
Set like behavior
Potential cause
No response