org-mode qualms #4851

New Issue

GiteaMirror · 2025-11-02T06:04:57-06:00

GiteaMirror commented

2025-11-02 06:04:57 -06:00

Originally created by @kayg04 on GitHub (Feb 14, 2020).

Gitea version (or commit ref): 1.11.0
Git version: 2.25.0
Operating system: Official docker image on NixOS
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
Upload on the instance is failing with:

Failed to upload files to '' with error: Unable to push back to repo from temporary repo: abc_abc_abc/test-org (/data/gitea/tmp/local-repo/upload.git309677686) Error: context deadline exceeded.

Description

These issues surface with the latest release and are most likely caused by the switch to go-org.

Hyperlinks in auto-generated TOC (Table of Contents) do not match the links of each heading. The auto-generated links follow the format: headline-N while the headings have links of the form: user-content-headline-N. Did it work before the latest release? Yes.
Syntax highlighting doesn't work for any language. Did it work before the latest release? Only for a select few languages.
Extra line spacing between items of a list. Did it work before the latest release? Unsure.

All of the above issues can be seen on this file or in any other repo on the instance.

Screenshots

Originally created by @kayg04 on GitHub (Feb 14, 2020). - Gitea version (or commit ref): 1.11.0 - Git version: 2.25.0 - Operating system: Official docker image on NixOS - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: Upload on the instance is failing with: > Failed to upload files to '' with error: Unable to push back to repo from temporary repo: abc_abc_abc/test-org (/data/gitea/tmp/local-repo/upload.git309677686) Error: context deadline exceeded. ## Description These issues surface with the latest release and are most likely caused by the switch to go-org. 1. Hyperlinks in auto-generated TOC (Table of Contents) do not match the links of each heading. The auto-generated links follow the format: `headline-N` while the headings have links of the form: `user-content-headline-N`. Did it work before the latest release? Yes. 2. Syntax highlighting doesn't work for any language. Did it work before the latest release? Only for a select few languages. 3. Extra line spacing between items of a list. Did it work before the latest release? Unsure. All of the above issues can be seen on [this file](https://git.kayg.org/kayg/cookbooks/src/branch/master/rust.org) or in [any other repo](https://git.kayg.org/kayg/) on the instance. ## Screenshots ![2](https://user-images.githubusercontent.com/30401343/74500734-c18ae400-4edf-11ea-8cf2-fe36f0fc8901.png) ![3](https://user-images.githubusercontent.com/30401343/74500739-c6e82e80-4edf-11ea-807b-6f6dafe83795.png)

GiteaMirror added the issue/confirmed type/proposal labels 2025-11-02 06:04:57 -06:00

GiteaMirror commented

2025-11-02 06:04:58 -06:00

@stale[bot] commented on GitHub (Apr 14, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 14, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:04:58 -06:00

@kayg04 commented on GitHub (Apr 14, 2020):

bump!

Apr 14, 2020 12:34:43 stale[bot] notifications@github.com:

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/go-gitea/gitea/issues/10267#issuecomment-613263546] , or unsubscribe [https://github.com/notifications/unsubscribe-auth/AHH6GP6ZOAOZ5YJGZCTSE2LRMQDITANCNFSM4KVAMQCQ] . [https://github.com/notifications/beacon/AHH6GP2L4KM46NTAWHYYW23RMQDITA5CNFSM4KVAMQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOESG2ROQ.gif]

@kayg04 commented on GitHub (Apr 14, 2020): bump! Apr 14, 2020 12:34:43 stale[bot] <notifications@github.com>: > > This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub [https://github.com/go-gitea/gitea/issues/10267#issuecomment-613263546] , or unsubscribe [https://github.com/notifications/unsubscribe-auth/AHH6GP6ZOAOZ5YJGZCTSE2LRMQDITANCNFSM4KVAMQCQ] . [https://github.com/notifications/beacon/AHH6GP2L4KM46NTAWHYYW23RMQDITA5CNFSM4KVAMQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOESG2ROQ.gif] >

GiteaMirror commented

2025-11-02 06:04:58 -06:00

@stale[bot] commented on GitHub (Jun 13, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Jun 13, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:04:58 -06:00

@kayg04 commented on GitHub (Jun 13, 2020):

bump

Jun 13, 2020 15:24:33 stale[bot] notifications@github.com:

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub[https://github.com/go-gitea/gitea/issues/10267#issuecomment-643600198], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AHH6GP4MEXUJTK3A4SHLJWTRWNEFRANCNFSM4KVAMQCQ]. [https://github.com/notifications/beacon/AHH6GP5FX62DVNAE4J2NOBTRWNEFRA5CNFSM4KVAMQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZOI6RQ.gif]

@kayg04 commented on GitHub (Jun 13, 2020): bump Jun 13, 2020 15:24:33 stale[bot] <notifications@github.com>: > This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub[https://github.com/go-gitea/gitea/issues/10267#issuecomment-643600198], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AHH6GP4MEXUJTK3A4SHLJWTRWNEFRANCNFSM4KVAMQCQ]. [https://github.com/notifications/beacon/AHH6GP5FX62DVNAE4J2NOBTRWNEFRA5CNFSM4KVAMQC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZOI6RQ.gif] >

GiteaMirror commented

2025-11-02 06:04:58 -06:00

@h3xx commented on GitHub (Aug 2, 2023):

It looks as if Gitlab's markdown parser is also having trouble rendering this link: https://gitlab.com/kayg/cookbooks/-/blob/master/rust.org?ref_type=heads

Blocks of code associated with the conditions in an =if= expression are
sometimes called /[[file:ch02/guessing_game/src/main.rs::Ordering::Less => println!("Too small!"),][arms]]/.

GitHub also has trouble:

Blocks of code associated with the conditions in an =if= expression are sometimes called //.

If you can, try using the traditional Markdown link format of [text](url)?
I.e. [arms](file:ch02/guessing_game/src/main.rs::Ordering::Less => println!("Too small!"),) or some variation thereof, massaged so your link works.

@h3xx commented on GitHub (Aug 2, 2023): It looks as if Gitlab's markdown parser is also having trouble rendering this link: https://gitlab.com/kayg/cookbooks/-/blob/master/rust.org?ref_type=heads ```markdown Blocks of code associated with the conditions in an =if= expression are sometimes called /[[file:ch02/guessing_game/src/main.rs::Ordering::Less => println!("Too small!"),][arms]]/. ``` GitHub also has trouble: > Blocks of code associated with the conditions in an =if= expression are sometimes called /[[file:ch02/guessing_game/src/main.rs::Ordering::Less => println!("Too small!"),][arms]]/. If you can, try using the traditional Markdown link format of `[text](url)`? I.e. `[arms](file:ch02/guessing_game/src/main.rs::Ordering::Less => println!("Too small!"),)` or some variation thereof, massaged so your link works.

GiteaMirror referenced this issue

2025-11-02 13:51:28 -06:00

[PR #4851] [MERGED] 1.5.1 Changelog #17521

GiteaMirror referenced this issue

2025-11-02 13:51:46 -06:00

[PR #4854] [MERGED] Backport 1.5.1 changelog #17523

Sign in to join this conversation.