Bug 460204 - [Feature Request] Support Syntax Highlighting for Code Blocks
Summary: [Feature Request] Support Syntax Highlighting for Code Blocks
Status: RESOLVED DUPLICATE of bug 460044
Alias: None
Product: NeoChat
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-10-10 16:31 UTC by ahuszagh
Modified: 2022-10-23 10:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ahuszagh 2022-10-10 16:31:01 UTC
Currently, when creating code blocks on Neochat, code blocks and inline blocks are barely distinguishable from regular message text. This is true for the Breeze Classic, Breeze Dark, Breeze Light, and Default themes (using the Sweet theme), or it should apply to every theme. Although Neochat correctly identifies this is a code block, it means that said code is practically indistinguishable from other text (including font, font color, or background).

A simple test to reproduce:

Message 1:
---

This is a `inline code`.

Message 2:
---

Here's my JSON config file:
```json
{
    "key": false
}
```

---

Desired outcome: using some style, the code block should be different from any regular text, generally done by using the system monospace font, reducing the font size slightly, and changing the font background. Likewise, code blocks should support syntax highlighting.
Comment 1 ahuszagh 2022-10-10 16:33:37 UTC
Other information, since this wasn't provided above: this is using KDE on Wayland, with version 22.06, installed via a Flatpak. It's using KDE Plasma version 5.25.5.
Comment 2 James Graham 2022-10-14 18:29:38 UTC
Yes Neochat is currently lacking here it does change the font to the system monospace but you get little else. Its on my list to look at, at some point but is a huge a mount of effort.
Comment 3 James Graham 2022-10-23 10:20:25 UTC
*** This bug has been marked as a duplicate of bug 460044 ***