Sorting and narrowing ledger data was a major issue for me. The
closest I got was using reports in Emacs to allow me to hyperlink to
ledger entries in any file.

When we start talking about sorting and queries (narrowing) this is
where the flat file format starts to be an issue vs a kind of
database.

Throw in the integration with version control, and this is a real
pickle. It certainly frustrated me.

I'd love to see how this is implemented, and welcome the discussion of
features.

On Mon, Aug 26, 2013 at 11:33:58AM -0700, Craig Earls wrote:
> OK. I am willing to work on an external script for this ( probably using 
> leder print to do the hard work)
>
>
>
>
>
>     If any is interested in this sort of tool please me know how you 
> personally would lik to handle non-cactus entries. 
>
>
>
>
>
>     There are many options, here are a few I can think of:
>
>
>
>
>
>     1. Comments, virtuals and autos that occurr before the first real xact 
> will be left at the head of the file. 
>
>     2. File level comments are tied to the xact immediately following and 
> will sort as such. There might be other smarter ways to handle this. 
>
>     3. File level commands that occur in the body of the file serve as 
> separators and all xacts that occur after that command will stay after that 
> command regardless of date. Should file level comments be the same?  
>
>
>
>
>
>     Optionally I can make the tool
>
>     Do a check. A simple ledger bal on the new file should be identical. 
>
>
>
>
>
>     Any other ideas?  I would probably do this in python unless there is a 
> more convenient scripting tool (bash is right out. Don't ask!)
>
>
>
>
>
>     Craig
>
>     --
> Craig
>
> On Mon, Aug 26, 2013 at 8:49 AM, Simon Michael <[email protected]> wrote:
>
> > hledger's print throws away top-level comments and directives, like
> > ledger's. I think it's not supposed to - there are data structures to
> > hold those things - but currently it does.
> > Other than patching h/ledger, sorting with the emacs mode (perhaps
> > hidden behind a command-line script) or an awk script sounds like the
> > best option.
> > --
> > ---
> > 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/groups/opt_out.
>
> --
>
> ---
> 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/groups/opt_out.


------------------------------------------------------------------
Russell Adams                            [email protected]

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

-- 

--- 
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/groups/opt_out.

Reply via email to