Hi Eric,
Eric Schulte wrote:
Sébastien Vauban wxhgmqzgw...@spammotel.com writes:
As you can see, the tables are completely wrongly made, because they're
based on spaces (à la Awk) and not on fixed position of fields (à la
Cut).
What can I do about this?
- Post-process every ledger
Hi Eric,
Sébastien Vauban wrote:
Eric Schulte wrote:
Sébastien Vauban writes:
As you can see, the tables are completely wrongly made, because they're
based on spaces (à la Awk) and not on fixed position of fields (à la
Cut).
What can I do about this?
- Post-process every ledger command
Hi Seb,
Sébastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Eric,
Sébastien Vauban wrote:
Eric Schulte wrote:
Sébastien Vauban writes:
As you can see, the tables are completely wrongly made, because they're
based on spaces (à la Awk) and not on fixed position of fields (à la
Cut).
Hi Eric,
Eric Schulte wrote:
Sébastien Vauban wxhgmqzgw...@spammotel.com writes:
Sébastien Vauban wrote:
Eric Schulte wrote:
Sébastien Vauban writes:
As you can see, the tables are completely wrongly made, because
they're based on spaces (à la Awk) and not on fixed position of
fields (à
Hi Seb,
Sébastien Vauban wxhgmqzgw...@spammotel.com writes:
Hi Eric(s),
As you can see, the tables are completely wrongly made, because they're
based on spaces (à la Awk) and not on fixed position of fields (à la
Cut).
What can I do about this?
- Post-process every ledger command with
Many languages import tabular contents into elisp tables which are then
inserted into Org-mode buffers as Org-formatted tables. This should be
possible by replacing the call to `buffer-string' at the end of the
`org-babel-execute:ledger' function with something analogous to the
following (copied
On Thu, Jul 29 2010, Sébastien Vauban wrote:
[...]
As you can see, the tables are completely wrongly made, because they're based
on spaces (à la Awk) and not on fixed position of fields (à la Cut).
What can I do about this?
- Post-process every ledger command with some awk or cut command
