Codeberg/Community
54
325
Fork
You've already forked Community
12

linked comment via URL in comment needs two spaces to be displayed #212

Closed
opened 2020年07月05日 17:27:50 +02:00 by fnetX · 6 comments
Owner
Copy link

I just commented including this code:
and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now
but look at what is displayed (same code below):

"and #140 (comment) is now"

so both the issue is not linked and the word after the URL is removed.

Inserting a second space after the url like so works:
and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now
and #140 (comment) is now

Interestingly the double space is removed from the code block ...

Can someone confirm that this is related to gitea and not some codeberg issue so someone can report it there?

Thank you!

(Hint: normal URLs work fine!

https://example.com/Codeberg/Community/issues/140#issuecomment-49756 test)

I just commented including this code: `and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now` but look at what is displayed (same code below): "and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now" so both the issue is not linked and the word after the URL is removed. Inserting a second space after the url like so works: `and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now` and https://codeberg.org/Codeberg/Community/issues/140#issuecomment-49756 is now Interestingly the double space is removed from the code block ... Can someone confirm that this is related to gitea and not some codeberg issue so someone can report it there? Thank you! (Hint: normal URLs work fine! https://example.com/Codeberg/Community/issues/140#issuecomment-49756 test)
Member
Copy link

Can you please verify on try.gitea.io and report to the gitea issue tracker?

Can you please verify on try.gitea.io and report to the gitea issue tracker?

was this reported upstream?

was this reported upstream?
Member
Copy link

not sure

not sure
Author
Owner
Copy link

was this reported upstream?

damn, no, I'm sorry. I apparently didn't find the time to check if it's reproducible in gitea itself.

It'd be nice if someone could do this, but I'll add a todo for next week to check if it's done and do it myself.

> was this reported upstream? damn, no, I'm sorry. I apparently didn't find the time to check if it's reproducible in gitea itself. It'd be nice if someone could do this, but I'll add a todo for next week to check if it's done and do it myself.

upstream: https://github.com/go-gitea/gitea/issues/13842

upstream: https://github.com/go-gitea/gitea/issues/13842
Author
Owner
Copy link

This seems to be fixed, too.

This seems to be fixed, too.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure
Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#212
Reference in a new issue
Codeberg/Community
No description provided.
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?