Thanks Peter for this message. I re-discovered the tool, and finally
switched to it! The 'i' of icsv2ledger ('i' meaning interactive) is what
convinced me. I forked and pulled some changes in github.
I have others changes but they may break some existing functionalities. I
write below what I have in mind, that may start a discussion about them:
- I want to use icsv2ledger through unix pipes. That means ability to read
from stdin (I think this is easy implementing this using fileinput python
module), and ability to write to stdout. This latter will break existing
way of working, as the default is "csv_filename" which csv extension is
replaced with .ledger. I procrastinate on how to implement it: 3 different
outputs can be used : stdout, csv_filename.ledger or newfilename. But the
unix philosophy would teach me to use only stdout and newfilename. But this
break the existing. And also, this may suppress the ability to treat
several input files. Any advise welcomed.
- I believe that --no-output-tags and --read-file can be moved to config
file (instead of executable option)
Thierry
On Tuesday, September 25, 2012 3:10:18 AM UTC+2, Peter Ross wrote:
>
> On 25 September 2012 08:19, thierry wrote:
> > icsv2ledger, from Quentin Stafford-Fraser
> > https://github.com/quentinsf/icsv2ledger
> > - code does not look to be unicode compliant
> > - can not rename payee
> >
> You can rename the payee now.
>
> It also has the advantage that it remembers the renaming of payee (and
> account), so that if you have the exact same payee in the future it
> automatically suggests your renaming.
>
> It also has the advantage that it does tab completion on account names
> and payees, so that you can type just a few letters for the payee and
> press tab to get complete payee name.
>
> I personally use this tool (and contributed the rename payee code) and
> for me it works how I want.
>
