From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [babel] Purpose of :results raw Date: Sat, 20 Apr 2013 13:52:12 +0200 Message-ID: <87vc7ho1w3.fsf@gmail.com> References: <86txn2i312.fsf@somewhere.org> <878v4ep362.fsf@gmail.com> <868v4d3c7m.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58197) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTWLI-0007jX-Df for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 07:52:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UTWLH-00070K-JJ for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 07:52:32 -0400 Received: from plane.gmane.org ([80.91.229.3]:52903) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTWLH-00070D-CH for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 07:52:31 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UTWLE-0004ko-Ch for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 13:52:28 +0200 In-Reply-To: <868v4d3c7m.fsf@somewhere.org> (Sebastien Vauban's message of "Sat, 20 Apr 2013 09:14:53 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org Hello, "Sebastien Vauban" writes: > The fact that the following output a normally behaving headline[1], AFAICS. > > #+begin_src sh :results drawer :exports both > echo "* Unescaped headline" > #+end_src > > #+results: > :RESULTS: > * Unescaped headline > :END: > > Though, effectively, when exported, it's not right: [...] > Do you mean it, because of the wrong export? By wrong, I don't mean "buggy", > but "not foreseen as I (= me) thought". Both cycling mechanism and fontification are bad indicators about the syntax at point. Use either `org-element-at-point' or `org-element-context' to know what is really parsed, according to the Org syntax. I will slowly integrate org-element-at-point in core interactive functions, like visibility cycling. Though, fontification will have to wait, because the parser isn't ready for that yet. Regards, -- Nicolas Goaziou