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

ampersands are not processed in filename (Origin: bugzilla #675607) #4696

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-05-07 12:07:29 +0000, Radek Liska wrote:

TCL source code header:

@file MCO/CL-B&R.tcl

D:/_src/ttt/MCO/CL-B&R.tcl:4: warning: the name `MCO/CL-B' supplied as the second argument in the \file statement is not an input file
The same happens for CL-B@&R.tcl, CL-B&R.tcl, CL-B&R.tcl. It also happens for CL-B@R.tcl, I didn't try more combinations.

On 2013-04-20 12:36:15 +0000, albert wrote:

Created attachment 241987
PATCH enable @ and & in file / directory name

The @ and & characters are added to the file names as used in commentscan.l, this
solved the problem as noted. For consistency the @ and & have also been added to the file patterns in doctokenizer.l

This bugfix superseded the bug fix for bug_657883 as it also contains that bug fix (the fix for scanner.l is already in svn)

On 2013-04-20 12:37:25 +0000, albert wrote:

*** Bug 657883 has been marked as a duplicate of this bug. ***

On 2013-04-20 16:56:06 +0000, albert wrote:

Following from bug_494760 - Directory path with '#' charactor in Doxywizard the # character should also be incorporated in patch. This has not been done.
When accepting the patch please add the # character as well.

On 2013-05-10 14:26:12 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update and add '#' as well.

On 2013-05-19 12:35:25 +0000, Dimitri van Heesch wrote:

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