Intendation not shown correctly in file view #3092

New Issue

GiteaMirror · 2025-11-02T05:00:32-06:00

GiteaMirror commented

2025-11-02 05:00:32 -06:00

Originally created by @theAkito on GitHub (Mar 21, 2019).

Gitea version (or commit ref): b78cbbcaa2
Git version: 2.11.0
Operating system: DietPi, based on Raspbian GNU/Linux 9 (stretch)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No, can't register on try.gitea.io, returns code 500.
- Not relevant
Log gist:

Description

Indentation is not shown correctly. If I remove the intendation at all and put the first character on the first place of the line, the intendation is entirely gone. If I press TAB to intend only once, then it shows up as if I pressed TAB and 3 times SPACE, in the file view, after commiting it.

Screenshots

In edit mode, before commit.

In file view, after commit.

Originally created by @theAkito on GitHub (Mar 21, 2019).   - Gitea version (or commit ref): b78cbbcaa25d03d07b77a010a26568182682c6f1 - Git version: 2.11.0 - Operating system: DietPi, based on Raspbian GNU/Linux 9 (stretch) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No, can't register on try.gitea.io, returns code 500. - [ ] Not relevant - Log gist: ## Description Indentation is not shown correctly. If I remove the intendation at all and put the first character on the first place of the line, the intendation is entirely gone. If I press TAB to intend only once, then it shows up as if I pressed TAB and 3 times SPACE, in the file view, after commiting it. ## Screenshots  In edit mode, before commit. ![2019-03-21 18_19_44-Gitea-Bug_B](https://user-images.githubusercontent.com/26848976/54773379-be24a500-4c09-11e9-849a-b23a813331ac.png) In file view, after commit. ![2019-03-21 18_19_44-Gitea-Bug_A](https://user-images.githubusercontent.com/26848976/54772004-c3342500-4c06-11e9-836f-8b40b05dba4f.png)

GiteaMirror added the topic/ui issue/stale type/bug labels 2025-11-02 05:00:32 -06:00

GiteaMirror closed this issue

2025-11-02 05:00:33 -06:00

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@lafriks commented on GitHub (Mar 24, 2019):

Could be that there was already issue for this

@lafriks commented on GitHub (Mar 24, 2019): Could be that there was already issue for this

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@theAkito commented on GitHub (Mar 24, 2019):

Could be that there was already issue for this

Before opening an issue, I always search for an existing one. I didn't find any issue even remotely close to intendation.

@theAkito commented on GitHub (Mar 24, 2019): > > > Could be that there was already issue for this Before opening an issue, I always search for an existing one. I didn't find any issue even remotely close to intendation.

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@lafriks commented on GitHub (Mar 25, 2019):

Could this be related to #5596 ?

@lafriks commented on GitHub (Mar 25, 2019): Could this be related to #5596 ?

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@theAkito commented on GitHub (Mar 25, 2019):

Could this be related to #5596 ?

Seems reasonable, but I am not sure. Can I check somehow if they are related?

@theAkito commented on GitHub (Mar 25, 2019): > > > Could this be related to #5596 ? Seems reasonable, but I am not sure. Can I check somehow if they are related?

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@stale[bot] commented on GitHub (May 24, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (May 24, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:00:34 -06:00

@stale[bot] commented on GitHub (Jun 7, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 7, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 12:18:31 -06:00

[PR #3092] [MERGED] Improve LFS tests + fix lfs url refs + keep path upper/lowercase in db. #16762

Sign in to join this conversation.