-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Emphasize heading titles in messages #1095
Comments
I would like to work on this issue, please assign it to me! |
@SwarupKharul Just calling out like you've done is fine, though you can use |
@zulipbot claim |
Welcome to Zulip, @SwarupKharul! 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:
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)! |
@SwarupKharul if u aren't working on this, may I take this issue? |
Hello @SwarupKharul, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
@kingjuno what about this one? |
@avats-dev I am not working on this. I guess you can go with this one. |
@zulipbot claim |
Welcome to Zulip, @mounilKshah! 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:
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)! |
Hello @mounilKshah, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days. You can reclaim this issue or claim any other issue by commenting Thanks for your contributions, and hope to see you again soon! |
Hello, |
@zulipbot claim |
Hello @neiljp Before After At present, I have implemented this only in the I wanted to ask if these changes are fine and should I continue to implement similar changes in the remaining themes as well or not. Here is the commit containing the changes made by me |
In order to emphasise the heading tags ranging from h1 to h6, they have been displayed with a different colour. This is to fix issue zulip#1095
…ulip#1095 This commit along with ed3227b and 22a17fb implement heading-styles for all the themes. h1 to h6 styles have the same implementation of 'msg_heading' in the respective themes as of now.
This commit along with ed3227b and 22a17fb implement heading-styles for all the themes. h1 to h6 styles have the same implementation of 'msg_heading' in the respective themes as of now. Fixes zulip#1095
This commit contains the changes required to pass all the pre-existing test cases It also contains the test case for heading-style in soup2markup as requested in the zulip#1095. Fixes zulip#1095.
Heading-style added for all themes. Tests updated and new test cases added under test_soup2markup. Fixes zulip#1095.
Heading-style added for all themes. Tests updated and new test cases added under test_soup2markup. Fixes zulip#1095.
New test cases added under test_soup2markup. Fixes zulip#1095.
It's possible to indicate "headings" at different levels, akin to h1-h6 in html, using markdown - this currently just appears as plain text.
This would be a good issue for someone new; here are some suggestions for implementation:
soup2markup
and think how they'd be extendedsoup2markup
; add it and ensure the test now passes :)A later addition would be to add support for multiple levels of heading, such as re-adding the number of leading
#
's, or some other design.Please check-in on #zulip-terminal on chat.zulip.org if you have questions :)
The text was updated successfully, but these errors were encountered: