So, the problem was, you were running out of keyboard shortcuts; you probably have more than 75 categories. So, I've changed how into-ledger assigns keyboard shortcuts to use the natural hierarchy of ledger accounts. This would make more keyboard shortcuts available, and they'll be context sensitive.
Do a go get -v -u; so it would also pull in the updated dependencies. Regarding alias, I was referring to the aliases that ledger allows: http://ledger-cli.org/3.0/doc/ledger3.html#Command-Directives My ledger file assigns aliases to accounts. If yours doesn't, it's alright. This isn't specific to into-ledger; so no changes required to your conf.yaml. On Fri, Dec 9, 2016 at 7:25 AM, Bren Smith <[email protected]> wrote: > Okay, I’m getting further along here but don’t quite seem to be able to > cross the finish line. I think you’re getting me closer though! Here’s the > most recent output from running after upgrading: > > into-ledger -a wells-primary -csv Primary-Checking-0405.2016-11- > 29-2016-12-06.csv > > Opening file: /Users/bren/.into-ledger/shortcuts.yaml for reading key > mappings > Using config: {Currency:USD Journal:/Users/bren/Documents/ > Personal/Financial/CLA/Ledger/smith.finances.journal > DateFormat:01/02/2006 Ignore:4 Output:/Users/bren/Documents/ > Personal/Financial/CLA/Ledger/wells-primary.out} > 2016/12/08 12:18:53 Unable to assign any char for > Expenses:Household:Apartment-Buildout > > Yes, I did define an account in my config.yaml with: > > ################ > accounts: > wells-primary: > currency: USD > journal: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > smith.finances.journal > dateformat: 01/02/2006 > ignore: "0" > output: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > wells-primary.out > ################ > > I created the above by using the example given on your GitHub page: > > https://github.com/manishrjain/into-ledger > > You’ve indicated that I should also have an alias? Would this be an alias > for each account that I have in Ledger? Or are you intimating that each > account should have an alias? > > e.g. > > ################ > accounts: > wells-primary: > alias wellsprim <— > currency: USD > journal: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > smith.finances.journal > dateformat: 01/02/2006 > ignore: "0" > output: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > wells-primary.out > ################ > > or > > ################ > accounts: > wells-primary: > currency: USD > journal: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > smith.finances.journal > dateformat: 01/02/2006 > ignore: "0" > output: /Users/bren/Documents/Personal/Financial/CLA/Ledger/ > wells-primary.out > account Expenses:Household:Apartment-Buildout<— > alias apartment <— > ################ > > I think my confusion revolves around not seeing where “alias” is defined > for into-ledger on your GitHub page. > > Many thanks for all you’ve done! > > Bren > > On Thursday, December 8, 2016 at 12:32:56 AM UTC-8, Manish Rai Jain wrote: >> >> It looks like you have defined an account, but not a corresponding alias. >> >> account Expenses:Shopping >> alias shop >> >> The previous code wasn't very smart about it. I've modified the code now >> to be smarter and to silently skip if it can't find what it's looking for. >> So, update the code and try again. >> >> One more thing I noticed. You have set ignored to column "0", but that's >> the only column which contains the date. This should cause some problems. I >> think you need to skip column 2 and 3 -> "*", "". 0 contains date, 1 >> contains amount and 4 contains transaction details; from what I can see. >> > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
