PS: keep in mind these two ways to use account aliases:

1. aliasing a short convenient name to the real account name, for a less 
verbose journal and easier data entry. This is what most people seem to use 
them for, and is what's in the Ledger manual. Not much need for regexp matching 
in this use case.

2. rewriting real account names in arbitrary ways, to massage report output, 
rearrange accounts, temporarily combine accounts, etc. This is what I use them 
for, and here the extra power is handy.



> On May 9, 2015, at 7:00 AM, Simon Michael <[email protected]> wrote:
> 
> Hi all, I'm seeking more input on
> 
> https://github.com/simonmichael/hledger/issues/252 
> "Please allow for aliases without regular expression expansion (and 
> re-establish compatibility with ledger)"
> 
> To recap, hledger 0.24+'s alias directive takes a regular expression, and 
> matches anywhere inside the account name. I find this much more useful, but 
> there are a few problems still to iron out.
> 
> The biggest is that you now often need to change aliases that you used before 
> 0.24, or that are in a Ledger file, to keep them working as intended. I think 
> it's (almost?) always possible to adjust them so that they'll still work in 
> both hledger and Ledger, but you need to (a) realize this and (b) know a 
> little about regular expressions.
> 
> As I say on the issue, it's a little painful to make the user use a special 
> syntax to get a regexp, since regexps are the default elsewhere in h/Ledger. 
> And I'd like not to add new syntax that Ledger won't accept. Some of the 
> options I suggest there are:
> 
> - get Ledger to also use regexp aliases. Any interest in this, Ledger folks ?
> 
> - have hledger wrap alias regexps in an implicit ^...$
> 
> - make hledger's aliases non-recursive by default, like Ledger
> 
> Reply here or on the issue. Thanks!

-- 

--- 
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.

Reply via email to