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

From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] in `org-element-interpret-data'
Date: Thu, 07 Aug 2014 11:15:14 +0200	[thread overview]
Message-ID: <87iom4acf1.fsf@gmail.com> (raw)


Hi List, 

when interpreting Org elements (type src-block) I frequently encounter
the case that the '#+end_src' delimter is not placed on a newline but
rather attached to the src-block's value without a linefeed in between.

I then have to append a "\n" to the src-block value to make things work,
but thats not a nice thing and causes problems in other places. The "\n"
should be set by the framework.

I think adding something like this at the end of the
interpreter-function could solve the problem, but this came out of
try-and-error only:
 
#+begin_src emacs-lisp
(((
 [...]
 (org-escape-code-in-string value)
 ;; check for newline
 (save-match-data
  (if (looking-at "^$") "" "\n"))
 "#+END_SRC")))
#+end_src

The problem seems to appear a bit randomly, but using my new function

#+begin_src emacs-lisp
;; might become `org-element-create'
(defun* tj/create-element (&optional insert-p &rest args &key (type 'headline) &allow-other-keys)
  "Create Org element, maybe insert at point."
  (let ((strg (org-element-interpret-data
	       (list type args))))
    (if insert-p (insert strg) strg)))
#+end_src

#+results:
: tj/create-element

I can give an the following example

#+begin_src emacs-lisp :results raw
  (tj/create-element nil
                     :type 'src-block
                     :language "emacs-lisp"
                     :value "(+ 2 2)")
#+end_src

#+results:
#+BEGIN_SRC emacs-lisp
  (+ 2 2)#+END_SRC

-- 
cheers,
Thorsten

next             reply	other threads:[~2014-08-07  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07  9:15 Thorsten Jolitz [this message]
2014-08-07 12:58 ` [BUG] in `org-element-interpret-data' Nicolas Goaziou

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=87iom4acf1.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.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

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