New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown Extra - fenced code block: '>' before tab width parsed as block quote (Origin: bugzilla #726294) #5437

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch

On 2014-03-14 01:06:51 +0000, Tim wrote:

Given this example markdown:

template <
    typename Mixins
> class Thing : public Mixins... {};

struct FooFunctionality;
struct BarFunctionality;
struct BazFunctionality;

Thing<
    FooFunctionality,
    BarFunctionality,
    BazFunctionality
> thing;

// I hope no one ever writes an if statement like this.
if (
 a
 >
 b
)
{
    bar();
}
    
stream >> a
>> b;

stream >> a
 >> b;
 
stream >> a
  >> b;
  
stream >> a
   >> b;
   
stream >> a
    >> b;

HTML generated by Doxygen has text block withe the following content:

template <
typename Mixins

class Thing : public Mixins... {};
struct FooFunctionality; struct BarFunctionality; struct BazFunctionality; Thing< FooFunctionality, BarFunctionality, BazFunctionality
thing;
// I hope no one ever writes an if statement like this. if ( a
b ) { bar(); } stream >> a
b;
stream >> a
b;
stream >> a
b;
stream >> a
b;
stream >> a >> b;

You can see that any line that starts with a '>' before the tab width is
reached is treated as a block quote (with nesting allowed).

I guess there are 2 possible errors here:
a) Looking for block quotes within a fenced code block should not occur (my preference)
b) Block quote generation within a code fence is incorrect (I don't really know why anyone would want to do this)

I have tested this on both 1.8.5 and 1.8.6

On 2014-03-17 20:34:19 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-04-21 10:09:27 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment