Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different file for completions #73

Open
csamak opened this issue Mar 14, 2023 · 5 comments
Open

Different file for completions #73

csamak opened this issue Mar 14, 2023 · 5 comments

Comments

@csamak
Copy link

csamak commented Mar 14, 2023

Would it make sense to allow specifying two journal files - one for completions and one for writes?

This would be useful with multiple journal files. With one journal file per year (2022.journal, 2023.journal, etc), completions become fairly useless every January. Separate files in the config would allow completion suggestions from an all.journal (which includes all individual files) while still only writing to 2023.journal.

@simonmichael
Copy link

simonmichael commented Mar 15, 2023

I don't relish complicating things, but yes I too have wanted something like this, also for hledger add, for editor modes like ledger-mode, and for history-aware CSV conversion/import.

@hpdeifel
Copy link
Owner

yep, I've also wanted this on occasion 👍

@soenderg
Copy link

That would be extremely useful! I'd really appreciate this too. I keep my hledger journals per year, so as have already been mentioned, completion only becomes useful quite a bit in the new year. Some yearly expenses won't complete until very late in the year. It would be awesome if hledger-iadd could just read one (or more) journals only for completion purposes.

@simonmichael
Copy link

simonmichael commented Jan 19, 2025 via email

@soenderg
Copy link

hledger-iadd unfortunately doesn't work this way. But that exact behaviour would be so helpful. Maybe this could be my first "learning Haskell" oportunity.

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

No branches or pull requests

4 participants