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

How different is vim-beancount from vim-ledger? #55

Open
alerque opened this issue Jul 11, 2019 · 1 comment
Open

How different is vim-beancount from vim-ledger? #55

alerque opened this issue Jul 11, 2019 · 1 comment

Comments

@alerque
Copy link

alerque commented Jul 11, 2019

Hey! I have recently stepped in to help maintain and develop the vim-ledger plugin. One of the things I'm interested in doing for it is expanding it from it's original mission of working with ledger-cli to also work well with hledger. This is not a radical shift, but it does require a few tweaks to the syntax highlighting to pick up some alternate forms, and also tweaking the way it runs shell commands for each engine.

I don't actually know a lot about the beancount ecosystem, but as I've started working I got to wondering: just how different is Beancount's syntax and the things this plugin does (or people would want it to do) from what (h)ledger does? Would in be possible to converge development on the vim plugin side of things and support all three syntax variants and commands out of the box? Or are there more radical differences that would make such an undertaking a conflict of interest that wouldn't be good for either plugin?

@tbm
Copy link

tbm commented May 26, 2020

I'm not the author of this vim plugin but beancount syntax is much more different compared to ledger than hledger vs ledger (which only differs in minor ways).

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

No branches or pull requests

2 participants