The only problem I have with it is that the author is terribly fond of weird self-referential puns and wordplay, and I find the docs (and posts and comments) he writes to be basically unreadable.
Even the project names: osh, and ysh, and oils, where osh is short for Oil Shell, but so is OilS I think...
It makes it really annoying and difficult to read, IMHO. Maybe it's just me.
As a haskeller, and shell scripter, I find this a refreshing and exciting experiment.
Much of the goodness of haskell, but with a much tighter focus and smaller scope.
No imports, language pragmas, packages or build tools needed;
all of the building blocks listed on one short page, https://chrisdone.github.io/hell/api.
More platform independent, robust, and regular than shell.
Potentially a nice learning language / stepping stone to haskell itself.
It's quite verbose right now, and I don't see much networking API yet, but it's just starting. I could see it easily growing into something very nice.
If you're giving a presentation, you should start by telling the audience what it is you're talking about. Someone in the audience won't have a clue, and usually most of the audience have no clue.
Just thank you very much, Mike and the large team of maintainers you've organised!
I was reading here about GnuCash yesterday. That's an old, GUI, non-mac app, surely a bit too much hassle to try out quickly I guessed. But brew install gnucash got me running it in seconds.
Not to go off topic - this story did inspire me to install gnucash again and enjoy the GUI -
> parsing it in a structured way is a nightmare
Ah, well that’s the job of the PTA app - converting “just text” to something very structured and validated. Which can then be moved into SQLite, if one likes.
> and scripting edits to plain text is a mess.
I suppose it depends. There are a lot of very powerful and quick tools and techniques for automated or assisted text munging.
I do some things to try to separate and subtly prioritise bug reports and discourage excessively cluttering the tracker with ideas (some are useful to discuss there, but not all).
- Issue types, using labels: (Almost) every issue’s first label is A-BUG in weighty red or A-WISH in less substantial pink. The spellings keep these two first among labels and most visible. The word “wish” is carefully chosen. I attach one of these on first sight of a new issue.
- Shortcut urls that redirect to a view of one or the other of these, making it easy (for me at least) to focus: bugs.foo.org and wishes.foo.org showing just those, issues.foo.org showing both, prs.foo.org, regressions.foo.org, etc.
- New issue template that gives (short!) guidance and a hint that mail list and chat room are good for discussion and brainstorming. (GH Discussions would be pleasant now, but I’m not keen to fragment discussion more, or lock in even more on GH)..
For most PTA users, 1 million transactions would be a large file; we usually split them up more.
On a macbook air m1, here's how hledger 1.40 from homebrew handles it
(it used to be faster; perhaps this will improve again):
$ hledger -f examples/1Mtxns-1kaccts.journal stats
Main file : .../1Mtxns-1kaccts.journal
Included files : 0
Txns span : 2000-01-01 to 4737-11-28 (1000000 days)
Last txn : 4737-11-27 (990974 days from now)
Txns : 1000000 (1.0 per day)
Txns last 30 days : 31 (1.0 per day)
Txns last 7 days : 8 (1.1 per day)
Payees/descriptions : 1000000
Accounts : 1000 (depth 10)
Commodities : 26
Market prices : 1000000
Runtime stats : 80.23 s elapsed, 12465 txns/s, 2584 MB live, 7679 MB alloc
Ledger was traditionally faster on at least some reports, but I haven't been able to reproduce that on my machines for some time. Today, with the same file above, it ran for 40m before I killed it.
In my experience about half the time is spent on parsing and half on report calculation. Long-running apps like hledger-ui and hledger-web do the parsing only once at startup, saving time compared to CLI commands.
To be precise, hledger-ui is not an editor, but it can open hledger add, hledger-iadd, or your $EDITOR[1] for data entry, all of which can complete account names. Web guis like hledger-web and Paisa tend to complete account names as well.
reply