emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: verbatim/code text and line breaks with auto fill mode
Date: Mon, 10 Mar 2014 13:13:45 +0100	[thread overview]
Message-ID: <87lhwi8d52.fsf@gmail.com> (raw)
In-Reply-To: <86siqqfgz3.fsf@somewhere.org> (Sebastien Vauban's message of "Mon, 10 Mar 2014 12:09:04 +0100")



Hello,

Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

> Alan Schmitt wrote:
>> I've continued looking into this, and it seems that what I want is use
>> `fill-nobreak-predicate'. This is what I ended up doing:
>>
>> #+begin_src emacs-lisp
>> (add-hook 'org-mode-hook
>>           (lambda ()
>>             (add-hook 'fill-nobreak-predicate 'org-in-verbatim-emphasis)))
>> #+end_src
>>
>> All the pieces were already there, it just took me a while to put them
>> together ;-)
>
> Shouldn't this be standard in Org, as it breaks LaTeX compilation
> otherwise?

This is not an Org problem, as verbatim objects can span over lines.

OTOH, `latex' back-end could remove newline characters from verbatim and
code contents.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-03-10 12:14 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 [this message]
2014-03-13 13:54         ` Bastien
2014-03-13 23:02           ` Nicolas Goaziou
     [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=87lhwi8d52.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --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).