Re: ledgible: a web interface for ledger-cli (with data entry!)
Hi Ankur, I'm trying to build Web interface for ledger CLI . Could you please help me with few of my queries -- 1> Does Ledger - CLI reads only from .dat file ? 2> I want to give user access to input his transaction details from front - end. So were can I store that incoming new data ? Can I use any DB for that ? Thanks Manish On Wednesday, March 9, 2016 at 12:02:03 PM UTC+5:30, Ankur Kothari wrote: > > Hello! > > I have used ledger-cli for some time, and wanted my family and friends to > be able to use it. > > Since not everyone is a programmer, I made a web interface for ledger. My > mother and my wife have been using it since mid-2015. It is actually so > convenient that I use it myself. > > So if you want: > >- your accounting information accessible everywhere >- easy entry of transactions (auto-completion which learns from past >entries!) >- interactive visualizations of your finances > > Then please check it out here <https://github.com/lipidity/ledgible> and > give me feedback. > -- --- 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Exchange a specific currency in report
Hey, Is there a way to only exchange transactions from one currency; while keeping the others intact. I have txns in USD, AUD and INR. I want my report to show me USD and AUD; and convert the ones in INR to USD. If I use the --exchange flag, it would exchange everything, including the AUDs, which I don't want to. Cheers, Manish -- --- 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Monthly report using --depth 1
I'm trying to run this: ledger -f journal.ldg reg Expenses Tax -MA --depth 1 so I can get a monthly average of expenses. But, this doesn't return any results. The minimum depth I can pass is 2, which doesn't give me just the overall expenses, instead breaking it down into further categories. Is there a way to achieve average of the whole expense category? Cheers, Manish -- --- 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Share] Report Scripts for Ledger CLI with Gnuplot
I'm in a similar boat. I've been using ledger for over a year now, but long for a good data visualization tool to work with ledger. I tried a solution mentioned in http://plaintextaccounting.org/, but it doesn't seem to work. Your scripts seem like a step in the right direction. Would be great if you'd also handle multiple currencies. On Sun, Jan 15, 2017 at 3:04 AM, Jason Checkwrote: > Thanks for posting. These look great! > > > On Monday, January 2, 2017 at 12:38:48 PM UTC-6, Shaodong Di wrote: >> >> Hi, I've been using Ledger for a year now. I made 6 script with Gnuplot >> based on Ledger's default report script. They plot good graphs, detailed >> can be found on my blog post: https://www.sundialdreams.com/ >> report-scripts-for-ledger-cli-with-gnuplot/ >> I hope it can help build a great personal financial report of 2016. >> >> P.S. Happy new year! >> > -- > > --- > 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Monthly average expenses for budgeting
Hard to explain the difference between documents and documentation. To me, it's clear -- sort of like Dropbox has file versioning, but that doesn't make it a version control system. The requirements of producing office related documents, isn't the same as providing documentation to end users. And hence, the systems designed around these requirements are inevitably different. But, I digress. The point is, I think ledger documentation could use a revamp. As a relatively new user (been over a year), I know a few basic commands, that I get by. But, any time you want to dig deeper, things feel a lot unclear and complicated. On Sat, Dec 17, 2016 at 10:15:13PM -0500, Martin Blais wrote: > On Sat, Dec 17, 2016 at 9:40 PM, Manish R Jain <manishrj...@gmail.com> > wrote: > > > I meant these templates: > > https://en.wikipedia.org/wiki/Help:Template > > > > Google Docs is nice and easy WYSIWYG, but the end result isn't going to be > > as good; because it's HTML output is going to be manual and basic. It's > > designed for documents, not really documentation. > > > Not to be facetious, but can you describe the difference between > "documents" and "documentation?" I don't know what it is. Documentation is > documents AFAIK. You could document your project with LaTeX and that would > be a fine choice. LaTeX produces documents. > > I think what you might mean is that there's a shortage of semantic markup > to address the specific needs of documenting a software artifact. For > example, the absence of a "code block" element. I would agree to that, if > that's what you mean, though in my specific case I feel that the enhanced > collaborative ability has largely made up for it and the occasional > annoyance at having to make a code block into a meaningless "Consolas 10pt." > > > > > Some of the best documentation is hosted on wiki: > > > > https://wiki.archlinux.org/ > > https://wiki.gentoo.org/wiki/Main_Page > > > > Not to mention Wikipedia itself. I say this, because we had the same > > discussions when using Wiki for Dgraph as well; and similar points and > > solutions were raised. It's an older software, a bit harder to set up, and > > uses unpopular syntax, agreed. But, once you get past that, it's a delight > > to work with and the end result is just astounding. We couldn't be happier > > having made the decision to switch to Wiki. > > > > > > On Sat, Dec 17, 2016 at 07:56:43PM -0500, Martin Blais wrote: > > > On Sat, Dec 17, 2016 at 7:25 PM, Manish Rai Jain <manishrj...@gmail.com> > > > wrote: > > > > > > > > > > > - And this is where Wiki really shines -- that is templates. You see a > > > > section which is incorrect, needs work, out of date, or want to have a > > > > special note, add a warning; you can add a special highlighted box in > > Wiki. > > > > That adds a real value for the end user. No other solution does that -- > > > > Google docs or Github. > > > > > > > > > > Not entirely accurate. Google Docs allows the user to either (a) > > highlight > > > the offending text and leave a comment in the margin (along with a button > > > for me to mark it resolved when I fix it and it makes the comment go > > away), > > > or (b) directly make the suggested edit - an email is sent to me and I > > can > > > choose to accept or reject it on the spot. No switching to source, no > > > markup, it's all right there in the doc and notifications are sent by > > email. > > > > > > -- > > > > > > --- > > > 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 ledger-cli+unsubscr...@googlegroups.com. > > > 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 ledger-cli+unsubscr...@googlegroups.com. > > 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Monthly average expenses for budgeting
I meant these templates: https://en.wikipedia.org/wiki/Help:Template Google Docs is nice and easy WYSIWYG, but the end result isn't going to be as good; because it's HTML output is going to be manual and basic. It's designed for documents, not really documentation. Some of the best documentation is hosted on wiki: https://wiki.archlinux.org/ https://wiki.gentoo.org/wiki/Main_Page Not to mention Wikipedia itself. I say this, because we had the same discussions when using Wiki for Dgraph as well; and similar points and solutions were raised. It's an older software, a bit harder to set up, and uses unpopular syntax, agreed. But, once you get past that, it's a delight to work with and the end result is just astounding. We couldn't be happier having made the decision to switch to Wiki. On Sat, Dec 17, 2016 at 07:56:43PM -0500, Martin Blais wrote: > On Sat, Dec 17, 2016 at 7:25 PM, Manish Rai Jain <manishrj...@gmail.com> > wrote: > > > > > - And this is where Wiki really shines -- that is templates. You see a > > section which is incorrect, needs work, out of date, or want to have a > > special note, add a warning; you can add a special highlighted box in Wiki. > > That adds a real value for the end user. No other solution does that -- > > Google docs or Github. > > > > Not entirely accurate. Google Docs allows the user to either (a) highlight > the offending text and leave a comment in the margin (along with a button > for me to mark it resolved when I fix it and it makes the comment go away), > or (b) directly make the suggested edit - an email is sent to me and I can > choose to accept or reject it on the spot. No switching to source, no > markup, it's all right there in the doc and notifications are sent by email. > > -- > > --- > 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Monthly average expenses for budgeting
Completely agree with Martin about non-technical users and ease of edits. To add some more thoughts from our experience using Wiki at Dgraph: https://wiki.dgraph.io - The amount of work required to submit a change to Wiki is **considerably lesser** than doing the same on Github. Consider this, you're consuming the documentation in a browser. You see an issue, if you're logged in, you'll see an edit next to the section, which you can click, fix the issue, and submit. The Github flow is, OTOH, designed not for quickly updating documentation, but for writing code. You switch away from browser; do a git clone or a git pull, do the mod in the entire doc (no section level edit), commit, create a PR, wait for it to be reviewed, address potential issues with the PR, and then wait until it gets submitted. The process complexity is the same whether it's a minor edit or a major one. The result is that Github flow isn't done by most consumers of the documentation. The smaller the edit is, the more neglected it would be. - Wiki formatting is slightly inferior to Markdown but isn't much different (the existing Texi is considerably harder to follow). So, the learning curve isn't all that much. Minor edits wouldn't need to worry about this anyway -- you just see what's around, and follow. - And this is where Wiki really shines -- that is templates. You see a section which is incorrect, needs work, out of date, or want to have a special note, add a warning; you can add a special highlighted box in Wiki. That adds a real value for the end user. No other solution does that -- Google docs or Github. Case in point: https://wiki.dgraph.io/Beginners_Guide . Templates are particularly useful for users who don't know how to fix the issue but can add a "needs fix" template in the right place in the documentation to let everyone else know that there's an issue here. This is a much better solution than using Github issues because you can see the issue when reading the documentation -- they're in the same place. You'll probably still need Github issues, but they'd be for major doc issues. So, what do you give up by moving to Wiki? I'd say nothing really. A one-time script can convert the Texi format to Wiki Syntax. What new things it would bring? All the above; particularly ease of edits and templates. On Sun, Dec 18, 2016 at 7:17 AM, Martin Blais <bl...@furius.ca> wrote: > On Sat, Dec 17, 2016 at 8:20 AM, Brian Exelbierd <b...@pobox.com> wrote: > >> On Sat, Dec 17, 2016, at 01:39 PM, Manish Rai Jain wrote: >> >> Thanks! That definitely helps. >> >> I think the documentation needs updating (documentation being one of my >> main gripes with ledger). I'd suggest a solution: Host the documentation on >> wiki, which would allow community to build and keep the documentation up to >> date. Issues like these for e.g., could be easily marked by the user as >> "not working", and then updated by someone in the know-how with the right >> instructions. That collaborative effort on documentation is the only way to >> keep high quality and easy to understand documentation. >> >> >> We don't need a wiki (even though we do already have one), we have >> something much better. Git. >> > > *giggles* > > > You can submit a pull request on GitHub here: >> >> https://github.com/ledger/ledger/blob/next/doc/ledger3.texi#L7734 >> >> You can track this as a problem by opening an issue there as well. >> > This way everyone keeps everything in one place. >> > > You really don't get collaboration. For tech nerds who are already heavily > involved in submitting changes to a project, that's a logistically superior > solution, in theory. The problem is that it leaves out most potential > contributors to documentation fixes or even just pointing out a sentence or > paragraph they might not understand. For either non-tech users, or users > who have never submitted changes to the project (or filed a pull request on > github for that matter, keep in mind most users' knowledge of git extends > to about two commands: git clone and git pull), that's just not going to > happen. I'd go even further: even if one's able to make the pull request, > the amount of trouble to go through is a threshold that most people don't > bother crossing. I certainly would have better things to do with my time > for a one-liner fix. > > Let me spell it out: > > The easier and quicker non-technical people are able to contribute to > documentation, the more they will. > > A system that would let a user highlight, then click, then type, then be > done with it would be ideal (e.g. Google Docs). A wiki is a slightly > inferior alternative - users have to at least learn some syntax and wade > through some of the source document - b
Re: Monthly average expenses for budgeting
Thanks! That definitely helps. I think the documentation needs updating (documentation being one of my main gripes with ledger). I'd suggest a solution: Host the documentation on wiki, which would allow community to build and keep the documentation up to date. Issues like these for e.g., could be easily marked by the user as "not working", and then updated by someone in the know-how with the right instructions. That collaborative effort on documentation is the only way to keep high quality and easy to understand documentation. For starters, the wikia service could be used (to avoid the pains of setting up our own): http://www.wikia.com On Sat, Dec 17, 2016 at 10:07 PM, Brian (bex) Exelbierd <b...@pobox.com> wrote: > > > On Dec 17, 2016, at 6:16 AM, Manish R Jain <manishrj...@gmail.com> > wrote: > > > > I'm trying to build a budget, following section 9 in the manual. > > http://www.ledger-cli.org/3.0/doc/ledger3.html#Budgeting-and-Forecasting > > > > This command is mentioned in the doc to help determine the average > spending per expenses category. But, when I use it, the numbers are out of > whack. They're way too low. > > > > $ ledger -p "this year" --monthly --average balance ^expenses -f > journal.ldg > > > > I've tried other variations like using reg, or setting -b flag instead > of -p. But, doesn't seem to work. > > > > Any ideas, what's going wrong? > > I was literally doing this yesterday as well. I had the same problem. I > "solved" it by doing the math manually. > > $ ledger -p "this year" balance ^expenses -f journal.ldg --amount "amount > / 11.5" > > As I understand this redefines the amount displayed to be the original > amount / 11.5. I chose 11.5 because we are approximately that far through > the year. > > Let me know if that gives you logical values. My transactions are in about > 12 currencies so I'm having trouble verifying them logically. > > This is also exposing a need for me to think about journal organization as > some of these values are "polluted" with data that shouldn't be counted. I > did conversion of data only back to 2016-01-01. The pollution is caused by > my having categorized things like my 2015 tax payment as > Expense:Tax:CZ:Income:2015. Not ideal in retrospect, I think. Still > thinking it through. > > Regards, > > bex > > > -- > > --- > 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] into-ledger: Efficient tool to import transactions into ledger
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 <bren.sm...@gmail.com> 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [ANN] into-ledger: Efficient tool to import transactions into ledger
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. On Thu, Dec 8, 2016 at 9:18 AM, Bren Smith <bren.sm...@gmail.com> wrote: > Hi Manish, > > No worry about the delay. Now, it’s me who should apologize for not trying > your suggestion out sooner! > > I was able to get a bit further, but I seem to have run into another > problem. When I run the application, I get the following assert error. I’m > including some dumps from the *.yaml files in ~/.into-ledger/ directory as > well as a sample line from the CSV file I’m attempting to parse. Let me > know if you see any obvious errors on my part. > > thanks, > > Bren > > > (~/.into-ledger):> into-ledger -a wells-primary -csv > Primary-Checking-0405.2016-11-08-2016-11-27.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:0 Output:/Users/bren/Documents/ > Personal/Financial/CLA/Ledger/wells-primary.out} > 2016/12/07 14:08:47 Should be true, but is false > main.assert > /Users/bren/Documents/Personal/Go/src/github.com/ > manishrjain/into-ledger/main.go:88 > main.(*parser).parseAccounts > /Users/bren/Documents/Personal/Go/src/github.com/ > manishrjain/into-ledger/main.go:153 > main.main > /Users/bren/Documents/Personal/Go/src/github.com/ > manishrjain/into-ledger/main.go:730 > runtime.main > /usr/local/go/src/runtime/proc.go:188 > runtime.goexit > /usr/local/go/src/runtime/asm_amd64.s:1998 > > > Here’s the contents of my config.yaml: > > 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 > > Here’s the contents of my shortcuts.yaml: > > keys: > - short: b > mapto: .back > label: default > - short: q > mapto: .quit > label: default > - short: a > mapto: .show all > label: default > - short: s > mapto: .skip > label: default > > and here’s a representative line from the CSV file I’m pulling from: > > "11/28/2016","-11.99","*","","PURCHASE AUTHORIZED ON 11/27 AMAZON > MKTPLACE PM AMZN.COM/BILL WA S38994578103554031 CARD 8956” > > On Friday, December 2, 2016 at 4:04:48 PM UTC-8, Manish Rai Jain wrote: > >> Hi Bren, >> >> Sorry for the delay. The config file should be located inside >> "~/.into-ledger", with the name "config.yaml". You can see the relevant >> code here: >> https://github.com/manishrjain/into-ledger/blob/master/main.go#L655 >> >> I'll add this part to the README, so it's clear. Also, feel free to file >> any documentation issues as bugs. I like to treat documentation as code, >> with the same level of importance. >> >> >> -- >> Thanks! >> >> Cheers, >> Manish >> >> Founder/CEO, Dgraph Labs >> +61-487138931 <+61%20487%20138%20931> >> https://calendly.com/mrjn >> >> On Tue, Nov 29, 2016 at 08:56:17PM -0800, Bren Smith wrote: >> > Hi Manish, >> > >> > Quick question. Where should one be putting their .into-ledger *config* >> > file? It appears that running the application creates a *directory* >> called >> > ".into-ledger" in my $HOME and then places the shortcuts.yaml file in >> that >> > directory (e.g. /Users/bren/.into-ledger/shortcuts.yaml). So it >> appears >> > that I can't have a directory and a config file of the same name. >> Perhaps >> > I'm just missing something terribly obvious. >> > >> > many thanks in advance, >> > >> > Bren >> > >> > -- >> > >> > --- >> > You received this message because you are subscribed to the Google >> Groups "Ledger" group. >> > To unsubscribe from this group and stop re
Re: [ANN] into-ledger: Efficient tool to import transactions into ledger
Hi Bren, Sorry for the delay. The config file should be located inside "~/.into-ledger", with the name "config.yaml". You can see the relevant code here: https://github.com/manishrjain/into-ledger/blob/master/main.go#L655 I'll add this part to the README, so it's clear. Also, feel free to file any documentation issues as bugs. I like to treat documentation as code, with the same level of importance. -- Thanks! Cheers, Manish Founder/CEO, Dgraph Labs +61-487138931 https://calendly.com/mrjn On Tue, Nov 29, 2016 at 08:56:17PM -0800, Bren Smith wrote: > Hi Manish, > > Quick question. Where should one be putting their .into-ledger *config* > file? It appears that running the application creates a *directory* called > ".into-ledger" in my $HOME and then places the shortcuts.yaml file in that > directory (e.g. /Users/bren/.into-ledger/shortcuts.yaml). So it appears > that I can't have a directory and a config file of the same name. Perhaps > I'm just missing something terribly obvious. > > many thanks in advance, > > Bren > > -- > > --- > 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 ledger-cli+unsubscr...@googlegroups.com. > 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[ANN] into-ledger: Efficient tool to import transactions into ledger
Hi ledger users, I have over a hundred transactions per month and a lot of categories; I was unhappy with the existing transaction import tools. So, I wrote "into-ledger" to make import efficient. Features: - *Accurate*: Uses a much more accurate tf-idf expense classifier than used by cantino/reckon. - *Includes and Aliases*: Correctly parses your existing journal file, handling all includes and account aliases. - *Keyboard Shortcuts*: Assigns dynamic keyboard shortcuts, so classifying transactions is just a keystroke away. - *Auto-save*: Uses temporary storage (boltdb) to persist transactions that you have categorized or acknowledged to be correctly categorized, so you can quit whenever you want, without the risk of losing the work done so far. - *Deduplication*: Deduplicates incoming transactions from CSV against the transactions already present in ledger journal. This allows an easy resume from a broken workflow. - *Nice UI*: Colors and formatting, because it's not just about getting things done. It's also about making them look nice! Github: https://github.com/manishrjain/into-ledger You can install it via Go using: go get -v -u github.com/manishrjain/into-ledger I encourage you to try it out. And if you do, send your comments and feedback my way. Cheers, Manish -- --- 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 ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Ledger Presentation
On Thu, Jul 2, 2009 at 8:52 PM, Russell Adams wrote: Manish, Thats really unusual. I haven't had any other reports of the site not working. Login to irc sometime and I can help. Looks like your IRC threat did something. ;-) I checked again before logging in to IRC and it worked! The presentation looks great and covers lots of ground. Looking forward to the video. Thanks! -- Manish
Ledger build failure on Debian Sid
Hello List! With latest git checkout (b182143 Mon Feb 2 00:28:12 2009) on Debian Unstable, compilation fails complaining of missing irrXML.h and CXMLReaderImpl.h. acprep and configure finished without any errors. , | master% make | make all-am | make[1]: Entering directory `/data/desktop/ledger.git' | /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src | -g -O2 -MT libledger_util_la-utils.lo -MD -MP -MF .deps/libledger_util_la-utils.Tpo -c -o libledger_util_la-utils.lo `test -f ' | src/utils.cc' || echo './'`src/utils.cc | mkdir .libs | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_util_la-utils.lo -MD -MP | -MF .deps/libledger_util_la-utils.Tpo -c src/utils.cc -fPIC -DPIC -o .libs/libledger_util_la-utils.o | In file included from src/utils.h:52, | from src/utils.cc:32: | ./src/system.hh:141:35: error: irrXML.h: No such file or directory | ./src/system.hh:142:28: error: CXMLReaderImpl.h: No such file or directory | make[1]: *** [libledger_util_la-utils.lo] Error 1 | make[1]: Leaving directory `/data/desktop/ledger.git' | make: *** [all] Error 2 ` Suggestions please. -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 1:26 AM, John Wiegley wrote: On Feb 2, 2009, at 3:43 PM, Manish wrote: | master% git submodule update | fatal: The remote end hung up unexpectedly | Unable to checkout 'fccfbd741a0fd974945bb259854768cc70258f07' in submodule path 'lib/cppunit' Youch, I'll figure this out today. | src/amount.cc: In function �void ledger::unnamed::stream_out_mpq(std::ostream, __mpq_struct*, uint_least16_t, const boost::op | tionalledger::commodity_t)�: | src/amount.cc:572: error: �mpfr_asprintf� was not declared in this scope I forgot to mention to the list: MPFR 2.4.0 is now a required dependency. I'm using MPFR, which is a library based on GMP, for doing reliable, multi-precision conversion of rationals to approximated floating-point. Unfortunately Debian unstable is still at 2.3.2. :-/ , | master% sudo apt-cache policy libmpfr1ldbl libmpfr-dev | libmpfr1ldbl: | Installed: 2.3.2.dfsg.1-1 | Candidate: 2.3.2.dfsg.1-1 | Version table: | *** 2.3.2.dfsg.1-1 0 | 500 http://the.earth.li unstable/main Packages | 100 /var/lib/dpkg/status | 2.3.1.dfsg.1-2 0 | 500 ftp://ftp.free.fr lenny/main Packages | libmpfr-dev: | Installed: 2.3.2.dfsg.1-1 | Candidate: 2.3.2.dfsg.1-1 | Version table: | *** 2.3.2.dfsg.1-1 0 | 500 http://the.earth.li unstable/main Packages | 100 /var/lib/dpkg/status | 2.3.1.dfsg.1-2 0 | 500 ftp://ftp.free.fr lenny/main Packages ` Thanks, -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 1:56 AM, John Wiegley wrote: On Feb 2, 2009, at 4:06 PM, Manish wrote: Unfortunately Debian unstable is still at 2.3.2. :-/ Yes, a friend mentioned that to me. Sadly, the most important function for me in MPFR only first appeared in 2.4.0. :( Maybe you could prompt the Debian maintainer for that package? Just checked 2.4.0 is in experimental. So hopefully it will get to unstable sometime. -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 2:07 AM, John Wiegley wrote: On Feb 2, 2009, at 4:31 PM, Manish wrote: | src/op.h:335: error: multiple parameters named �op� This is fixed and pushed. Thanks. I am trying a fresh clone also. Looks like my earlier repo is not completely healthy (submodules failing etc.) What version of gcc are you using? Mine didn't catch this. , | master% gcc --version | gcc (Debian 4.3.2-1) 4.3.2 | Copyright (C) 2008 Free Software Foundation, Inc. | This is free software; see the source for copying conditions. There is NO | warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ` -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 2:14 AM, Manish wrote: On Tue, Feb 3, 2009 at 2:07 AM, John Wiegley wrote: On Feb 2, 2009, at 4:31 PM, Manish wrote: | src/op.h:335: error: multiple parameters named �op� This is fixed and pushed. Thanks. I am trying a fresh clone also. Looks like my earlier repo is not completely healthy (submodules failing etc.) Fresh clone and acprep worked flawlessly. Apologies for noise earlier. And sorry for another silly question: earlier passing --libdir to configure seemed to work but I am getting following error now. , | configure: error: Could not find mpfr library 2.4.0 or higher (set CPPFLAGS and LDFLAGS?) ` I have tried to pass /usr/local/lib to configure in many ways but nothing seems to work. Headers are really present in /usr/local/include and libraries in /usr/local/lib , | master% find /usr/local -name *mpfr* | /usr/local/include/mpfr.h | /usr/local/include/mpf2mpfr.h | /usr/local/share/info/mpfr.info | /usr/local/lib/libmpfr.la | /usr/local/lib/libmpfr.a | /usr/local/lib/libmpfr.so.1.2.0 | /usr/local/lib/libmpfr.so | /usr/local/lib/libmpfr.so.1 ` Can someone suggest a way please? Thanks -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 2:27 AM, Manish wrote: On Tue, Feb 3, 2009 at 2:14 AM, Manish wrote: On Tue, Feb 3, 2009 at 2:07 AM, John Wiegley wrote: On Feb 2, 2009, at 4:31 PM, Manish wrote: | src/op.h:335: error: multiple parameters named �op� This is fixed and pushed. Thanks. I am trying a fresh clone also. Looks like my earlier repo is not completely healthy (submodules failing etc.) Fresh clone and acprep worked flawlessly. Apologies for noise earlier. And sorry for another silly question: earlier passing --libdir to configure seemed to work but I am getting following error now. , | configure: error: Could not find mpfr library 2.4.0 or higher (set CPPFLAGS and LDFLAGS?) ` For the sake of record, I was told to use this on irc and it works great. --8---cut here---start-8--- C_INCLUDE_PATH=$C_INCLUDE_PATH:/usr/local/include LIBRARY_PATH=$LIBRARY_PATH:/usr/local/lib export C_INCLUDE_PATH LIBRARY_PATH ./configure --8---cut here---end---8--- Now it fails with this. , | CXX libledger_util_la-utils.lo | CXX libledger_util_la-error.lo | CXX libledger_util_la-times.lo | CXX libledger_util_la-mask.lo | CXX libledger_util_la-stream.lo | CXX libledger_util_la-binary.lo | CXX libledger_util_la-sha1.lo | LD libledger_util.la | CXX libledger_math_la-amount.lo | CXX libledger_math_la-commodity.lo | CXX libledger_math_la-balance.lo | CXX libledger_math_la-balpair.lo | CXX libledger_math_la-value.lo | LD libledger_math.la | CXX libledger_expr_la-token.lo | CXX libledger_expr_la-parser.lo | CXX libledger_expr_la-op.lo | CXX libledger_expr_la-expr.lo | CXX libledger_expr_la-scope.lo | CXX libledger_expr_la-predicate.lo | CXX libledger_expr_la-format.lo | CXX libledger_expr_la-option.lo | In file included from src/option.cc:32: | src/option.h:54: error: multiple parameters named �name� | make[1]: *** [libledger_expr_la-option.lo] Error 1 | make[1]: Leaving directory `/data/desktop/johnw/ledger' | make: *** [all] Error 2 ` Thanks -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 3:26 AM, John Wiegley wrote: On Feb 2, 2009, at 5:09 PM, Manish wrote: | src/option.h:54: error: multiple parameters named �name� Thank you. Now there's a new kind of error (last 60 lines quoted below.) , | (cd .libs rm -f libledger_report.la ln -s ../libledger_report.la libledger_report.la) | /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src | -g -O2 -MT libledger_extra_la-derive.lo -MD -MP -MF .deps/libledger_extra_la-derive.Tpo -c -o libledger_extra_la-derive.lo `tes | t -f 'src/derive.cc' || echo './'`src/derive.cc | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-derive.lo -MD -M | P -MF .deps/libledger_extra_la-derive.Tpo -c src/derive.cc -fPIC -DPIC -o .libs/libledger_extra_la-derive.o | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-derive.lo -MD -M | P -MF .deps/libledger_extra_la-derive.Tpo -c src/derive.cc -o libledger_extra_la-derive.o /dev/null 21 | mv -f .deps/libledger_extra_la-derive.Tpo .deps/libledger_extra_la-derive.Plo | /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src | -g -O2 -MT libledger_extra_la-reconcile.lo -MD -MP -MF .deps/libledger_extra_la-reconcile.Tpo -c -o libledger_extra_la-reconcil | e.lo `test -f 'src/reconcile.cc' || echo './'`src/reconcile.cc | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-reconcile.lo -MD | -MP -MF .deps/libledger_extra_la-reconcile.Tpo -c src/reconcile.cc -fPIC -DPIC -o .libs/libledger_extra_la-reconcile.o | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-reconcile.lo -MD | -MP -MF .deps/libledger_extra_la-reconcile.Tpo -c src/reconcile.cc -o libledger_extra_la-reconcile.o /dev/null 21 | mv -f .deps/libledger_extra_la-reconcile.Tpo .deps/libledger_extra_la-reconcile.Plo | /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src | -g -O2 -MT libledger_extra_la-quotes.lo -MD -MP -MF .deps/libledger_extra_la-quotes.Tpo -c -o libledger_extra_la-quotes.lo `tes | t -f 'src/quotes.cc' || echo './'`src/quotes.cc | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-quotes.lo -MD -M | P -MF .deps/libledger_extra_la-quotes.Tpo -c src/quotes.cc -fPIC -DPIC -o .libs/libledger_extra_la-quotes.o | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src -g -O2 -MT libledger_extra_la-quotes.lo -MD -M | P -MF .deps/libledger_extra_la-quotes.Tpo -c src/quotes.cc -o libledger_extra_la-quotes.o /dev/null 21 | mv -f .deps/libledger_extra_la-quotes.Tpo .deps/libledger_extra_la-quotes.Plo | /bin/sh ./libtool --tag=CXX --mode=link g++ -g -O2 -release 3.0.0 -o libledger_extra.la -rpath /usr/local/lib libledger_extr | a_la-derive.lo libledger_extra_la-reconcile.lo libledger_extra_la-quotes.lo -lboost_filesystem -lboost_system -lboost_date_time | -lboost_regex -lmpfr -lgmp | g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.3.2/crtbeginS.o .l | ibs/libledger_extra_la-derive.o .libs/libledger_extra_la-reconcile.o .libs/libledger_extra_la-quotes.o -lboost_filesystem -lboo | st_system -lboost_date_time -lboost_regex /usr/local/lib/libmpfr.so /usr/lib/libgmp.so -L/usr/local/lib/../lib -L/usr/lib/gcc/i4 | 86-linux-gnu/4.3.2 -L/usr/lib/gcc/i486-linux-gnu/4.3.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L. -L/usr/local/lib -L/u | sr/lib/gcc/i486-linux-gnu/4.3.2/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i486-linux-gnu/4.3.2/crtendS.o /usr/lib/gcc/i486- | linux-gnu/4.3.2/../../../../lib/crtn.o -Wl,-soname -Wl,libledger_extra-3.0.0.so -o .libs/libledger_extra-3.0.0.so | (cd .libs rm -f libledger_extra.so ln -s libledger_extra-3.0.0.so libledger_extra.so) | ar cru .libs/libledger_extra.a libledger_extra_la-derive.o libledger_extra_la-reconcile.o libledger_extra_la-quotes.o | ranlib .libs/libledger_extra.a | creating libledger_extra.la | (cd .libs rm -f libledger_extra.la ln -s ../libledger_extra.la libledger_extra.la) | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src-g -O2 -MT ledger-main.o -MD -MP -MF .deps/ | ledger-main.Tpo -c -o ledger-main.o `test -f 'src/main.cc' || echo './'`src/main.cc | mv -f .deps/ledger-main.Tpo .deps/ledger-main.Po | g++ -DHAVE_CONFIG_H -I. -I./src -I./lib -I./lib/utfcpp/source -I./lib/irrxml/src-g -O2 -MT ledger-work.o -MD -MP -MF .deps/ | ledger-work.Tpo -c -o ledger-work.o `test -f 'src/work.cc' || echo './'`src/work.cc | mv -f .deps/ledger-work.Tpo .deps/ledger-work.Po | /bin/sh ./libtool --tag=CXX --mode=link g++ -g -O2
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 7:11 AM, John Wiegley wrote: On Feb 2, 2009, at 6:17 PM, Manish wrote: Would you prefer to take this off-list or would you like me to stop testing so you can get it to work with new gcc? I want to get it to compile once so I can test my buildbot. :) I'm going to reverse the link order of the new sub-libraries. Git pull, acprep and a make later: ,[ last 45 lines from compile log ] | LD libledger_math.la | CXX libledger_util_la-utils.lo | CXX libledger_util_la-error.lo | CXX libledger_util_la-times.lo | CXX libledger_util_la-mask.lo | CXX libledger_util_la-stream.lo | CXX libledger_util_la-binary.lo | LD libledger_util.la | CXX libledger_python_la-py_utils.lo | CXX libledger_python_la-py_times.lo | python/py_times.cc: In static member function �static PyObject* ledger::date_to_python::convert(const ledger::date)�: | python/py_times.cc:49: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:49: warning: deprecated conversion from string constant to �char*� | python/py_times.cc: In static member function �static void* ledger::date_from_python::convertible(PyObject*)�: | python/py_times.cc:58: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:58: warning: deprecated conversion from string constant to �char*� | python/py_times.cc: In static member function �static void ledger::date_from_python::construct(PyObject*, boost::python::converter::rvalue_from_py | thon_stage1_data*)�: | python/py_times.cc:65: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:65: warning: deprecated conversion from string constant to �char*� | python/py_times.cc: In static member function �static PyObject* ledger::datetime_to_python::convert(const ledger::datetime_t)�: | python/py_times.cc:82: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:82: warning: deprecated conversion from string constant to �char*� | python/py_times.cc: In static member function �static void* ledger::datetime_from_python::convertible(PyObject*)�: | python/py_times.cc:95: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:95: warning: deprecated conversion from string constant to �char*� | python/py_times.cc: In static member function �static void ledger::datetime_from_python::construct(PyObject*, boost::python::converter::rvalue_fro | m_python_stage1_data*)�: | python/py_times.cc:102: warning: deprecated conversion from string constant to �char*� | python/py_times.cc:102: warning: deprecated conversion from string constant to �char*� | CXX libledger_python_la-py_amount.lo | CXX libledger_python_la-py_commodity.lo | CXX libledger_python_la-py_value.lo | CXX libledger_python_la-pyinterp.lo | LD libledger_python.la | CXX ledger-main.o | CXX ledger-work.o | LD ledger | ./.libs/libledger_report.a(libledger_report_la-chain.o): In function `ledger::reconcile_xacts::reconcile_xacts(boost::shared_ptrledger::item_hand | lerledger::xact_t , ledger::value_t const, boost::gregorian::date const)': | chain.cc:(.text._ZN6ledger15reconcile_xactsC1EN5boost10shared_ptrINS_12item_handlerINS_6xact_tERKNS_7value_tERKNS1_9gregorian4dateE[ledger::re | concile_xacts::reconcile_xacts(boost::shared_ptrledger::item_handlerledger::xact_t , ledger::value_t const, boost::gregorian::date const)]+0 | x3c): undefined reference to `vtable for ledger::reconcile_xacts' | collect2: ld returned 1 exit status | make[1]: *** [ledger] Error 1 | make[1]: Leaving directory `/data/desktop/johnw/ledger' | make: *** [all] Error 2 | make 171.91s user 10.89s system 98% cpu 3:05.10 total ` Thanks -- Manish
Re: Ledger build failure on Debian Sid
On Tue, Feb 3, 2009 at 11:37 AM, John Wiegley wrote: On Feb 3, 2009, at 1:53 AM, Manish wrote: Git pull, acprep and make all completed okay. Fullcheck now failed with an mpfr related error. Is it because `sh' being invoked at the end does not know where mpfr is installed? How can I set the location of mpfr (/usr/local) available system-wide? I created a file `/etc/ld.so.conf.d/libmpfr.conf' with a single line `/usr/local/bin' and ran ldconfig to make the mpfr libs available system-wide (I hope) leading to a successful fullcheck. :) But read on... ,[ make fullcheck ] | master% time make fullcheck | CXX util_tests-UnitTests.o | CXX util_tests-t_times.o | CXX libledger_util_la-utils.lo | CXX libledger_util_la-error.lo | CXX libledger_util_la-times.lo | CXX libledger_util_la-mask.lo | CXX libledger_util_la-stream.lo | CXX libledger_util_la-binary.lo | LD libledger_util.la | LD util_tests | CXX math_tests-UnitTests.o | CXX math_tests-t_commodity.o | CXX math_tests-t_amount.o | CXX math_tests-t_balance.o | CXX libledger_math_la-amount.lo | CXX libledger_math_la-commodity.lo | CXX libledger_math_la-balance.lo | CXX libledger_math_la-balpair.lo | CXX libledger_math_la-value.lo | LD libledger_math.la | LD math_tests | CXX expr_tests-UnitTests.o | CXX expr_tests-t_expr.o | CXX libledger_expr_la-token.lo | CXX libledger_expr_la-parser.lo | CXX libledger_expr_la-op.lo | CXX libledger_expr_la-expr.lo | CXX libledger_expr_la-scope.lo | CXX libledger_expr_la-predicate.lo | CXX libledger_expr_la-format.lo | CXX libledger_expr_la-option.lo | LD libledger_expr.la | LD expr_tests | CXX data_tests-UnitTests.o | CXX libledger_data_la-item.lo | CXX libledger_data_la-xact.lo | CXX libledger_data_la-entry.lo | CXX libledger_data_la-account.lo | CXX libledger_data_la-journal.lo | CXX libledger_data_la-timelog.lo | CXX libledger_data_la-iterators.lo | CXX libledger_data_la-compare.lo | LD libledger_data.la | LD data_tests | CXX parse_tests-UnitTests.o | CXX libledger_parse_la-textual.lo | CXX libledger_parse_la-cache.lo | CXX libledger_parse_la-xml.lo | CXX libledger_parse_la-csv.lo | CXX libledger_parse_la-emacs.lo | CXX libledger_parse_la-qif.lo | CXX libledger_parse_la-gnucash.lo | LD libledger_parse.la | LD parse_tests | CXX report_tests-UnitTests.o | CXX libledger_report_la-session.lo | CXX libledger_report_la-report.lo | CXX libledger_report_la-filters.lo | CXX libledger_report_la-chain.lo | CXX libledger_report_la-precmd.lo | CXX libledger_report_la-output.lo | CXX libledger_report_la-help.lo | CXX libledger_report_la-derive.lo | CXX libledger_report_la-reconcile.lo | CXX libledger_report_la-quotes.lo | LD libledger_report.la | LD report_tests | sh ./tools/fullcheck ./util_tests --verify | .. | OK (2) | sh ./tools/fullcheck ./math_tests --verify | | OK (44) | sh ./tools/fullcheck ./expr_tests --verify | . | OK (1) | sh ./tools/fullcheck ./data_tests --verify | | OK (0) | sh ./tools/fullcheck ./parse_tests --verify | | OK (0) | sh ./tools/fullcheck ./report_tests --verify | | OK (0) | make fullcheck 158.17s user 11.21s system 99% cpu 2:50.35 total ` A plain acprep has been completing successfully but this one issued as part of release-distcheck failed ./acprep --release --boost xgcc40 --build -j3 distcheck output ,[ make release-distcheck ] | ... rsync and git clean output snipped ... | checking where .elc files should go... ${datarootdir}/emacs/site-lisp | checking if pipes can be used... true | checking if libgmp is available... true | checking if libmpfr is available... true | checking if boost_regex is available... false | configure: error: Could not find boost_regex library (set CPPFLAGS and LDFLAGS?) | See `config.log' for more details. | + make ARCHFLAGS= 'CPPFLAGS=-isystem /usr/local/stow/cppunit/include -isystem /usr/local/include -isystem /opt/local/include -is | ystem /opt/local/include/libofx -isystem /usr/local/include/boost-1_37 -isystem /usr/include/python2.5' 'LDFLAGS=-L/usr/local/st | ow/cppunit/lib -L/usr/local/lib -L/usr/lib -L/opt/local/lib -L/usr/lib/python2.5/config' 'CXXFLAGS=-pthread -pipe' 'DISTCHECK_C | ONFIGURE_FLAGS=--disable-shared --disable-dependency-tracking --with-boost-suffix=-xgcc40' -j3 distcheck | make[1]: Entering directory `/tmp/ledger' | make[1]: *** No rule to make target `distcheck'. Stop. | make[1]: Leaving directory `/tmp/ledger' | make: *** [release-distcheck] Error 2 | make release-distcheck 14.12s user 1.76s system 72% cpu 21.931 total ` Any ideas? Actually, just never mind about fullcheck. Does 'make check' work? Here are the results for `make check': ,[ make check ] | master% make check | make check-am | make[1