Open bpsib opened 4 years ago
In fact, because of this, termux-notification strictly requires specifying an id for ongoing notifications. For regular notifications, however, the id is not strictly required because if you foresee that you will want to remove a notification in the future, you will naturally specify an id when creating it.
Perhaps you want to interact with notifications not generated by termux-notification?
On Fri, Oct 18, 2019, 20:16 bpsib notifications@github.com wrote:
I have found a really annoying problem with the termux-notification-remove command. It requires the id parameter yet the termux-notification command doesn't. This means there's no way of removing a notification with the
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/termux/termux-api-package/issues/85?email_source=notifications&email_token=AD6X32XSDDW2VTMB64CO2D3QPH4PJA5CNFSM4JCKYIPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HS2LX4A, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6X32QV7LS4JMHSYLCRNKLQPH4PJANCNFSM4JCKYIPA .
I have found a really annoying problem with the termux-notification-remove command. It requires the id parameter yet the termux-notification command doesn't. This means there's no way of removing a notification with the termux-notification-remove command if an id wasn't specified.