emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [babel] Expertise in string manipulation available?
Date: Wed, 10 Aug 2011 18:17:04 -0400	[thread overview]
Message-ID: <6036.1313014624@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com> of "Thu, 11 Aug 2011 00:00:21 +0200." <801uwtapvu.fsf@somewhere.org>

Sebastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:

> Hello,
> 
> #+TITLE:     String manipulation
> 
> * Data
> 
> #+tblname: list-of-couples
> | Me           | @Here  |
> | Myself and I | @There |
> 
> * Successful outcome
> 
> I expect the above table to be transformed to those lines:
> 
> #+begin_example
> ---
> Me
> @Here
> ---
> Myself and I
> @There
> #+end_example
> 

I can do it easily in python except that I don't know how to produce the #+begin/end_example block.
My results are preceded by colons:

--8<---------------cut here---------------start------------->8---
* Data

#+tblname: list-of-couples
| Me           | @Here  |
| Myself and I | @There |

#+begin_src python :var table=list-of-couples :exports code :results output :tangle no
  for row in table:
      print "---"
      for i in range(len(row)):
          print row[i]
#+end_src

#+results:
: ---
: Me
: @Here
: ---
: Myself and I
: @There
--8<---------------cut here---------------end--------------->8---

Nick

> * First attempt
> 
> ** Code and output
> 
> #+begin_src awk :stdin list-of-couples :exports code :results output :tangle no
> {
>     print "---";
>     print $1;
>     print $2;
> }
> #+end_src
> 
> #+results:
> #+begin_example
> ---
> Me
> @Here
> ---
> Myself
> and
> #+end_example
> 
> ** Issue
> 
> The first line of the table is perfectly outputted.
> 
> The second line is not, because of the space in its first column: $2 refers
> then to the second word, not to the string of the second column.
> 
> * Second attempt
> 
> ** Code and output
> 
> #+begin_src emacs-lisp :var data=list-of-couples :exports results :results output :tangle no
> (mapc
>  (lambda (item)
>    (print (format "---\n%s\n%s\n"
>                   (first item)
>                   (second item))))
>  data)
> #+end_src
> 
> #+results:
> #+begin_example
> 
> "---
> Me
> @Here
> "
> 
> "---
> Myself and I
> @There
> "
> #+end_example
> 
> ** Issue
> 
> Literal double quotes are inserted in the output. Plus blank lines...
> 
> Best regards,
>   Seb
> 
> -- 
> Sebastien Vauban
> 
> 

next prev parent reply	other threads:[~2011-08-10 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 22:00 [babel] Expertise in string manipulation available? Sebastien Vauban
2011-08-10 22:17 ` Nick Dokos [this message]
2011-08-11 22:17   ` Sebastien Vauban
2011-08-15  0:29     ` Nick Dokos

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=6036.1313014624@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.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

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).