Jeremie Juste <jeremieju...@gmail.com> writes: > * Request > > However If I have a csv file with say semi column delimited values (;) > I don't get the org table as output > > #+begin_src awk :in-file test1.csv :cmd-line -F ";" > {print $0} > #+end_src > > #+RESULTS: > : 123;0;123
> In my opinion, this could be fixed if we could read the :cmd-line > parameter -F and use the delimeter argument ; as a parameter to the > following function Org knows nothing about your output, by default. You could as well do something like {print $1+-+$2+-+$3} What should Org do in such case? Currently, Org tries to guess the type of arbitrary output. If the output looks like a table, with fields separated by tabs, commas, or spaces, it converts the output to table. Otherwise, it is treated as string. I guess we might add an option to tell Org which separator to use when parsing output when :results table header argument is provided (see 16.6 Results of Evaluation section of Org manual). However, you can achieve the same now, using :post header argument, replacing the separators with something Org can understand. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>