Oh, and here is the output:
$ ledger -f fake_journal --pedantic print
2017/10/01 ff
assets:ff:cash:wallet:Extalticana:S 3000 "Those super crypto coins"
{=BTC3000}
$
On Friday, December 1, 2017 at 12:05:26 AM UTC, Ella Lobatina wrote:
>
> Sorry for the typo, 'pedant' should have been 'pedantic'
>
> On Friday, December 1, 2017 at 12:04:27 AM UTC, Ella Lobatina wrote:
>>
>> Here you are:
>>
>> This block in one file (fake_journal I called it):
>> ===============
>> year 2017
>>
>> account assets:ff:cash:wallet:Extalticana:S
>> alias ffCaE
>> assets:hh:cash:wallet:Agelica Simpson:S
>> alias hhCaA
>>
>> commodity "Those super crypto coins"
>>
>> bucket hhCaA
>>
>> 2017/10/01 ff
>> ffCaE 3000 "Those super crypto coins" {=BTC 3000}
>> ===============
>>
>> then run:
>> $ ledger -f fake_journal --pedant print
>>
>>
>> If this is a quirk of my current edger 3.0.3-20140608 then I'll have to
>> install a newer version, if it wants to run on Fedora 18.
>>
>>
>> By the way, I'm using ledger-cli 'in the field', which means on a
>> smartphone.
>> Formatting a transaction with new lines and whitespaces is then a bit
>> cumbersome because it requires more 'thumb clicks' and uses more 'screen
>> estate' then I'd liked to.
>> So, in order to speed up entering transactions and to save space on the
>> screen, I have now input every transaction in a daily file in which only
>> the first transaction gets the (full) date prefix and every transaction set
>> (date, payee, multiple lines) is entered on one line only (those lines
>> separated by one or more empty lines), after which a little bash script
>> cleans up the mess and re-formats the file into a valid ledger file.
>> In order to not confuse the script, amazingly enough it suffices to start
>> every transaction line (as I call it) with a period immediately preceding
>> the account name (abbreviation) and comments of course start with a
>> semi-colon.
>> The script then takes care of proper translation.
>>
>> A transaction input will then look like this one-liner:
>>
>> 2017/10/01 ff .ffCaE 3000 "Those super crypto coins" {=BTC 3000} ;
>> comment blahblah .apples 0.000000000000000001 BTC ; Another comment I
>> didn't check the value for real .c
>>
>> (c is the balancing account abbreviation)
>>
>> It only requires a bit of care to make sure every 'textual' period is
>> followed by white space.
>> Anyone interested in the script can have it. It's small and built with
>> lots of great help from the ingenious Stack Exchange (TM) community,
>> because I wasn't proficient enough in bash to work it out all on my own.
>>
>>
>> Thanks for looking into this.
>>
>>
>>
>> On Thursday, November 30, 2017 at 7:16:30 PM UTC, John Wiegley wrote:
>>>
>>> >>>>> "EL" == Ella Lobatina <[email protected]> writes:
>>>
>>> LE> Obviously I'm doing it wrong, but how should I go about it in order
>>> to get
>>> LE> those balancing transactions included in my output?
>>>
>>> Can you show me an example of a single transaction (fake) within the
>>> context
>>> of the other settings you have in your Ledger file? I'd like to try it
>>> here.
>>>
>>> LE> Thanks for the nice program, it's the only one that works for me.
>>>
>>> You're welcome! :)
>>>
>>> John
>>>
>>
--
---
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.
