Discord parser behaves weirdly on strings that begin with "Input #"

echo 'Input #0,string string string \nsometext \nsomemoretext \nmoretext \nwaymoretext\nInput #1 \nanothertext' | apprise -t 'T E S T !' "discord://<name>@<hookID>/<token>/?avatar=off&thumbnail=off"

results in the following… it appears like it parses from one Input to another. E.g. “somemoretext” and “moretext” and “wamoretext” are all being discarded.

[TildeSlashC0re]

Finally found some time to give this a go … and it’s beautiful! Works as intended and can be merged for all I care 😄.

closing this now. thanks for the quick solution once again.

[caronc]

I could have sworn i fixed this; the output you’re seeing will definitely be present in the master branch, but it shouldn’t be in this one. I can clearly see the markdown being set in your screenshot; but now that should only trigger if one adds ?format=markdown in the URL which i presume you’re not doing.

I’ll re-investigate this later and keep you posted.

That being said it would be nice if apprise would inform you of any errors thrown right away instead of the user having to rely on an -verbose switch 😃

This is great feedback. I personally always enjoyed silence from shell commands unless I ask for noise. I rarely throw errors in apprise because if a notification fails, i just move onto the next (but i’m sure to return a non-zero value in the response). But i do respect that when something doesn’t work, i need to go back and add -vvv to the output which probably isn’t the most intuitive approach.