emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scot Becker <scot.becker@gmail.com>
To: Scot Becker <scot.becker@gmail.com>,
	Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>,
Cc: Nicolas <n.goaziou@gmail.com>
Subject: Re: latex export issue
Date: Thu, 10 Mar 2011 21:29:05 +0000	[thread overview]
Message-ID: <AANLkTikTHyEvQ4x=ZACyRMaQJLZBGUG+un6yBj9bnwjp@mail.gmail.com> (raw)
In-Reply-To: <8739mvs7ru.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]

Looks good, but I can't get it to work.  To test it, can I just evaluate the
two sexp's in the block you gave inside a scratch buffer, then switch to my
trial org file and export to LaTeX?  Trying the OP's sample file gives the
same results before and after I evaluate this new bit of code, but I suspect
I'm doing something wrong....


On Thu, Mar 10, 2011 at 8:24 AM, Nicolas <n.goaziou@gmail.com> wrote:

> Hello,
> Scot Becker <scot.becker@gmail.com> writes:
> > That sounds like it means that any documents you might want to export to
> > LaTeX (and format with hard line breaks) should always have non-breaking
> > spaces after the periods---or you should keep a manual eye on your
> paragraph
> > formatting to make sure no numbers come first on the line.
> Would that work for you?
> #+begin_src emacs-lisp
> (defun org-fill-item-nobreak-p ()
>  "Non-nil when line break would insert a new item."
>  (and (looking-at (org-item-re)) (org-list-in-valid-block-p)))
> (add-to-list 'fill-nobreak-predicate 'org-fill-item-nobreak-p)
> #+end_src
> If it is fine, we may as well include it by default in Org.
> Regards,
> --
> Nicolas

[-- Attachment #2: Type: text/html, Size: 1676 bytes --]

  reply	other threads:[~2011-03-10 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 22:05 latex export issue Stephen Eglen
2011-03-09 23:46 ` Nicolas
2011-03-10  6:16   ` Scot Becker
2011-03-10  8:24     ` Nicolas
2011-03-10 21:29       ` Scot Becker [this message]
2011-03-10 22:00         ` Nicolas
2011-03-10 22:07           ` Scot Becker
2011-03-11 11:26             ` Stephen Eglen

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:

  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='AANLkTikTHyEvQ4x=ZACyRMaQJLZBGUG+un6yBj9bnwjp@mail.gmail.com' \
    --to=scot.becker@gmail.com \
    --cc=S.J.Eglen@damtp.cam.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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