github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 03:46:23 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

org-mode parser isn't parsing nested lists #1333

New Issue
Closed
opened 2025-11-02 03:56:51 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 03:56:51 -06:00
Owner
Copy Link

Originally created by @jrmiller82 on GitHub (Dec 8, 2017).

The org-mode parser isn't parsing nested lists.

I.e.

- Bullet
- Bullet
  - Sub Bullet
  - Sub Bullet

Should show up with the sub bullets indented and nested. They show up as same level in gitea output.

Gitea 1.3.0 sqlite3
Linux amd64

Can you reproduce the bug at https://try.gitea.io? Yes

https://try.gitea.io/poop/org-issues/src/branch/master/README.org
capture

Originally created by @jrmiller82 on GitHub (Dec 8, 2017). The org-mode parser isn't parsing nested lists. I.e. ``` - Bullet - Bullet - Sub Bullet - Sub Bullet ``` Should show up with the sub bullets indented and nested. They show up as same level in gitea output. Gitea 1.3.0 sqlite3 Linux amd64 Can you reproduce the bug at https://try.gitea.io? **Yes** https://try.gitea.io/poop/org-issues/src/branch/master/README.org ![capture](https://user-images.githubusercontent.com/7538678/33785523-07ea98a2-dc2b-11e7-9869-d97daa9be3eb.PNG) <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. -->
GiteaMirror added the status/blockedtype/bug labels 2025-11-02 03:56:51 -06:00
GiteaMirror commented 2025-11-02 03:56:52 -06:00
Author
Owner
Copy Link

@sondr3 commented on GitHub (Dec 9, 2017):

This isn't a bug with Gitea though, but rather with goorgeous.

@sondr3 commented on GitHub (Dec 9, 2017): This isn't a bug with Gitea though, but rather with [goorgeous](https://github.com/chaseadamsio/goorgeous).
GiteaMirror commented 2025-11-02 03:56:52 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 9, 2017):

@jrmiller82 could you also send an issue to https://github.com/chaseadamsio/goorgeous and reference to this one.

@lunny commented on GitHub (Dec 9, 2017): @jrmiller82 could you also send an issue to https://github.com/chaseadamsio/goorgeous and reference to this one.
GiteaMirror commented 2025-11-02 03:56:52 -06:00
Author
Owner
Copy Link

@jrmiller82 commented on GitHub (Dec 10, 2017):

Done. https://github.com/chaseadamsio/goorgeous/issues/75

@jrmiller82 commented on GitHub (Dec 10, 2017): Done. https://github.com/chaseadamsio/goorgeous/issues/75
GiteaMirror commented 2025-11-02 03:56:52 -06:00
Author
Owner
Copy Link

@monkeyhybrid commented on GitHub (May 21, 2018):

Apologies, for I have realised my comment is not applicable to this issue. I've created a new issue.

@jrmiller82 - can you confirm if this only happens on double (and more) nested lists?

For me, nested lists work for the top level, and the first level of nested, but anything deeper than that is shown flat. However, I can force deeper levels of nesting to work by using twice as much indenting as you'd normally expect.

So the following Markdown, using the normal two (2) spaces per level of nesting:

[code deleted]

As you can see, Level 3 is not being nested any deeper in the HTML than Level 2.

However, if I use four (4) spaces for each list indent, on Level 3 and deeper, all levels nest correctly:

[code deleted]

I see this on both my own installation and try.gitea.io.

I can add this to the issue @jrmiller82 raised on chaseadamsio/goorgeous if that is appropriate.

@monkeyhybrid commented on GitHub (May 21, 2018): Apologies, for I have realised my comment is not applicable to this issue. I've created a [new issue](https://github.com/go-gitea/gitea/issues/4009). ~~@jrmiller82 - can you confirm if this only happens on double (and more) nested lists?~~ ~~For me, nested lists work for the top level, and the first level of nested, but anything deeper than that is shown flat. However, I can force deeper levels of nesting to work by using twice as much indenting as you'd normally expect.~~ ~~So the following Markdown, using the normal two (2) spaces per level of nesting:~~ ``` [code deleted] ``` ~~As you can see, Level 3 is not being nested any deeper in the HTML than Level 2.~~ ~~However, if I use four (4) spaces for each list indent, on Level 3 and deeper, all levels nest correctly:~~ ``` [code deleted] ``` ~~I see this on both my own installation and try.gitea.io.~~ ~~I can add this to the [issue](https://github.com/chaseadamsio/goorgeous/issues/75) @jrmiller82 raised on chaseadamsio/goorgeous if that is appropriate.~~
GiteaMirror commented 2025-11-02 03:56:52 -06:00
Author
Owner
Copy Link

@jrmiller82 commented on GitHub (May 21, 2018):

I don’t have a gitea instance installed to test on at the moment.

On May 21, 2018, at 13:22, monkeyhybrid notifications@github.com wrote:

@jrmiller82 - can you confirm if this only happens on double (and more) nested lists?

For me, nested lists work for the top level, and the first level of nested, but anything deeper than that is shown flat. However, I can force deeper levels of nesting to work by using twice as much indenting as you'd normally expect.

So the following Markdown, using the normal two (2) spaces per level of nesting:

  • Level 1
    • Level 2
      • Level 3 (2+2 spaces for indent)
        incorrectly outputs:
  • Level1
    • Level 2
    • Level 3
As you can see, Level 3 is not being nested any deeper in the HTML than Level 2.

However, if I use four (4) spaces for each list indent, on Level 3 and deeper, all levels nest correctly:

  • Level 1
    • Level 2
      • Level 3 (2+4 spaces indent)
        outputs:
  • Level1
    • Level 2
      • Level 3
I see this on both my own installation and try.gitea.io.

I can add this to the issue @jrmiller82 raised on chaseadamsio/goorgeous if that is appropriate.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jrmiller82 commented on GitHub (May 21, 2018): I don’t have a gitea instance installed to test on at the moment. > On May 21, 2018, at 13:22, monkeyhybrid <notifications@github.com> wrote: > > @jrmiller82 - can you confirm if this only happens on double (and more) nested lists? > > For me, nested lists work for the top level, and the first level of nested, but anything deeper than that is shown flat. However, I can force deeper levels of nesting to work by using twice as much indenting as you'd normally expect. > > So the following Markdown, using the normal two (2) spaces per level of nesting: > > * Level 1 > * Level 2 > * Level 3 (2+2 spaces for indent) > incorrectly outputs: > > <ul> > <li>Level1 > <ul> > <li>Level 2</li> > <li>Level 3</li> > </ul> > </li> > </ul> > As you can see, Level 3 is not being nested any deeper in the HTML than Level 2. > > However, if I use four (4) spaces for each list indent, on Level 3 and deeper, all levels nest correctly: > > * Level 1 > * Level 2 > * Level 3 (2+4 spaces indent) > outputs: > > <ul> > <li>Level1 > <ul> > <li>Level 2 > <ul> > <li>Level 3</li> > </ul> > </li> > </ul> > </li> > </ul> > I see this on both my own installation and try.gitea.io. > > I can add this to the issue @jrmiller82 raised on chaseadamsio/goorgeous if that is appropriate. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread.
GiteaMirror commented 2025-11-02 03:56:53 -06:00
Author
Owner
Copy Link

@monkeyhybrid commented on GitHub (May 21, 2018):

@jrmiller82 - Sorry, please ignore my message. I just re-read your original issue and realised it has nothing to do with Markdown. I've edited my comments on this issue, and have created a new issue.

@monkeyhybrid commented on GitHub (May 21, 2018): @jrmiller82 - Sorry, please ignore my message. I just re-read your original issue and realised it has nothing to do with Markdown. I've edited my comments on this issue, and have created a new [issue](https://github.com/go-gitea/gitea/issues/4009).
GiteaMirror commented 2025-11-02 03:56:53 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 22, 2018):

@jrmiller82 test it on https://try.gitea.io

@lunny commented on GitHub (May 22, 2018): @jrmiller82 test it on https://try.gitea.io
GiteaMirror commented 2025-11-02 03:56:53 -06:00
Author
Owner
Copy Link

@Ekleog commented on GitHub (Sep 9, 2019):

goorgeous has since been deprecated and is pointing to go-org as a replacement, so fixing this would likely mean switching to go-org

@Ekleog commented on GitHub (Sep 9, 2019): `goorgeous` has since been deprecated and is pointing to `go-org` as a replacement, so fixing this would likely mean switching to `go-org`
GiteaMirror commented 2025-11-02 03:56:53 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 6, 2020):

Is not present on current master anymore

@6543 commented on GitHub (Sep 6, 2020): Is not present on current master anymore
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label status/blocked type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1333
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?