emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Paul Stansell <paulstansell@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: fill paragraph: math and latex environments
Date: Wed, 03 Jul 2013 21:50:44 +0200	[thread overview]
Message-ID: <87zju3jucr.fsf@gmail.com> (raw)
In-Reply-To: <CAMJKaZwmqkf4RAqdcD=j+mDHZ6VBmdNYoMrg_2QRS=XV5JML+w@mail.gmail.com> (Paul Stansell's message of "Wed, 3 Jul 2013 15:38:30 +0100")

Hello,

Paul Stansell <paulstansell@gmail.com> writes:

> I'm sorry, but I don't fully understand your explanation as I don't
> know what you mean by an "element" in this context?

See: http://orgmode.org/worg/dev/org-syntax.html

> Also, am I missing something about the latex?  Do you want to be able
> to use display style maths inside a sentence (ie. avoid placing the
> maths on a new line but have it formatted in display style)?  That
> would seem strange as that's not what it's for.  I don't, therefore,
> see why anyone would want to write
>
>   Some text \[1+1\] and some other text

I do sometimes. I like compact text in my Org file, even though I know
the output will be different (and intend it to) when exported.

Let me try again with another example:

  Some text...

  \[1+1\]

  Some other text...

will not be possible anymore either. I like to use \[...\] for one
liners and \begin{equation*} ... \end{equation*} for more complicated
formulas. 

> I agree with you there.  It's not a big deal type, but I do think
>
> \[
> 1+1
> \[
>
> looks a lot nicer and cleaner in the org file than
>
> \begin{displaymath}
> 1+1
> \end{displaymath}

Of course but

  \[1+1\]

is a lot nicer than

  \[
  1+1
  \]

and

  \begin{equation*}
   u(x) =
    \begin{cases}
     \exp{x} & \text{if } x \geq 0 \\
     1       & \text{if } x < 0
    \end{cases}
  \end{equation*}


is (arguably) nicer than

  \[
   u(x) =
    \begin{cases}
     \exp{x} & \text{if } x \geq 0 \\
     1       & \text{if } x < 0
    \end{cases}
  \]

Anyway, it's a matter of taste. And currently, we can have both. We
won't anymore if we want to treat \[...\] as an element.


Regards,

-- 
Nicolas Goaziou

     prev parent reply	other threads:[~2013-07-03 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 16:14 fill paragraph: math and latex environments Albert Z. Wang
2012-09-17 19:16 ` Nicolas Goaziou
2012-09-18  0:37   ` Albert Z. Wang
2012-09-19 13:03     ` Nicolas Goaziou
2013-07-01 21:45       ` Paul Stansell
2013-07-02 17:16         ` Nicolas Goaziou
2013-07-03 14:38           ` Paul Stansell
2013-07-03 19:50             ` Nicolas Goaziou [this message]

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=87zju3jucr.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=paulstansell@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

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