Thanks for the help. So I guess the first step is defining my metadata key *pn* for post-narrations.
Then the next step would be to see if a plugin can be written to parse strings that come after the amounts and insert them into the pn metadata automatically. I don't believe such a plugin exists already. I've found various plugins here and there but no centralized directory of user plugins to confirm this. I hope that the plugin can suppress Parser errors. On Saturday, September 5, 2020 at 2:48:38 AM UTC-5 Máté Farkas wrote: > On Sat, Sep 5, 2020, 08:33 Martin Michlmayr <[email protected]> wrote: > >> * Mefju <[email protected]> [2020-09-05 08:23]: >> > I also use narration for postings, and also miss that Beancount does not >> > parse comments. >> >> IHMO that's a feature and not a bug. > > > That's definitely not a bug, it is by design, I checked the source code. > > On the other hand I think there is information loss because of it. > Beancount has a cool syntax to comment a transaction, a posting, > unfortunately I cannot access it progmamatically. So I have to use the not > so cool "put your comment in metadata" feature, so I can access it. (Having > metadata is amazing by the way.) > >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/de0c2d1c-d3e4-45ae-80ee-9af670e779dcn%40googlegroups.com.
