From: Dan Davison <davison@stats.ox.ac.uk>
To: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-babel-perl and formats
Date: Thu, 08 Apr 2010 11:50:06 -0400 [thread overview]
Message-ID: <8739z6djv5.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <874ojm7py8.fsf@kotik.lan> ("Łukasz Stelmach"'s message of "Thu, 08 Apr 2010 02:22:55 +0200")
Łukasz Stelmach <lukasz.stelmach@iem.pw.edu.pl> writes:
> Hello.
>
> I am not sure I will be able to spend some time on this so I'll share my
> observation with you. org-babel-perl can't cope with perl formats, with
> their endings to be precise. A format is defined by:
>
> format FORMAT_NAME =
> body of the format
> .
>
> The problem is that formats *must* and with a single solitary dot or, to
> be precise "\n.\n" sequence. org-babel-perl doesn't care about it and
> puts "\t" befor the dot.
Hi Łukasz,
Could you post an example? I don't believe we insert tab
characters. I've never used a perl format before, but I just tried it
and it seemed to work OK with C-c C-c:
--8<---------------cut here---------------start------------->8---
#+begin_src perl
format STDOUT =
@<<<<<< @|||||| @>>>>>>
"left", "middle", "right"
.
write ;
#+end_src
#+results:
: left middle right
--8<---------------cut here---------------end--------------->8---
Incidentally, do you know the variable org-src-preserve-indentation?
When I first read your email I thought that would be the answer. In fact
it doesn't seem to be relevant, but I thought I would mention it anyway.
Dan
>
> Are these indents really necessary in the text
> that goes straight through IPC pipes of our OS of choice?
next prev parent reply other threads:[~2010-04-08 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 0:22 [BUG] org-babel-perl and formats Łukasz Stelmach
2010-04-08 15:50 ` Dan Davison [this message]
2010-04-09 9:11 ` Łukasz Stelmach
2010-04-09 13:21 ` Dan Davison
2010-04-09 20:53 ` Łukasz Stelmach
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=8739z6djv5.fsf@stats.ox.ac.uk \
--to=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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).