Activity for David Haney

  • David Haney David Haney posted a comment on ticket #11

    I think this makes sense, I just want to make sure I'm capturing the scenarios correctly. Given a directory structure like: root base .astylerc cpp java .astylerc Assuming that base is the top-level folder for the project: If astyle is invoked from /root/base/java with no arguments, /root/base/java/.astylerc will be used. If astyle --recursive is invoked from /root/base/java, /root/base/java/.astylerc will be used. (this seems to contradict the last sentence of your second paragraph, but I'm not...

  • David Haney David Haney posted a comment on ticket #11

    @Jim I think what you're describing is pretty close to what I was looking for (and I think what I implemented in my patch). Maybe a specific example would help to clarify. Let's say I have a directory structure like: base .astylerc cpp java .astylerc If I call astyle from the base/java directory, I would expect the configuration in base/java/.astyle to be used (it was found in the directory where I invoked astyle). If I call astyle from the base/cpp directory, it would use the configuration in base/.astylerc...

  • David Haney David Haney posted a comment on ticket #11

    I wasn't able to access the patch proposed by Hannes Eder, so implemented a new version. This patch sets a new environment variable ARTISTIC_STYLE_PROJECT_OPTIONS. The patch will search for the file identified by this environment variable in the current directory or any parent directory. The first instance that's found will be used as the option file. If the file isn't found, it will fallback to the traditional search path for option files.

1