Quote original message content, not rendered version (html)

[neiljp]

If quoting an image, and maybe other items, zulip-terminal quotes the html, rather than the unrendered message, which leaves quite a mess if sent!

We should be able to request the original content, if we don't have it, and store/send it.

This should probably be a request to the Model (possibly via controller), before quoting the correct text.

[amanagr]

msg1 - contains text I want to quote.
@neiljp you want to quote the exact same text rendered by zt finally in msg1, right?
(If yes, then I suppose it can be easily done)

[timabbott]

https://zulipchat.com/api/get-raw-message is the API you want to get raw content. We do some clever stuff with putting in a placeholder "Quoting..." immediately, and then replacing that placeholder when we get the response from the server in the webapp; not sure if that's worth it here, but FYI :). Generally use the raw_content variable name for the raw text/markdown.

[neiljp]

@amanagr I'm not sure what you're trying to say, but for example I came across this in the image case - see ZT emoji & quote topic on test here on czo.

[aditya-hari]

@amanagr @neiljp I'd like to work on this since this is labelled as a good first issue, but I'll be honest - I have absolutely no idea where to even begin looking.

[neiljp]

@aditya-hari This occurs when we use the '>' keypress, which as you'll see in config/keys.py translates to the command string QUOTE_REPLY. If you use git grep to search through the source, you should be able to find where this is triggered, and so where it is not quite working properly.

[aditya-hari]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @aditya-hari! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Sign the Dropbox Contributor License Agreement, so that Zulip can use your code.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!