emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [babel] Purpose of :results raw
Date: Sat, 20 Apr 2013 13:52:12 +0200	[thread overview]
Message-ID: <87vc7ho1w3.fsf@gmail.com> (raw)
In-Reply-To: <868v4d3c7m.fsf@somewhere.org> (Sebastien Vauban's message of "Sat, 20 Apr 2013 09:14:53 +0200")



Hello,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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

  reply	other threads:[~2013-04-20 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 22:11 [babel] Purpose of :results raw Sebastien Vauban
2013-04-19 22:27 ` Nicolas Goaziou
2013-04-20  7:14   ` Sebastien Vauban
2013-04-20 11:52     ` Nicolas Goaziou [this message]
     [not found]       ` <CAJcAo8uRp8xOk+_cZefMc8PBfMDywzARdkTyCR_FDuXCLjAnZA@mail.gmail.com>
2013-04-22  1:43         ` Samuel Wales
2013-04-20 21:34   ` John Hendy

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=87vc7ho1w3.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \
    /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).