That's fine Wolf. I really meant that in case you have some Perl experience. There are certainly many different issues (see good first issue label), but similar to the Perl issue is what you get when running `shellcheck */*.sh`.
https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 On Sat, Oct 2, 2021 at 7:02 AM Wolf Bergenheim <wolf+gr...@bergenheim.net> wrote: > Ugh. I give up. Perl and I just agreed to go our separate ways :P > > --Wolf > > *-- * > * ^.___* > > *( ,__// / Wolf Bergenheim* > > > > On Sat, 2 Oct 2021 at 12:01, Wolf Bergenheim <wolf+gr...@bergenheim.net> > wrote: > >> Hey Vaclav, >> >> Sure, perl is by no means an area I know much about, but looks quite >> simple :) >> >> *-- * >> * ^.___* >> >> *( ,__// / Wolf Bergenheim* >> >> >> >> On Sat, 2 Oct 2021 at 10:23, Vaclav Petras <wenzesl...@gmail.com> wrote: >> >>> >>> >>> >>> On Fri, Oct 1, 2021 at 10:31 AM Wolf Bergenheim < >>> wolf+gr...@bergenheim.net> wrote: >>> >>>> Mainly I'm looking for opportunities to contribute after 10 years away >>>> :P >>>> >>> >>> Hi Wolf, >>> >>> If you are looking for suggestions, there are some Perl linting issues >>> in grass-addons repo I just stumbled across. >>> >>> https://github.com/OSGeo/grass-addons/issues/619 >>> https://github.com/OSGeo/grass-addons/issues/620 >>> >>> Besides Python and C, some Bash linting fixes might be needed too, but >>> I've never looked into those except for disabling the check. >>> >>> Best, >>> Vaclav >>> >>
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
