You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a point mentioned in a YouTube video by @NapoleonWils0n, first brought to my attention in issue #5. In the video, plain URLs are inserted in the message body, but a better way to communicate URLs would be to use XML-based markup. Unfortunately, EDNC currently doesn't do any parsing of notification bodies at all (which is allowed by the standard as long as it doesn't claim to be able to do so).
Either way, notifications from Firefox commonly open an URL as their default action, so I don't know how pressing of an issue it really is.
The text was updated successfully, but these errors were encountered:
As a workaround, the following will automatically highlight all URLs in ednc-view-mode:
(add-hook'ednc-view-mode-hook#'goto-address-mode)
I'm wary of adding this to EDNC, however, because if markup parsing is implemented at some point, it might interfere with goto-address-mode (e.g., if the text contains one URL, but the href another).
This is a point mentioned in a YouTube video by @NapoleonWils0n, first brought to my attention in issue #5. In the video, plain URLs are inserted in the message body, but a better way to communicate URLs would be to use XML-based markup. Unfortunately, EDNC currently doesn't do any parsing of notification bodies at all (which is allowed by the standard as long as it doesn't claim to be able to do so).
Either way, notifications from Firefox commonly open an URL as their default action, so I don't know how pressing of an issue it really is.
The text was updated successfully, but these errors were encountered: