1.12 the new code editor is great, except for markdown. #5640

New Issue

GiteaMirror · 2025-11-02T06:31:38-06:00

GiteaMirror commented

2025-11-02 06:31:38 -06:00

Originally created by @TwoTwenty on GitHub (Jun 26, 2020).

It would be cool if we could detect .md files and give slightly different context for the wysiwyg or use the old editor even.

Originally created by @TwoTwenty on GitHub (Jun 26, 2020). It would be cool if we could detect .md files and give slightly different context for the wysiwyg or use the old editor even.

GiteaMirror added the type/proposal label 2025-11-02 06:31:38 -06:00

GiteaMirror commented

2025-11-02 06:31:38 -06:00

@hrvoj3e commented on GitHub (Jun 30, 2020):

Preview mode is not available when creating new .md file in GUI.
Editing existing .md file show tabs edit, preview, changes.

@hrvoj3e commented on GitHub (Jun 30, 2020): Preview mode is not available when creating new `.md` file in GUI. Editing existing `.md` file show tabs edit, preview, changes.

GiteaMirror commented

2025-11-02 06:31:38 -06:00

@realpixelcode commented on GitHub (Jul 1, 2020):

I saw this on Codeberg's Gitea instance and first I thought it was just a bug but it's obviously actually a feature which I hate. The old markdown editor was so great – there's no need to replace it!

@realpixelcode commented on GitHub (Jul 1, 2020): I saw this on Codeberg's Gitea instance and first I thought it was just a bug but it's obviously actually a feature which I hate. The old markdown editor was so great – there's no need to replace it!

GiteaMirror commented

2025-11-02 06:31:39 -06:00

@ashimokawa commented on GitHub (Jul 1, 2020):

As @TwoTwenty, I also think for markdown the new editor, and the old one was better.
Since the old one still exists for issues and issue comments, it would be better to also use it for markdown again.

One problem is still if someone wants to create a new file, there is not way of determining if this will be a markdown file or not in advance.

@ashimokawa commented on GitHub (Jul 1, 2020): As @TwoTwenty, I also think for markdown the new editor, and the old one was better. Since the old one still exists for issues and issue comments, it would be better to also use it for markdown again. One problem is still if someone wants to create a *new* file, there is not way of determining if this will be a markdown file or not in advance.

GiteaMirror commented

2025-11-02 06:31:39 -06:00

@realpixelcode commented on GitHub (Jul 1, 2020):

One problem is still if someone wants to create a new file, there is not way of determining if this will be a markdown file or not in advance.

On Codeberg, the editor recognizes your file type as soon as you enter the file name like filename.md

@realpixelcode commented on GitHub (Jul 1, 2020): > One problem is still if someone wants to create a _new_ file, there is not way of determining if this will be a markdown file or not in advance. On Codeberg, the editor recognizes your file type as soon as you enter the file name like ```filename.md```

GiteaMirror commented

2025-11-02 06:31:39 -06:00

@lafriks commented on GitHub (Jul 1, 2020):

Problem with old markdown editor that is not maintained anymore and has many bugs, especially on mobile devices

@lafriks commented on GitHub (Jul 1, 2020): Problem with old markdown editor that is not maintained anymore and has many bugs, especially on mobile devices

GiteaMirror commented

2025-11-02 06:31:39 -06:00

@MarionMoseby commented on GitHub (Jul 2, 2020):

I must say I have never experienced any bug while using the markdown in mobile. Imho the new code editor is terrible for markdown and the old one should be brought one, as this one makes git more complicated for beginners

@MarionMoseby commented on GitHub (Jul 2, 2020): I must say I have never experienced any bug while using the markdown in mobile. Imho the new code editor is terrible for markdown and the old one should be brought one, as this one makes git more complicated for beginners

GiteaMirror commented

2025-11-02 06:31:39 -06:00

@lafriks commented on GitHub (Jul 5, 2020):

For example this issue #9658

@lafriks commented on GitHub (Jul 5, 2020): For example this issue #9658

GiteaMirror commented

2025-11-02 06:31:40 -06:00

@melroy89 commented on GitHub (Sep 25, 2020):

I really want to have a markdown editor on markdown files within the Git repo! At least for desktop PCs...

Please....! 🤙

EDIT: I call it almost a bug, rather than a proposal.

@melroy89 commented on GitHub (Sep 25, 2020): I really want to have a markdown editor on markdown files within the Git repo! At least for desktop PCs... Please....! :call_me_hand: **EDIT:** I call it almost a bug, rather than a proposal.

GiteaMirror commented

2025-11-02 06:31:40 -06:00

@IzzySoft commented on GitHub (Nov 13, 2020):

TBH, both editors are going to kill me one day. None of the two permits copy/pasting via mouse (on Linux, middle-click pastes – which works everywhere but in Gitea – see #11216). With the old one, I destroyed a perfectly written paragraph more than once (as shift-home does not, as everywhere else, mark to the beginning of the line but to the beginning of the paragraph – and thus a quick mark-delete trashed it all; needless to say none of the two editors seems to have an Undo function for cases like that).

Luckily, I rarely use the WebIf to edit files… But I really wish there were a decent replacement for both.

@IzzySoft commented on GitHub (Nov 13, 2020): TBH, both editors are going to kill me one day. None of the two permits copy/pasting via mouse (on Linux, middle-click pastes – which works everywhere but in Gitea – see #11216). With the old one, I destroyed a perfectly written paragraph more than once (as shift-home does not, as everywhere else, mark to the beginning of the line but to the beginning of the paragraph – and thus a quick mark-delete trashed it all; needless to say none of the two editors seems to have an Undo function for cases like that). Luckily, I rarely use the WebIf to edit files… But I really wish there were a decent replacement for both.

GiteaMirror commented

2025-11-02 06:31:40 -06:00

@umutpiri commented on GitHub (Feb 16, 2021):

I think there should be an option to use the old editor. The new editor is better for any file format except markdown.

@umutpiri commented on GitHub (Feb 16, 2021): I think there should be an option to use the old editor. The new editor is better for any file format except markdown.

GiteaMirror commented

2025-11-02 06:31:40 -06:00

@vincowl commented on GitHub (Nov 28, 2022):

Hello
Any news on this subject ? Lacking a markdown editor for files like README.md is a pain and even more painfull while it is available for issues written in the same "language". If needed, I am ready to invest time if a gitea dev gives me some hints on the right way to implement it

@vincowl commented on GitHub (Nov 28, 2022): Hello Any news on this subject ? Lacking a markdown editor for files like README.md is a pain and even more painfull while it is available for issues written in the same "language". If needed, I am ready to invest time if a gitea dev gives me some hints on the right way to implement it

GiteaMirror commented

2025-11-02 06:31:41 -06:00

@yp05327 commented on GitHub (Sep 19, 2024):

Preview mode is not available when creating new .md file in GUI. Editing existing .md file show tabs edit, preview, changes.

This is supported.

@yp05327 commented on GitHub (Sep 19, 2024): > Preview mode is not available when creating new `.md` file in GUI. Editing existing `.md` file show tabs edit, preview, changes. This is supported.

GiteaMirror commented

2025-11-02 06:31:41 -06:00

@therysin commented on GitHub (Jan 16, 2025):

Any plans for a markdown editor? I'm using gitea mainly for documentation, along with other non technical people, who would like basic editor options (like the old UI provided)

@therysin commented on GitHub (Jan 16, 2025): Any plans for a markdown editor? I'm using gitea mainly for documentation, along with other non technical people, who would like basic editor options (like the old UI provided)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5640