In other projects, those have come from the branch protections settings for
me.
On Sun, Sep 5, 2021, 11:56 Rahix wrote:
> On Sun, 2021-09-05 at 10:08 +0800, Martin Michlmayr wrote:
> > * Rahix [2021-09-04 09:35]:
> > > Now that GHA seems to be up and running, can you drop Travis from the
> > >
In ledger negatives go between the commodity and the amount. So instead of
-$100 you should right $-100.
It looks to me like you have 2,300 of the commodity "$" and 2,500 of the
commodity "-$", and ledger is treating them as separate, unrelated
commodities.
If you change your negatives to the
For this purpose, I use balance with the --group-by option, like this:
ledger balance Expense:Entertainment --depth 2 --group-by
'format_date(date, "%Y-%m")'
That would produce a series of balances grouped by month. You could also
use "%Y" as the format string to get grouped by year, or many
To deal with the default account problem, I make the transaction explicitly
0. To deal with it not being a real transaction, I make it a virtual one.
Together it looks like this
2020-04-06 * Reconcile
[Assets:Checking] $0 = $123.00
[Assets:Savings] $0 = $456.00
-Mythmon
On Mon, Apr
Hey psion,
Every well behaving command line app should only use color at interactive
colors that can render them. If you are seeing raw formatting codes, I
think we can all agree there is a problem somewhere. It would be great if
you could give some specific examples of times this goes wrong.
In
You'll need to pass --generated to the command to see the automatically
generated parts of transactions.
On Mon, Mar 26, 2018, 08:41 Ella Lobatina wrote:
> Yes I did :)
> Here is an example:
> (Ledger 3.0.3-20140608 on Fedora 18)
>
> This block in one file (journal):
>
Ledger cares a lot about the order of transactions, and doesn't care much
for dates in many ways.
HLedger and Beancount both ignore the order of transactions, and only care
about dates.
On Sat, Jan 6, 2018 at 4:45 AM Eduardo Elias wrote:
> Hi,
>
> I was having problems
I would generally agree with the "if it isn't broken, don't fix it" ideal,
but in Ledger's case, there is almost 2 years and 172 commits worth of
development, according to Github [0], since the release of 3.1.1. There
should be at least a plan for when that effort is going to be deemed
suitable
Your problem is that there is a space character on the "empty" line between
the two transactions. Since the line is not totally empty, it throws off
ledger's parser. Deleting the space character makes the file work for me.
On Wed, Dec 6, 2017 at 11:32 AM Andrew Thorp wrote:
dust off my very dusty C++ and try to fix it, or
> try one of the ledger spinoffs like beancount... maybe there are
> beancount / hledger people here who can comment re whether those systems
> have ways to tackle the problem from the thread linked above?
>
> On Thu, 19 Oct 2017,
me both a history of balances,
and also a sort of test suite. If I change the organization of my files,
change rules, or do other refactoring, these assertions give me confidence
that I didn't break anything.
-Michael Cooper
On Thu, Oct 19, 2017 at 3:43 PM John Lee <j...@pobox.com> wrote:
, 2017 at 11:32 PM John Wiegley <jo...@newartisans.com> wrote:
> >>>>> "MC" == Michael Cooper <myth...@gmail.com> writes:
>
> MC> for transaction in transactions_from(some_file):
> MC> transaction.check_assertions()
> MC> boo
book.add(transaction)
```
Disclaimer: I haven't read any of the ledger source code, and I don't know
C++. This is just based on a guess of how I might write a ledger-like-tool.
On Sun, Feb 19, 2017 at 9:48 AM John Wiegley <jo...@newartisans.com> wrote:
> >>>>> "
13 matches
Mail list logo