Thanks for that clarity. That scope makes perfect sense. I'll build what I 
need and share, and hope others do the same :).

Agree with rename: I was thinking of that as a "hello world" starter 
high-level function, but there are probably more meaningful things. For 
example, to "bake in" plugin-transformed transactions. Eg: zerosum 
<https://github.com/redstreet/beancount_reds_plugins/tree/main/beancount_reds_plugins/zerosum>.
 
I do have per-account files, and need to first find a good way to write 
back to the same location a transaction was read from.

Thanks, and I look forward to the updates!

On Wednesday, October 19, 2022 at 12:22:05 PM UTC-7 [email protected] wrote:

> Glad it feels useful to you.
>
> I'd like to limit the scope of this project to AST manipulation and things 
> currently on my plan are:
>
>    - Performance improvements. Most operations currently unnecessarily 
>    takes O(number of token) time.
>    - Stabilize the interface (e.g. simpler interface to get token 
>    position, print model, parse files recursively following `include`, ...)
>    - Documentation
>    - Support of out-of-line tags / links.
>
> I'll probably build higher level stuff in separate projects afterwards but 
> I don't have a concrete plan yet (the first one might be a formatter that 
> also supports sorting). Also feel free to build your own stuff!
>
> In relation to `rename_account(old_name, new_name)`, I personally feel it 
> is a simple task where regex substitution does better than this library. 
> This library would be more useful for slightly more complex cases like "I'd 
> like to split all my expenses on tea, as marked by a posting meta, into a 
> new subaccount" but those use cases tend to be very case-specific and 
> difficult to generalize. But if you have some ideas what people might need 
> in common, feel free to just build higher level tools on top of it!
>

-- 
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/fd0be169-5a6b-4168-a567-891ad13da605n%40googlegroups.com.

Reply via email to