> "JR" == Jim Robinson writes:
JR> The page https://github.com/ledger/ledger/wiki/Bug-tracking
JR> points to http://bugs.ledger-cli.org/
Thank you, I'll update this pointer.
John
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubsc
Hi,
The page https://github.com/ledger/ledger/wiki/Bug-tracking
points to http://bugs.ledger-cli.org/
which is not available via DNS. I've logged something under the github
issue tracker
https://github.com/ledger/ledger/issues/1689
I can re-enter it elsewhere if sometime tells me the location
> "JR" == Jim Robinson writes:
JR> Thank you for the reply. This is on 3.1.1-20160111. Do you want me to
JR> file a bug report?
If you would, that would be great, thank you!
John
--
---
You received this message because you are subscribed to the Google Groups
"Ledger" group.
To unsubs
Hi,
Thank you for the reply. This is on 3.1.1-20160111. Do you want me to file
a bug report?
Jim
--
---
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+u
> "JR" == Jim Robinson writes:
JR> this seems odd to me, it's true the entry is for a time in the future but
JR> why should that matter to ledger?
JR> Without changing anything, running the report again at 14:04:00, or after,
JR> works.
Not just seems odd, *is* odd. This is a bug.
John
--
Hi,
I use ledger to track my time working on tickets, and sometimes I end up in
a situation where a rounding up of time values to the next minute causes
ledger to freak out.
As an example, if it was 14:03:45 in the local time and the ledger file
held lines:
i 2018-11-08 12:10:00 PROJ1
o 2018-
