From: "Eric Schulte" <email@example.com> To: "Sébastien Vauban" <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Re: Org-Babel and Ledger Date: Thu, 12 Aug 2010 16:57:23 -0600 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (=?utf-8?Q?=22S=C3=A9bastien?= Vauban"'s message of "Thu, 12 Aug 2010 13:45:33 +0200") Hi Seb, Sébastien Vauban <firstname.lastname@example.org> 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 some awk or cut command that will >>>> do whatever is needed >>>> >>>> - Exploit the CSV export format (never tried, don't have Ledger 3 >>>> installed yet -- and I'm also using hledger...) >>> >>> Couldn't you use ledger's format strings for fine-tuned control of the >>> command output? I don't know how you're snarfing the output, but it seems >>> like you could using formatting to produce something that already looks >>> very much like an org table, or perhaps CSV. > > That anser is not really applicable in my case, as I would like to use at > least `ledger' and `hledger' for different reports, and they don't share the > same exporting capabilities. > > Plus the problem would come back for any other command-line tool... > > >> 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 from ob-sqlite.el). >> >> (if (or (member "scalar" result-params) >> (member "html" result-params) >> (member "code" result-params) >> (equal (point-min) (point-max))) >> (buffer-string) >> (org-table-convert-region (point-min) (point-max)) > > That's, then, the interesting line for me... > > >> (org-babel-sqlite-table-or-scalar >> (org-babel-sqlite-offset-colnames >> (org-table-to-lisp) headers-p))) >> >> I would recommend this approach over shell-script post-processing. > > That seems not to work for me, as input data is, for example: > > 09-Aug-21 CHEQUE : 9953055 Expenses:Unknown 166.70 EUR 166.70 EUR > 09-Sep-17 CHEQUE : 7691785 Expenses:Unknown 100.00 EUR 266.70 EUR > 09-Oct-16 REMISE CHEQUE N 8686318 001 105 Expenses:Unknown -525.00 EUR -258.30 EUR > > and as =org-table-convert-region= can't convert fixed positioned fields > (when SPC are used instead of TAB): > > (org-table-convert-region beg0 end0 &optional separator) > > Convert region to a table. > The region goes from beg0 to end0, but these borders will be moved > slightly, to make sure a beginning of line in the first line is included. > > separator specifies the field separator in the lines. It can have the > following values: > > '(4) Use the comma as a field separator > '(16) Use a TAB as field separator > integer When a number, use that many spaces as field separator > nil When nil, the command tries to be smart and figure out the > separator in the following way: > - when each line contains a TAB, assume TAB-separated material > - when each line contains a comma, assume CSV material > - else, assume one or more SPACE characters as separator. > > Should that function be smarter, or do I still need pre-processing, then? > Neither, notice that if you pass an integer as the third argument to org-table-convert-region it will parse on that many consecutive spaces. The following works for me, on the case your provided although I suppose it may not work on all cases. --8<---------------cut here---------------start------------->8--- #+results: ledger-output #+begin_example 09-Aug-21 CHEQUE : 9953055 Expenses:Unknown 166.70 EUR 166.70 EUR 09-Sep-17 CHEQUE : 7691785 Expenses:Unknown 100.00 EUR 266.70 EUR 09-Oct-16 REMISE CHEQUE N 8686318 001 105 Expenses:Unknown -525.00 EUR -258.30 EUR #+end_example #+begin_src emacs-lisp :var ledger=ledger-output (with-temp-buffer (insert ledger) (message ledger) (org-table-convert-region (point-min) (point-max) 2) (org-table-to-lisp)) #+end_src #+results: | 09-Aug-21 CHEQUE : 9953055 | Expenses:Unknown | 166.70 EUR | 166.70 EUR | | 09-Sep-17 CHEQUE : 7691785 | Expenses:Unknown | 100.00 EUR | 266.70 EUR | | 09-Oct-16 REMISE CHEQUE N 8686318 001 105 | Expenses:Unknown | -525.00 EUR | -258.30 EUR | --8<---------------cut here---------------end--------------->8--- Hope this helps -- Eric > > Thanks for your comments... > > Best regards, > Seb
next prev parent reply other threads:[~2010-08-12 22:57 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-29 9:40 Sébastien Vauban 2010-07-29 16:33 ` Eric Abrahamsen 2010-07-30 20:47 ` Eric Schulte 2010-08-12 11:45 ` Sébastien Vauban 2010-08-12 22:57 ` Eric Schulte [this message] 2010-08-13 9:23 ` Sébastien Vauban 2010-08-13 11:33 ` Sébastien Vauban 2010-08-13 17:41 ` Eric Schulte 2010-08-13 19:04 ` Sébastien Vauban
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Re: Org-Babel and Ledger' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).