Introducing SourceForge’s new markdown text editor

By Community Team

Sometimes small things make all the difference and that’s why we are happy to release a new markdown text editor on SourceForge. What this means is that when you create a ticket, edit a wiki page, or comment on a post on SourceForge you find it that much easier to format your text.  Our new text editor includes a toolbar to insert formatting and live syntax highlighting, so you can see what you’re doing while you edit.

Here’s what it looks like:

Markdown text editor screenshot

Note that the toolbar functions do the most of the common formatting so you don’t have to remember the syntax; however, the toolbar contains just the essential options. The full list of formatting and macro options are available by clicking the “?” – Help button. You’ll find that markdown supports lots of formatting, and we’ve taken care to extend it with additional linking and macro options too.

In the area where you type, there is live syntax highlighting of most formatting. This gives useful indicators of what formatting is being applied and it also helps you avoid accidental formatting. To see a full preview of your text, click the preview button (eyeball icon).

A special thank you to the Open Source Apache Allura platform folks. SourceForge developer tools run on Apache Allura and that’s where this improvement came from. Read all about it at:

That’s it for now. Happy editing!

3 Responses

  1. Alan W. Irwin says:

    I am sorry but this new “editor” is just plain awful. Did anyone actually try to use it to update a complex wiki item? That just cannot be done, and I will give specifics below so you can replicate the issues for yourself.

    I fought with it today just trying to update a specific page on our wiki with both konqueror and iceweasel (Debian’s version of firefox). But I never was able to get it to work, although I had no such problems with either browser before.There are repeated tables of test results in that wiki page so typically I use an existing table as a template to create new tables of results. However, here are the showstopper bugs I ran into while attempting to copy and edit tables today.

    1. Cursor location is misidentified. So you click on where you want to type and insert text there, and the text appears elsewhere (5 lines up in this case) in the document! This is obviously a show stopper, but there is more.

    2. Cut and paste using the mouse (i.e., by selecting text, moving the mouse to where you want to paste the text and right clicking) no longer works. Essentially, the data never makes it to my clipboard.

    3. I couldn’t get old-fashioned copy using the ctrl-c keyboard shortcut to work. That might be my fault since it has been years since I attempted to use that method.

    4. I did simulate copy by the old-fashioned method of selecting an area, hitting ctrl-x to cut, and immediate ctrl-v to put back the text, then ctrl-v elsewhere to copy it to where you want. But the placement of the results was completely screwed up by issue 1.

    If/when you respond to this bug report, I am sure you will suggest that I use your official bugtracker, but I am not sure where that is so please be specific about the best way to report all these bugs in your new markdown editor.

    Until those bugs are completely fixed could you please just give users the option of using your old markdown editor which “just worked”?

  2. Dave Brondsema says:

    The cursor location misidentification is a bug we are currently working on and will fix as soon as we can.

    Copy and paste does work with ctrl-c / ctrl-v on Windows, Mac and Linux. The Linux ability to middle-click paste is not supported in certain situations on Firefox, see bug And that is used by the CodeMirror library which is part of our markdown editor. It has a bug report about it too: I am not familiar with how Konqueror handles the middle click in these situations.

    Thanks for the detailed report. Our official bugtracker is at You don’t need to repost this report there, but if you do find additional issues, that would be the best place to report them.

    • Steven W Flinchbaugh says:

      On Mac, you use command-c (sometimes called the Apple key) NOT control-c.