Skip to content

Conversation

@alerque
Copy link
Collaborator

@alerque alerque commented Jan 21, 2026

This implements the same --drop functionality as balance command for register subcommand, allowing users to trim leading account name components from register output.

@simonmichael
Copy link
Owner

Nice! Would you mind mentioning it briefly in the body of Register.md also. (The flags list at the top will be regenerated before release, so updating that is optional.)

@alerque alerque force-pushed the add-drop-flag-to-register branch from 2860b63 to 5aa16af Compare January 22, 2026 08:22
@alerque
Copy link
Collaborator Author

alerque commented Jan 22, 2026

Something like that?

@simonmichael
Copy link
Owner

Great. There's still a build warning; hopefully just functest reproduces it on your machine. (If not, try a stack clean --full first.)

@alerque
Copy link
Collaborator Author

alerque commented Jan 23, 2026

Unfortunately none of the just tasks or default invocations of stack work for me at all (due to old ghc, lack of ghcid, etc.) so part of the reason to get the PR open was to get CI results.

@alerque alerque force-pushed the add-drop-flag-to-register branch from 5aa16af to ac26388 Compare January 23, 2026 11:29
This implements the same --drop functionality as balance command for
register subcommand, allowing users to trim leading account name
components from register output.
@alerque alerque force-pushed the add-drop-flag-to-register branch from ac26388 to 1f911cf Compare January 23, 2026 11:43
@simonmichael
Copy link
Owner

Unfortunately none of the just tasks or default invocations of stack work for me at all (due to old ghc

Could you help me understand this kind of situation better ? What ghc version(s), installed by what method, do you have ?

@simonmichael
Copy link
Owner

PR looks good - thank you!

@simonmichael simonmichael merged commit e3cf646 into simonmichael:master Jan 23, 2026
1 check passed
@alerque alerque deleted the add-drop-flag-to-register branch January 23, 2026 19:15
@alerque
Copy link
Collaborator Author

alerque commented Jan 23, 2026

Could you help me understand this kind of situation better ? What ghc version(s), installed by what method, do you have ?

GHC 9.6.6 installed by system packages on Arch. Yes it is ancient, yes there is work being done to update it, but our whole Haskell stack being dynamically linked is a huge pain point. GHCID is just not packaged at all, probably because it wasn't compatible with whatever ghc we had a while back and had to get dropped to unblock a ghc update. I see it does actually build at the moment. I'll check on it again when the GHC stack gets fully up to date and see if it can get added.

@simonmichael
Copy link
Owner

simonmichael commented Jan 23, 2026

Ah Arch. (It's always Arch. :) But, GHC 9.6 is still supported by hledger, so it shouldn't be a big deal to use it. It might be enough to change this line in Justfile (make it use stack96.yaml):

#STACK := 'stack --stack-yaml=stack912.yaml'

ghcid is not something you need, probably. I use it only when HLS in VS Code isn't working.

We do want it to be easy for everyone to be able to run just test or just functest though.

@simonmichael
Copy link
Owner

Related: recent discussion of Justfile/test portability and dev docs at #2528.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants