Ticket search results

In editor, pasting should be auto-wrapped

Dave Brondsema — Fri, 04 Sep 2015 14:24:45 -0000

When pasting a large chunk of text into the markdown editor, it often would be useful to automatically wrap it with `~~~~` or indent it. People who paste code snippets or log lines would benefit from this, especially if they are not familiar with markdown and don't realize it needs to be in a code block to avoid `__foo__` from getting formatted etc. I think this would help alleviate problems expressed in https://sourceforge.net/p/forge/feature-requests/134/ However, that won't be appropriate all the time, since some people could paste large amounts of regular text or even markdown formatting (e.g. restructuring a wiki page). Turning it into a code block won't be helpful. We'll need some sort of UI to make this work well. I am thinking that we show a notification after it happens, and tell the user how they can click the code snippet button to undo it. We can also save a cookie/sessionStorage setting to not do it again. Here's an autoindent snippet proof-of-concept: ~~~~ cm = editor.codemirror; // based on https://github.com/codemirror/CodeMirror/issues/2120 cm.on("change", function(cm, change) { if (change.origin != "paste" || change.text.length < 2) { return; } var spaces = cm.options.tabSize; cm.operation(function() { for (var line = change.from.line, end = CodeMirror.changeEnd(change).line; line <= end; ++line) { cm.indentLine(line, spaces); } }); }); ~~~~

Editor should autocomplete artifact references and macros

Dave Brondsema — Thu, 14 Mar 2019 02:19:57 -0000

In the markdown editor, it would be great if you type `[` it shows a list of artifact choices. And if you type `[[` it shows a list of macro choices. Using the autocomplete addon for codemirror can get us a lot of the way there. https://codemirror.net/doc/manual.html#addon_show-hint We probably will want to save recently visited tickets, wiki pages, and other artifacts in the browser's localStorage or sessionStorage, so that we can give useful initial choices. We'll also need to do ajax lookups to get a full list of matching artifacts, as well as mount points and project names for cases like `[wiki:Baz]` or `[proj:wiki:Baz]`. The UI could be extra nice if it didn't require typing a `[` first in some cases, since some people might not know that syntax. If you just typed `#` it could suggest tickets and put the `[` in for you automatically if you select one.

Research odd behavior / bugs in simplemde

Dave Brondsema — Mon, 21 Sep 2015 14:05:40 -0000

See if these are upstream bugs, report them, see if we can fix them * when you get multiple levels deep in a list, some lines are colored green * any sort of `foo:bar` text with a colon in it gets turned into a link style. Should have a smarter URL pattern * within a blockquote section, the Image button is highlighted instead of blockquote button * `#foobar` heading without a space after #, does not get styled like a heading

Markdown editor should have max height

Dave Brondsema — Mon, 10 Aug 2015 14:28:45 -0000

After a certain height, the markdown editor should switch to scrolling. If the editor is too tall, then the toolbar is far away and it generally is just a lot bigger than normal expectations for text editing. Method to do this: https://groups.google.com/d/msg/codemirror/1zjPxioENiA/ujiZU3Of-5oJ With some preliminary tests, this makes [#7948] less of a problem too

Allura's Markup chokes on IRCS URLs

Anonymous — Wed, 15 Apr 2015 13:07:08 -0000

*Originally created by:* willpittenger I created an IRC channel and went to list it in my project's discussion board. However, Allura couldn't handle the URL. Compare the source code with the results in the table below. Source code | Results ------------|-------- <ircs://irc.freenode.net/allura> | ircs://irc.freenode.net/allura | ircs://irc.freenode.net/allura I know the second isn't how you list a URL with Markdown, but at least it's visible.

Markdown * for unordered lists does not make bullet but italisizes text

Anonymous — Mon, 07 Nov 2011 14:40:37 -0000

*Originally created by:* geoffreyvanwyk When I try to make an unordered list on a wiki page by using the asterisk (*), the first, third, and fifth items are italisized. Bullets are supposed to be created. * first * second The Markdown for unordered lists seems to work correctly in this ticket description box, but it definitely does not work in the wiki page. The alternative to the asterisk is the plus (+), but the plus is simply printed literarlly.

Fixed font on markdown input area

Anonymous — Thu, 20 Aug 2015 22:07:54 -0000

*Originally created by:* wladid * I think you should use a fixed font for markdown input areas.