From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Org-Babel and Ledger
Date: Fri, 13 Aug 2010 11:41:31 -0600 [thread overview]
Message-ID: <87iq3ewgtw.fsf@gmail.com> (raw)
In-Reply-To: <87fwyizr0f.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Fri, 13 Aug 2010 13:33:20 +0200")
Hi Seb,
Sébastien Vauban <wxhgmqzgwmuf@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").
>>>>>>>
>>>>>>> What can I do about this?
>>>>>>>
>>>>>>> - Post-process every ledger command with some awk or cut command that
>>>>>>> will do whatever is needed
This might actually be a good solution for the shell block you mention
below.
>>>>>
>>>>> (org-table-convert-region (point-min) (point-max))
>
> As you adviced, I can play with the optional parameter in ob-ledger's code.
>
> But what about the results of sh code?
>
> Imagine now that I'm forced to use =sh= instead of =ledger=, in the following
> pratical case:
>
> #+srcname: reg
> #+begin_src sh
> m4 scorpios-ledger.dat | ledger -f - reg unknown
> #+end_src
>
> I'm using =m4= (and thus make some pre-processing) because I need (or want) to
> be able to switch between =ledger= and =hledger= and comment in or out the
> directives that are accepted by one but not by the other.
>
> Then, such a result is still problematic:
>
> 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
>
> I've looked in =org-babel-execute:sh= and =org-babel-reassemble-table=, among
> others, to look for similar constructs (calls to =org-table-convert-region=)
> but did not find any.
>
> Is there still a solution to get such results?
>
As an interim solution you could add a :results scalar header argument
to your sh code block, then pass the output of that code block to a
parsing code block (namely the one from my previous email). That's
certainly not idea, but it should work for the moment.
Alternately if ledger supports a more clearly delimited output format
(e.g. csv) then that would probably work as well.
>
> #+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 |
>
> Couldn't we specify somehow the field separator as an extra header
> argument? I've looked for such an already existing in
> http://orgmode.org/manual/Specific-header-arguments.html#Specific-header-arguments,
> but that does not seem to be available yet.
This would probably be a good addition to ob-sh (and any other language
which doesn't have a defined list syntax). I'll add this idea to the
babel dev stack, but I'm swamped for the next week or so.
Best -- Eric
> Though, I do not know if this is the right solution. I'm sure you'll
> tell me... ;-)
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-08-13 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 9:40 Org-Babel and Ledger 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
2010-08-13 9:23 ` Sébastien Vauban
2010-08-13 11:33 ` Sébastien Vauban
2010-08-13 17:41 ` Eric Schulte [this message]
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 \
--in-reply-to=87iq3ewgtw.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public 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).