| Summary: | Syntax Highlighting for Markdown | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | `{3rd: "Beedell", 1st: "Roke"}`{.JSON5} <1c4cmcli> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | UNCONFIRMED --- | ||
| Severity: | enhancement | CC: | dgp-mail |
| Priority: | medium | ||
| Version: | 24.2.1.2 release | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://bugs.documentfoundation.org/show_bug.cgi?id=43089#c0 | ||
| See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=94978 | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | 160362 | ||
| Bug Blocks: | |||
| Attachments: | Demonstration of the feature in Visual Studio Code. | ||
|
Description
`{3rd: "Beedell", 1st: "Roke"}`{.JSON5}
2024-03-25 20:04:14 UTC
Please submit a valid bug report as described here: https://www.documentfoundation.org/submit-code-of-conduct-report/ => NEEDINFO (In reply to Dieter from comment #1) > Please submit a valid bug report as described here: > https://www.documentfoundation.org/submit-code-of-conduct-report/ > > => NEEDINFO 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? I don't quite understand how CoC relates. (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.
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. 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. (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. |