Tried out all the updates, they all look great!
Will respond more via github. On Thursday, September 4, 2025 at 2:44:22 PM UTC-7 Alen Šiljak wrote: > I've created the item for this feedback - > https://github.com/alensiljak/ledger2bql/issues/1 > and have resolved the main issues, as far as I can tell. While doing that, > I've had some inspiration and have completed a few more ideas tonight. > Any further feedback welcome! > > On Thursday, 4 September 2025 at 7:32:32 pm UTC+2 Alen Šiljak wrote: > >> Hey! Thanks a lot for the feedback! Note that it's been only about 2 days >> since I started writing this. I haven't really had time to use it more than >> 3 times on my real data. ;) >> The remarks are spot on and I have addressed some, like currency >> exchange. However, I'm running into an issue where Beanquery does not chain >> conversions (somehow I thought this was the default) and direct >> prices/exchange rates are required between currency pairs. Perhaps I'm just >> not aware of other ways of converting to any currency that can be chained >> from existing prices. >> >> You're right about the dates. I assumed it would shorten the queries >> while not interfering with anything else. But ok, using "-d" is not a big >> deal since the date spec happens only once per query (hopefully!). >> >> I also agree about the ledger syntax. I've started straining away from >> it. There is nothing particularly tying it to Ledger, other than my habit >> of using (a subset) of it's syntax over the years. It will probably end up >> a bit different, but mainly if it is simpler, more elegant, and/or >> effective. This will likely lead to a name change at some point. I am >> anyway using an `l` shortcut to point to the executable, making queries >> look like `l b credit`. >> >> It would be great to track feedback via issues on github, since I won't >> be able to address all of them soon but am looking forward to improving >> some of these items in the near future! Also, PRs are very welcome, even >> though I haven't explicitly added it to the readme or contributing file >> (yet!). >> >> On Thursday, 4 September 2025 at 7:41:56 am UTC+2 Red S wrote: >> >>> Nice tool to be a part of the ecosystem, I can see this being very >>> helpful, thank you for writing this and sharing! >>> >>> Some thoughts/feedback: >>> >>> - if the PAGER is used automatically, when needed, that’ll eliminate >>> having to pipe through less, given you want a tool with a minimal cli >>> burden. This is a common interface for polished CLI tools in my >>> experience. >>> click.echo_via_pager() does this for you >>> - automatic date range detection conflicts for me as I look up >>> accounts using account numbers frequently. Beancount account names can >>> include numbers (even though they can’t start with them) >>> - A way to stuff command line options into environment variables >>> would eliminate the need to keeping specifying things like --zero >>> and --total. Eg: BQ_BAL_OPTS=--zero --total >>> - Is there a way to convert balances to the default currency I’m not >>> seeing? For commodity accounts. >>> - Does the tool have to be constrained by ledger syntax? It seems >>> like it’s a good idea on its own. Would calling it something else (bq >>> for >>> beanquick?) allow the syntax to develop on its own right, suited to >>> Beancount better? >>> >>> >>> >>> On Tuesday, September 2, 2025 at 3:51:33 PM UTC-7 Alen Šiljak wrote: >>> >>>> Thank you for the link! That is useful to know. >>>> >>>> In the meantime, I've had a few ideas and have implemented various >>>> options and filters that don't exist or are not as elegant in Ledger (i.e. >>>> date range syntax). The beauty of having a tool in a language that one is >>>> comfortable with. >>>> I'm looking to minimize the syntax, so that quick queries for balances >>>> or transaction listing for a certain period, currency, payee, account, >>>> etc. can be quickly listed. With or without total or running balance. >>>> `bal` and `reg` are the most common queries I use. The filters are >>>> mostly common for both. >>>> With this tool I now feel I have a query tool that provides a quick >>>> insight into transactions and balances for everyday use, like when you >>>> need >>>> to see how much you've spent on auto electricity during the holiday >>>> period, >>>> checking if a bill to @xyz was paid, when the bills were paid, how much >>>> you've spent in certain currency, etc, etc. >>>> >>>> On Wednesday, 3 September 2025 at 12:01:47 am UTC+2 [email protected] >>>> wrote: >>>> >>>>> https://github.com/zacchiro/beangrep >>>>> >>>>> It's not quite the same thing -- it isn't trying to be similar to >>>>> ledger and doesn't cover many of the metadata'ish aspects of what you've >>>>> done -- but still might be worth looking at. >>>>> >>>>> On Tuesday, September 2, 2025 at 3:42:01 AM UTC+9:30 Alen Šiljak wrote: >>>>> >>>>>> As a poc, today I've quickly assembled and published a couple of >>>>>> scripts that provide a simpler, ledger-style queries for Beancount. >>>>>> Over the years I've become so used to using a quick "l b card" or "l >>>>>> r cash -b 2025-08" to see balances and last transactions. These tend to >>>>>> be >>>>>> my most-frequent queries, for balance checks and finding missing or >>>>>> erroneous records. >>>>>> >>>>>> If there are other Ledger-CLI converts who are missing this, feel >>>>>> free to try and suggest missing features. I will likely add more >>>>>> parameters >>>>>> and parsing for the most-common use cases I need. >>>>>> >>>>>> At the same time, before going deeper, I'd like to ask if there is >>>>>> already something of this sort out there that I was unable to find. >>>>>> >>>>>> The repo is here: >>>>>> https://github.com/alensiljak/ledger2bql >>>>>> >>>>>> -- 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 visit https://groups.google.com/d/msgid/beancount/fd73152f-e391-40ef-ae81-604c7d8fd873n%40googlegroups.com.
