org-mode syntax high lighting #306

The .org files blocks does not display with syntax highlighting

by block i mean something like

#+begin_src C
#include <stdio.h>
int 
main(void)
{
 puts("Hello World!");
}
#+end_src

org-mode evaluates that to a syntax-highlighted block. However, the org-mode implemented in gittea does not displays it (for example here

Did you report the issue upstream?

Issue upstream

I'm sorry, but i don't think I know the meaning of that

@qorg11 codeberg is powered by gitea and this project has its own bugtracker ...

if something is not related to codeberg specific but to gitea (software) as a whole, it get the lable gitea-related issue

"report issue upstream" | "upstream" ... means either tell us the link to an already created issue https://github.com/go-gitea/gitea/issues (by yourselve?) or tell us if we should create one

example: https://github.com/go-gitea/gitea/issues/13085

thank you! Yes, exactly

@qorg11 You mean that the code blocks inside the .org files are not syntax-highlighted? Well, I think this is not a bug but intended behaviour, I don't recall them being highlighted in Markdown or other markup languages either. Gitea only highlights whole text files.

If I understand correctly, you're requesting the feature that this is done? Could you please report this to https://github.com/go-gitea/gitea/issues if you haven't already done so far?

I don't recall them being highlighted in Markdown or other markup languages either

I have to correct this: I think you only get syntax highlighting if you specify the language after the block, like so

```javascript
var a = 3;
``` ­ 

see:

var a = 3;

vs

var a = 3;

I see that you tried this, right? Hmm, emacs-lisp is supported ...

(setq a "abc")
(setq b "bcd")
(setq c "cde")

Do you mind filing this issue upstream at https://github.com/go-gitea/gitea/issues as the request to support syntax highlighting in org mode?

upstream: https://github.com/go-gitea/gitea/pull/14222

but pull is not jet ready as it breaks org mode render completly :/

the pull request has been merged upstream, so we'll likely see this feature in 1.15

Codeberg-test runs 1.15 now, so we can test ;)

should be fixed - feel free to reopen if not