telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.29k stars 5.22k forks source link

Inline bots and ```blocks of code``` markdown #2421

Closed zhkvia closed 8 years ago

zhkvia commented 8 years ago

Steps to reproduce

  1. Send to @bold (or any other inline bot supporting markdown) message like this:

```word1 word2```

  1. Select custom markdown in @bold's options list

    Expected behaviour

@bold bot sends markdown-rendered message with all words appeared in input

Actual behaviour

The first word of the message disappears in resulting answer.

Configuration

Operating system: OS X

Version of Telegram Desktop (Qt version): 0.10.1

auchri commented 8 years ago

Seems to be an api issue, the same is happing on the android version. /cc @john-preston

john-preston commented 8 years ago

@auchri Or maybe a bot bug.

zhkvia commented 8 years ago

@john-preston what do you mean by saying "bot problem": only @ bold problem itself or a bug in the whole telegram bots platform? I just wanted to say that this dilemma happens with any inline bot supporting markdown input.

Btw, is there any place where people can submit API / platform issues?

zhkvia commented 8 years ago

Oh, I noticed an "api issue" label added by @auchri. My question isn't relevant anymore (:

john-preston commented 8 years ago

@luc1ph3r You mentioned "select custom markdown", so I thought it was a specific single bot problem. If none of the bots get the right text then it is a bot platform problem. If they do get correct text on some Telegram apps, but not on Telegram Desktop, then it is a Telegram Desktop problem and it can be discussed here :)

auchri commented 8 years ago

Happens on android too:

screenshot_20160911-213047

s3c commented 7 years ago

I'm having the same problem, when using something like:

*Title:* ``` a b c d ```\n'

I only get:

Title: b c d

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.