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
The usage message on the command line mentions that in some cases the first character of the message needs to be escaped (but only mentions open bracket as one of those characters- the less-than character is another one). The command fails in those cases if message is not escaped.
I've found similar behavior with title and subtitle, although for those, the notification does get made, with those fields simply missing.
I'm seeing that simply adding a \ as the first character of the title, subtitle, or message, regardless of what follows, is suitable. However, if using an environment variable instead of literal text, the $ is what gets escaped, and is included as a literal $. Using a double backslash, \, prevents that, and also works for literal text.
Given this behavior, at the very least, mention should be made in the README of it somehow. Or better, tweak the code as needed (adding the ?). I'd be happy to submit a PR with a README addition if desired, but am not familiar enough with the code, or Ruby, to dig in there.
I bring this up because I was having issues when the first character happened to be a <.
The text was updated successfully, but these errors were encountered:
The usage message on the command line mentions that in some cases the first character of the message needs to be escaped (but only mentions open bracket as one of those characters- the less-than character is another one). The command fails in those cases if message is not escaped.
I've found similar behavior with title and subtitle, although for those, the notification does get made, with those fields simply missing.
I'm seeing that simply adding a \ as the first character of the title, subtitle, or message, regardless of what follows, is suitable. However, if using an environment variable instead of literal text, the $ is what gets escaped, and is included as a literal $. Using a double backslash, \, prevents that, and also works for literal text.
For example:
Returns error message:
Works as expected:
Puts up notification, ignoring title (or subtitle, if done with subtitle instead of title):
Works as expected:
Given this behavior, at the very least, mention should be made in the README of it somehow. Or better, tweak the code as needed (adding the ?). I'd be happy to submit a PR with a README addition if desired, but am not familiar enough with the code, or Ruby, to dig in there.
I bring this up because I was having issues when the first character happened to be a <.
The text was updated successfully, but these errors were encountered: