From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luka Stanisic <luka.stanisic@imag.fr>
Subject: [babel] Shell session output problem
Date: Thu, 31 Jul 2014 16:21:38 +0200
Message-ID: <53DA50F2.4010206@imag.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42019)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <luka.stanisic@imag.fr>) id 1XCrSp-0007Nt-Pz
	for emacs-orgmode@gnu.org; Thu, 31 Jul 2014 10:36:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <luka.stanisic@imag.fr>) id 1XCrSi-0008EF-89
	for emacs-orgmode@gnu.org; Thu, 31 Jul 2014 10:36:15 -0400
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org, bzg@gnu.org
Cc: Arnaud Legrand <arnaud.legrand@imag.fr>

Hello,

     When running org-babel shell snippets in *session*, I stumbled upon 
the following problem:

     Output shown in my .org file is already formatted:
     1. Starting white spaces are lost
     2. All code before first ">", "$" or "#" (prompt related?) is lost

     Here is a minimal example (run it twice, first time when opening a 
new session it is working)

#+begin_src sh :results output  :session org-sh-test
echo "   too$  foo"
echo "      too$  foo"
#+end_src

#+RESULTS:
:
: foo
: too$  foo


     Is there a way or some org-babel options to avoid this behavior?

     I see how this formatting can be beneficial in many cases, but this 
doesn't apply for mine.

Best regards,
Luka