After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 504305 - FILTER_PATTERNS won't take command with arguments
FILTER_PATTERNS won't take command with arguments
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.4
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 690864 700148 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-12-18 18:32 UTC by Anthony Foglia
Modified: 2016-09-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Anthony Foglia 2007-12-18 18:32:18 UTC
INPUT_FILTER and FILTER_PATTERNS have differing functionality.  I can give INPUT_FILTER a string containing a command and its arguments, but when I try to set FILTER_PATTERN to do the same, doxygen is unable to run the command.

For example, I can have:

INPUT_FILTER = "doxypy.py --autobrief"

and the filter if found and run.

But since doxypy.py only filters Python files, I'd like to have

FILTER_PATTERNS = *.py="doxypy.py --autobrief"

But Doxygen can't parse that properly.  Instead, I get the error message:

sh: doxypy.py --autobrief: command not found

If I remove the command-line argument ("--autobrief"), the filter is found and run without errors.
Comment 1 albert 2016-01-31 13:21:09 UTC
I've just pushed a proposed solution to github (pull request 449)
Comment 2 Kevin McBride 2016-01-31 18:12:22 UTC
*** Bug 700148 has been marked as a duplicate of this bug. ***
Comment 3 Kevin McBride 2016-01-31 18:12:37 UTC
*** Bug 690864 has been marked as a duplicate of this bug. ***
Comment 4 albert 2016-02-03 10:16:31 UTC
Code has been integrated in github
Comment 5 Dimitri van Heesch 2016-09-05 13:45:55 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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 (preferably in the form of a self-contained example).