Bryce I agree one configs folder. Also we can move doxigen file here.
On Sat, 2017-07-15 at 10:32 -0700, Bryce Harrington wrote:
On Sat, Jul 15, 2017 at 05:46:14PM +0200, Jabier Arraiza wrote:
> Hi Bryce thanks for your deep inform:
>
>
> > ---------------------------------------------------------------
> > ----
> > -----
> > + astylerc
> >
> > This config file appears to be for a code formatting tool. I
> > vaguely
> > remember kk discussing it a while back. Is anyone still using
> > it?
> >
> > The astyle man page indicates it supports using --
> > options=FILENAME to
> > specify a path to astylerc, so the file could be moved to utils/
> > or
> > elsewhere.
> >
> > I see we already have the options documented at
> >
https://inkscape.org/en/develop/coding-style/ including
> > directions
> > for how to store the settings locally in ~/.astylerc. If no one
> > is
> > actively using this tool, that might be a better solution and
> > remove
> > astylerc from the codebase.
> >
> >
> > ---------------------------------------------------------------
> > ----
> > -----
> > + _clang-format
> >
> > I'm not sure why this is in the tree. Guessing it was a jenkins-
> > related thing? I suspect we can drop this.
> >
>
> Is a similar objective than astylerc both need external programs to
> run maybe we need to select the less intrusibe or the best OS
> compatibility one
> True, yes, not a bad idea. Alternatively, if we're going to have a
collection of such things, they could be housed in a subdirectory
somewhere. Projects will often carry configs for vim, emacs, and
other
editors... Having them in one place might also make it easier to
spot
discrepancies in each other's formatting configurations.
Bryce