From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Subject: Re: verbatim/code text and line breaks with auto fill mode
Date: Fri, 14 Mar 2014 00:02:34 +0100 [thread overview]
Message-ID: <871ty51z3p.fsf@gmail.com> (raw)
In-Reply-To: <87bnxaw6eo.fsf@bzg.ath.cx> (Bastien's message of "Thu, 13 Mar 2014 14:54:23 +0100")
Hello,
Bastien <bzg@gnu.org> writes:
> Hi Nicolas,
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>> OTOH, `latex' back-end could remove newline characters from verbatim and
>> code contents.
>
> Is it only for the LaTeX backend?
No idea.
> Or something we can add to `org-export-before-processing-hook'.
Hook are usually for user consumption. There is probably a better way to
handle it.
> In any case, yes, would be great if you could fix this somehow.
We first need to know what is the problem. Does Org allow newline
characters in verbatim objects? If it does, what backends do not support
it?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-03-13 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:45 verbatim/code text and line breaks with auto fill mode Alan Schmitt
2014-03-07 20:50 ` Nick Dokos
2014-03-08 7:58 ` Alan Schmitt
2014-03-08 12:12 ` Alan Schmitt
2014-03-10 11:09 ` Sebastien Vauban
2014-03-10 12:13 ` Nicolas Goaziou
2014-03-13 13:54 ` Bastien
2014-03-13 23:02 ` Nicolas Goaziou [this message]
[not found] ` <m2vbvhng0o.fsf@polytechnique.org>
2014-03-14 12:19 ` Alan Schmitt
2014-03-21 8:57 ` Bastien
[not found] ` <m2k3bnvp8p.fsf@polytechnique.org>
2014-03-21 10:57 ` Alan Schmitt
2014-03-18 22:35 ` R. Michael Weylandt <michael.weylandt@gmail.com>
2014-03-24 20:47 ` Michael Weylandt
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=871ty51z3p.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@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).