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

Continuation data for parameters to aliases adds a "/" character (Origin: bugzilla #618079) #3768

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 minor in component general for ---
Reported in version 1.6.2 on platform Other
Assigned to: Dimitri van Heesch

On 2010-05-08 04:05:11 +0000, blort_blort@yahoo.com wrote:

Using the Aliase in the config file:

ALIASES += funcid{2}="\par Function \2 in CSU \1"

and putting in the code:

/// \funcid{something
/// first, another
/// second}

The output adds a "/" character for each continuation line - see below

Function another
/ second in CSU something / first

When the input is changed to (note /// changed to //):

/// \funcid{something
// first, another
// second}

The output is also messed up as everything should be on one line:

Function another
second in CSU something first

In both cases I expected the output to look like:

Function another second in CSU something first

In addition, I have tested with several other aliases that aren't as strange as FuncId. All of them still have the "/" character added when the parameter is continued on the next "///" line.

On 2010-06-11 21:52:37 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-06-15 11:22:20 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.0. 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.

@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