From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [Exporter] Keep formatting or non-org comment-section when exporting?
Date: Tue, 08 Apr 2014 19:42:02 +0200 [thread overview]
Message-ID: <87wqezwwet.fsf@gmail.com> (raw)
Hi Nicolas,
is there any way to make the exporter recognize non-org comment-syntax
in an org-buffer?
When writing emails with outorg, I often have these message-mode quotes
in the outorg-edit-buffer which have outcommented multiple times and
therefore remain as message-mode comments). They do not cause any
problems for editing, since outorg/org-mode treats them like normal
text, but formatting is lost when exporting:
,----------------------------------------------------------------------------
| > Thorsten Jolitz <tjolitz@gmail.com> writes:
| >
| >> I like to use rebox2 and put boxes in emails and source-file
| >> comment-sections, but when I use outorg on such an message-mode or elisp
| >> buffer and try to export it, I always get 'Args out of range' errors:
| >
| > The following line
| >
| > | org-element--parse-objects: Args out of range: 315, 316
| >
| > is a table row in Org syntax, so it will not be exported as you expect
| > it to. However, it shouldn't return an error. I fixed it.
| >
| > Thank you for your report.
`----------------------------------------------------------------------------
becomes:
#+begin_src emacs-lisp :results value replace
(org-export-as 'ascii)
#+end_src
#+results:
,------------------------------------------------------------------------
| _________________
|
| Thorsten Jolitz
| _________________
|
|
| 1 --text follows this line--
| ============================
|
| Nicolas Goaziou <n.goaziou@gmail.com> writes:
|
| > Hello, Thorsten Jolitz <tjolitz@gmail.com> writes: > I like to use
| >rebox2 and put boxes in emails and source-file > comment-sections,
| >but when I use outorg on such an message-mode or elisp > buffer and
| >try to export it, I always get 'Args out of range' errors: The
| >following line | org-element--parse-objects: Args out of range: 315,
| >316 is a table row in Org syntax, so it will not be exported as you
| >expect it to. However, it shouldn't return an error. I fixed it.
| >Thank you for your report.
`------------------------------------------------------------------------
This is a pity, would be nice if these quoted section could be wrapped
in a verbatim-type block so that exporting them gives a nice result.
The same thing happens when I use outorg with e.g. emacs-lisp or
picolisp. Section that are outcommented twice or more like
,-----------
| ;; ;; Comment
| ;; ;; part
`-----------
are seen in the outorg-edit-buffer like
,-----------
| ;; Comment
| ;; part
`-----------
and lose their formatting when exported.
--
cheers,
Thorsten
next reply other threads:[~2014-04-08 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 17:42 Thorsten Jolitz [this message]
2014-04-08 18:37 ` [Exporter] Keep formatting or non-org comment-section when exporting? 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqezwwet.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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.