Bug 160360 - Syntax Highlighting for Markdown
Summary: Syntax Highlighting for Markdown
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.1.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL: https://bugs.documentfoundation.org/s...
Whiteboard:
Keywords:
Depends on: 160362
Blocks:
  Show dependency treegraph
 
Reported: 2024-03-25 20:04 UTC by `{third: "Beedell", first: "Roke"}`{.JSON5}
Modified: 2024-04-19 19:37 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Demonstration of the feature in Visual Studio Code. (17.76 KB, image/png)
2024-04-10 23:39 UTC, `{third: "Beedell", first: "Roke"}`{.JSON5}
Details

Note You need to log in before you can comment on or make changes to this bug.
Description `{third: "Beedell", first: "Roke"}`{.JSON5} 2024-03-25 20:04:14 UTC
Markdown can already be edited as plain text, and if https://bugs.documentfoundation.org/show_bug.cgi?id=94978 is implemented, shall become an exportable format. Consequently, syntax highlighting is the sole important feature absent for it to be easily modifiable too.
Comment 1 Dieter 2024-04-10 06:55:27 UTC Comment hidden (obsolete)
Comment 2 `{third: "Beedell", first: "Roke"}`{.JSON5} 2024-04-10 12:15:17 UTC Comment hidden (obsolete)
Comment 3 Dieter 2024-04-10 14:20:45 UTC
(In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #2)
> I don't think that that's the correct URI. Did you mean
> https://wiki.documentfoundation.org/index.php?title=QA/
> BugReport&oldid=685909#Description_and_attachments?

Yes, of course. sorry for that wrong link.
Comment 4 `{third: "Beedell", first: "Roke"}`{.JSON5} 2024-04-10 23:39:54 UTC
Created attachment 193605 [details]
Demonstration of the feature in Visual Studio Code.

(In reply to Dieter from comment #3)
> (In reply to `{third: "Beedell", first: "Roke"}`{.JSON5} from comment #2)
> > I don't think that that's the correct URI. Did you mean
> > https://wiki.documentfoundation.org/index.php?title=QA/
> > BugReport&oldid=685909#Description_and_attachments?
> 
> Yes, of course. sorry for that wrong link.

In which case, I'm surprised that you consider anything absent. That page mostly describes the reporting process for reproducible errata, rather than enhancements, and the few things it does mention appear to have been fulfilled.

However, I've uploaded https://camo.githubusercontent.com/e2965a3699df6f45b0175f7b697ce6ef102ed939660ca5d80615358c08467ef0/68747470733a2f2f646c2e64726f70626f7875736572636f6e74656e742e636f6d2f732f75336e6868337469666673367370632f323031352d31302d3239253230617425323031342e33332e706e673f646c3d30 as an attachment so that I've provided a demonstration of the feature.
Comment 5 Eyal Rozenberg 2024-04-19 19:33:39 UTC
I don't remember that LO offers syntax highlighting for files it edits as text. Why should Markdown be any different?

If you want to edit Markdown as text, use a source code editor or a specialized MD editor with a preview. I don't know that LibreOffice is used that way.

Suggest marking as either WONTFIX or INVALID.
Comment 6 `{third: "Beedell", first: "Roke"}`{.JSON5} 2024-04-19 19:37:18 UTC
(In reply to Eyal Rozenberg from comment #5)
> I don't remember that LO offers syntax highlighting for files it edits as
> text. Why should Markdown be any different?
> 
> If you want to edit Markdown as text, use a source code editor or a
> specialized MD editor with a preview. I don't know that LibreOffice is used
> that way.
> 
> Suggest marking as either WONTFIX or INVALID.

Indeed, it shouldn't be, hence https://bugs.documentfoundation.org/show_bug.cgi?id=160362#c1.