emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [POLL] Syntax change: make \[...\] non-inline (+1)
Date: Sun, 3 Aug 2014 22:05:09 +0200	[thread overview]
Message-ID: <CAKrPhPMzx0=ry8pbnKuDocSKwtWC=xp6WDMToB-7cvB1vv+ZxA@mail.gmail.com> (raw)

> It's a bit more complicated than that: one upgrades org at some
> opportune moment, then three months/years/centuries later, tries to use
> that presentation that worked perfectly before - boom. If you go back
> and check all your old presentations each time you upgrade org, you are,
> I would guess, the exception, not the rule. I certainly don't do that

Well, if I reuse an old presentation I usually use the old pdf.

> I generally put displays in separate paragraphs, I rarely use
> autofill[fn:1] and I'm happy to do M-q on individual paragraphs instead,
> but if I happen to do it on the wrong paragraph (backtraces, code
> fragments, displayed equations), undo is easy enough.

The problem with that is that a displayed equation should NOT start a
new paragraph (in the generated LaTeX file). This is because if it
does then LaTeX puts more (vertical) space than desirable.

Regards,
Federico

             reply	other threads:[~2014-08-03 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 20:05 Federico Beffa [this message]
2014-08-03 20:48 ` [POLL] Syntax change: make \[...\] non-inline (+1) Nick Dokos
2014-08-04  8:55 ` Rasmus
  -- strict thread matches above, loose matches on Subject: below --
2014-08-03 16:32 Federico Beffa
2014-08-03 18:19 ` Nick Dokos
2014-08-01  8:22 Federico Beffa
2014-07-30 20:19 Federico Beffa
2014-07-30 16:50 Federico Beffa
2014-07-30 17:17 ` Nick Dokos
2014-07-31  9:03 ` Rasmus
2014-08-02 19:12   ` 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='CAKrPhPMzx0=ry8pbnKuDocSKwtWC=xp6WDMToB-7cvB1vv+ZxA@mail.gmail.com' \
    --to=beffa@ieee.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /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).