Adrien, I'll note that Geert's proposal only requires the user to add a switch at run time--i.e., "gnucash --extra". There is no need for the prospective report writer to recompile.I
David On May 21, 2019, at 9:43 PM, Adrien Monteleone <adrien.montele...@lusfiber.net> wrote: I’m in agreement there. If someone did take the plunge into scheme and they wanted to work on those particular reports, asking them to compile with flags isn’t a stretch for them at that point. The less clutter and cruft the better, especially for new users. Regards, Adrien > On May 21, 2019, at 7:09 AM, David T. via gnucash-user > <gnucash-user@gnucash.org> wrote: > > > I am not a fan of keeping reports that *no one uses* included in the > application, on the offhand chance that some new user might decide to learn > scheme and the gnucash api to write a new report. As noted in the bug, this > has not been a particularly common occurrence. > > Geert's solution is a good compromise, IMHO. > > It would be easy enough to add a note to the Custom Reports wiki page to > explain how a user would activate this. > > David _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
