Skip to content

fix(excmds): clear excmd misuse notification after successful execution#205

Open
suveshmoza wants to merge 1 commit intoglide-browser:mainfrom
suveshmoza:fix/excmd-notification-clr-on-success
Open

fix(excmds): clear excmd misuse notification after successful execution#205
suveshmoza wants to merge 1 commit intoglide-browser:mainfrom
suveshmoza:fix/excmd-notification-clr-on-success

Conversation

@suveshmoza
Copy link
Copy Markdown
Contributor

@suveshmoza suveshmoza commented Jan 1, 2026

Closes #195

  • Added notification cleanup logic when command is not one of commandline.
  • Updated TabsCompletionSource to handle both tab and tab <index> scenarios.
    • For tab we rely on the tabs selected by the user from completion list.
    • For tab <index> we pass it to GlideExcmds.execute to handle both execution and notification cleanup.
  • Added test cases covering different scenarios for various commands.

@suveshmoza suveshmoza force-pushed the fix/excmd-notification-clr-on-success branch 2 times, most recently from 2900123 to 40d1ce8 Compare January 3, 2026 10:13
@suveshmoza suveshmoza force-pushed the fix/excmd-notification-clr-on-success branch from 40d1ce8 to bba80f8 Compare January 9, 2026 14:56
@suveshmoza suveshmoza force-pushed the fix/excmd-notification-clr-on-success branch from bba80f8 to e1ed3ec Compare February 27, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clear excmd misuse notification errors after executing successfully

1 participant