On Sun, May 05, 2019 at 08:09:30AM -0400, Martin Blais wrote: > One often recurring issue is that of new users getting confused about > options in included files. I'm contemplating simply disabling them to > avoid confusion. Does anyone care for options in included files, or > use them for anything useful? (AFAIK they shouldn't be working.)
What is confusing is that they work in the main file but not in included ones. Disabling them completely from included files (which is what I'm assuming your proposal here is) wouldn't make it any less confusing. More generally, when you have file inclusion support in some sort of language/templating system, the general expectation is that it is should be completely transparent and that you can always "refactor" your files any way you like without incurring in semantically meaningful changes. I have no idea how hard it would be to get that with Beancount (maybe inclusion should just become a purely textual operation, delegated to a "dump" file processor?), but IMHO *that* is what will make file inclusion not confusing at all. Cheers -- Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o Computer Science Professor . CTO Software Heritage . . . . . o . . . o o Former Debian Project Leader & OSI Board Director . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20190505122950.ykny3trnimpwmbo3%40upsilon.cc. For more options, visit https://groups.google.com/d/optout.
