Wiki formatting lost in ">" quoted blocks

[anonymous]

1. Why not allow editing comments along with ticket itself?
2. When replying to comment with quoting, wiki formatting will be lost in quoted text (e.g. numbering 1. 1. 1.)

[cboos]

1. See #454
2. Yes, that would be a good thing.

... and:

3. What do you think about having two reply buttons, one "Quote" doing what "Reply" does today, and "Reply" simply adding a reply to a specific comment, without quoting?

This would be especially interesting once we have #1835 (threaded view for comments).

[mgood]

I'm updating the summary to reflect the core issue with the quote formatting. Right now it's possible to remove the ">" in front of some types of blocks and they'll be formatted, but still included in the quote.

For example:

> a
{{{
b
}}}
> c

is displayed as:

a

b

c

Replying to cboos:

3. What do you think about having two reply buttons, one "Quote" doing what "Reply" does today, and "Reply" simply adding a reply to a specific comment, without quoting?

Coincidentally I just finished reading this Joel on Software article Choice = Headaches. Providing two buttons that do almost exactly the same thing adds unneeded clutter to the UI. It only takes a second to clear the textarea, so I'd rather keep just the one button.

[sid]

#4095 was marked as duplicate of this ticket. It also noted that blank space is lost when replying to tickets.

For example, this:

> test
>
> test2

shows up as:

test test2

[cboos]

Right, the quoting related stuff in the Wiki engine really needs some improvements. I'm thinking of having "line prefix"-style rules that would be applied in turn, so that one could quote lists or other type of formatting (like tables).

[eblot]

#4606 marked as a duplicate

[cboos]

#4615 also...

[cboos]

And another duplicate: #4965. I teally need to find some time to finish the WikiEngine refactoring :-)

[cboos]

WikiEngine refactoring postponed.

[cboos]

#6683, another duplicate, about the ability to quote code blocks.