-
Notifications
You must be signed in to change notification settings - Fork 55
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
"Nothing to reconcile" #123
Comments
I also am getting this with hedger. Something else that needs to be configured? Here's my rc:
|
@alerque I'd love to see this working. I've tried a few older versions from git history, but all give the same error. It's Open Source: I know I get to break it and keep all the bits. If you're able to give any pointers to debugging this, I'd be very grateful (I find Vimscript a bit opaque, but with some clues I may be able to make some progress). If more information would help, just tell me what you need. Thanks, |
I'm sorry, I don't actually have a good idea what to look for on this on. I'm happy to facilitate a fix if somebody has one, but my FOSS time is kind of being sucked up by some other projects right now (and my personal finances are behind, maybe when I get to them...). |
I can try to take a crack at solving this. Could you provide a sample register where you still get the same errors? |
Any update on this issue? I experienced the same issue. @parmort, here is my sample register.
My
|
As far as I can see from a cursory review of the code, the Reconcile command ( @parmort feel free to take a swing at this, or if you think you won't get to it lets note that here so somebody else can try without feeling like they may be duplicating effort. @p4kl0nc4t Thanks for the MWE, that example does show the error for me when configured with |
Running: 96ec5f9 - (HEAD -> master, origin/master, origin/HEAD) Merge pull request #112 from kcwu/post-state (6 months ago)
Using hledger
Enter :Reconcile and I get "Nothing to reconcile"
Probably user error. What should I look for?
The text was updated successfully, but these errors were encountered: