-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apprise Notification linebreak #33
Comments
The people who created this aren't involved anymore, so I cant tell for sure, but I doubt this So I'm unsure on how to label this as a bug or a feature request 🤡 |
Since I brought this up: my understanding is that markdown doesn't support forced line breaks. Hence, it is a feature, not a bug. 😉 A linebreak can be used by adding a prefix of two spaces to a new line - which can't work if you just have one line. While I would very much appreciate if it would be possible to add a line break for (e.g., telegram) notifications, I don't think think this should be a priority. |
It's not an bug at all
I have markdown disabled and it doesn't work It works with just one line, as you can see in my screenshot. It's not a priority by any means. Edit:
|
Lines breaks for notification (in this case it's telegram) don't work as they should.
Test message is fine, normal operation is not.
Example, this is how it's set up normally:

Ein/e $comname ($sciname) wurde soeben erkannt. Erkennungswahrscheinlichkeit $confidencepct%
Looks like this:
Code for break-line <> , /n , %0A or whatever the server wants for a break
Ein/e $comname ($sciname) wurde soeben erkannt. %0AErkennungswahrscheinlichkeit $confidencepct%
This is how it's supposed to look like (send with "test notification" button)

Same break line

%0A
How it actually comes out:
If I have the time (can be weeks to months) I can handle it. Though I would be glad if someone else can look at it.
Maybe it's an issue with apprise? (I don't think so)
Ursprünglich gepostet von @MueJosh in #26 (comment)
The text was updated successfully, but these errors were encountered: