Use "standard" {{{ and }}} delimiters for code sections

[techtonik]

It would be really convenient if code sections could be inserted into {{{ and }}} tags. These are less common than @@ inside source files and won't cause issues like http://developer.qt.nokia.com/forums/viewthread/1059/

The {{{ and }}} convention is used by Trac, Google Code and MoinMoin wiki.

[goetz]

Good idea. Jira/Confluence uses {{xx}} for inline code and {code}abc{code} for blocks (i.e. it always starts on a new line).

[dangelog]

I agree, and I'd also like to see the ability to specify the source language (C++ / QML / JS / Python / Perl / SH / unformatted / ...) in order to get proper syntax highlighting.

[techtonik]

Here is the description of how to specify language in Trac - http://trac.edgewall.org/wiki/WikiProcessors#CodeHighlightingSupport

What language/license is used for this Wiki? Will it be possible to use Trac processor together with pygments for code highlighting?

[vsorokin]

Now used "Textile":http://warpedvisions.org/projects/textile-cheat-sheet/ markup language, I don't see sense for change part of it.

[techtonik]

It doesn't seem like Textile is appropriate choice for code development communities.

[vsorokin]

Why not? Textile is easy and convenient. And Editor have visual button is on panel. What's the difference what would be the tag?

[stukdev]

Exactly what is the sense of change the tag? Maybe is a good improve the markup syntax.
Vut if the cose is '@'code'@' or {{{code}}} or [coder]code[/coder] don't change anything.

[dangelog]

Because '@' is more likely to be found inside a source code or in other text than }}}, thus it easily screws up formatting:

@
QString email(QLatin1String("foo@ bar.com"));
@

(the above thing is broken intentionally). I'm not saying we should remove at, but simply ADD the other ones (and, for instance, leave ATs for inline code and [ code ] [ / code ] for blocks).

And still, how about supporting more than one language (namely, C++)? [ code lang = perl ] [ / code ] would make it easy.

--

To say it all, I'm hating textile. It's really fragile and really unfit for a IT / Tech forum.

[techtonik]

Most people are not familiar with Textile, and new people find its syntax rather weird. Thanks to PySide bindings you may expect many Python users who are used to Trac, Moinmoin and reStructuredText, but not to Textile. The [code] and @@ conventions are clumsy.