All known bugs and features for 3.0 implemented

[John Wiegley]

Now begins the documenting and further testing stage for 3.0. If you
have any bugs to submit, please do so now! so that I can get
everything into 3.0 that should be.

Thanks, John

[Juergen Daubert]

Got the following error:

./ledger -f doc/sample.dat
Ledger master-0-gcb3c7c3, the command-line accounting tool

Copyright (c) 2003-2009, John Wiegley. All rights reserved.

This program is made available under the terms of the BSD Public
License.
See LICENSE file included with the distribution for details and
disclaimer.
Error: basic_string::resize

System-information:
linux, gcc 4.4.2, boost 1.40.0

regards
Juergen

[ed]

What is the approved way to get the latest version? ./acprep pull give
me

checking build system type... Invalid configuration `pull': machine
`pull' not recognized

I've been using git pull but don't know if this works well with acprep

[Simon Michael]

A big milestone - congrats John!

[Juergen Daubert]

On Sat, Oct 31, 2009 at 11:23:59AM +0100, Juergen Daubert wrote:
>
> On Sat, Oct 31, 2009 at 04:54:38AM -0400, John Wiegley wrote:
> >
> > Now begins the documenting and further testing stage for 3.0. If
> > you have any bugs to submit, please do so now! so that I can get
> > everything into 3.0 that should be.
> >
> > Thanks, John
>
> Got the following error:
>
> ./ledger -f doc/sample.dat
> Ledger master-0-gcb3c7c3, the command-line accounting tool
>
> Copyright (c) 2003-2009, John Wiegley. All rights reserved.
>
> This program is made available under the terms of the BSD Public
> License.
> See LICENSE file included with the distribution for details and
> disclaimer.
> Error: basic_string::resize

Found the reason for this error, I have a --cache entry in my
.ledgerrc which points to a file produced with ledger 2.6.2.
After removing that file everything works.

regards
Juergen

[Vinod Kurup]

Excellent work!

I'm not sure if this is a bug or a "lack of a feature", but I would
love to see the period flag (-p) accept "YYYY/MM". The sample file
only has entries from 'May 2004', but using -p to request entries from
'April 2004' still shows the ones from May.

vinod@ike:~/dev/ledger$ ./ledger -f ./doc/sample.dat -p 2004/04 bal
expenses
$90.000 Expenses
$20.000 Books
$40.000 Cards
$30.000 Docs
--------------------
$90.000

[John Wiegley]

On Oct 31, 2009, at 6:30 AM, ed wrote:

> What is the approved way to get the latest version? ./acprep pull give
> me
>
> checking build system type... Invalid configuration `pull': machine
> `pull' not recognized
>
> I've been using git pull but don't know if this works well with acprep

The best way to update to the latest version is:

./acprep update

This should do everything you need.

John

[John Wiegley]

On Oct 31, 2009, at 4:10 PM, Vinod Kurup wrote:

> I'm not sure if this is a bug or a "lack of a feature", but I would
> love to see the period flag (-p) accept "YYYY/MM". The sample file
> only has entries from 'May 2004', but using -p to request entries from
> 'April 2004' still shows the ones from May.

YYYY/MM format should certainly be accepted by -p now. This is a bug
and I'll add it to the list. Thanks!

John

[Juergen Daubert]

Would be nice to have more meaningful error message like
'corrupted cache file' or maybe a warning that the file is
for 2.6 and cannot be used by 3.0 here.

thanks
Juergen

[John Wiegley]

On Nov 1, 2009, at 4:21 AM, Juergen Daubert wrote:

> Would be nice to have more meaningful error message like
> 'corrupted cache file' or maybe a warning that the file is
> for 2.6 and cannot be used by 3.0 here.

Ok, this has been fixed. I'm afraid the caching feature needs a lot
more testing.

John

[Juergen Daubert]

On Sat, Oct 31, 2009 at 04:54:38AM -0400, John Wiegley wrote:
>

Many thanks for your work, seems I've found some small issues:

- The !include statememt no longer accepts simple filenames, but
needs the full path to the file.
- No error message is thrown if ledger cannot find the file defined
in a !include statement, ledger runs but the output is empty.
- Looks like ledger always assums UTF-8 encoding, or is there a
way to force ledger to use other encodings?

Thanks
Juergen

[John Wiegley]

On Nov 1, 2009, at 4:59 AM, Juergen Daubert wrote:

> - The !include statememt no longer accepts simple filenames, but
> needs the full path to the file.
> - No error message is thrown if ledger cannot find the file defined
> in a !include statement, ledger runs but the output is empty.

I'll get both of these fixed shortly.

> - Looks like ledger always assums UTF-8 encoding, or is there a
> way to force ledger to use other encodings?

UTF-8 is the only encoding Ledger supports.

John