emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: math in parentheses
Date: Tue, 28 Oct 2014 17:30:29 +0000	[thread overview]
Message-ID: <olu7fzkje4q.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87sii8yv4v.fsf@alphaville.bos.redhat.com

Hi Nick,

Nick Dokos <ndokos@gmail.com> writes:
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> Hi Richard,
>>
>> Richard Lawrence <richard.lawrence@berkeley.edu> writes:
>>> Hi Andreas,
>>>
>>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>>
>>>> I encounter a problem using $..$ expressions when they are enclosed
>>>> in parentheses.
>>>
>>>> This $T$ works, but ($T$) this does not.
>>>>
>>>> Is that expected behaviour?
>>>>
>>>> (Note that \(...\) expressions work.)
>>>
>>> Yes, that is the expected behavior.  Org is much pickier about when "$"
>>> can be a math delimiter than "\( ... \)".  The reason is that "$" can
>>> also be used as a regular symbol in Org documents; when it is, it should
>>> be *not* be exported as a math delimiter to LaTeX, and distinguishing
>>> non-math-delimiting from math-delimiting uses of "$" is not a trivial
>>> matter.
>>>
>>> Thus, when in doubt, use "\( ... \)".
>>>
>>
>> Thanks for following that up.  I do use \(...\) when I encounter
>> problems with $...$ (which is a lot nicer to type and read).
>>
>> I am happy with using the fall-back \(...\) every now and then.
>>
>> Just for me to understand:  Is the problem the missing whitespace
>> around the $...$ expression?
>>
>
> See
>
>    http://tex.stackexchange.com/questions/510/are-and-preferable-to-dollar-signs-for-math-mode
>
> for some arguments for and (mostly) against (although one of the "for"s
> is Frank Mittelbach - which surely tilts the scale quite a lot).

Thanks.  A very good read.  These are arguments on the LaTeX end.  My
question was more on the orgmode end, I guess.

> FWIW,
> I've trained myself to use \(...\) and don't find it any harder to read
> than $...$ - and I don't mind the extra typing either.  The fact that
> both org and MathJax deal better with \(...\) just reinforces that
> choice.

I do not agree with the readability but I can live (quite happily) with
using \(...\).  And maybe my perception of the readability changes over
time....

Regards,
Andreas

  reply	other threads:[~2014-10-28 17:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 12:54 math in parentheses Andreas Leha
2014-10-28 15:50 ` Richard Lawrence
2014-10-28 16:03   ` Andreas Leha
2014-10-28 16:31     ` Rasmus
2014-10-28 16:57       ` Andreas Leha
2014-10-28 22:32         ` Rasmus
2014-10-29  9:55           ` Andreas Leha
2014-10-28 17:14     ` Nick Dokos
2014-10-28 17:30       ` Andreas Leha [this message]
2014-10-29 12:24       ` Rasmus
2014-10-29 13:03         ` Nick Dokos
2014-10-31 18:09         ` Eric S Fraga

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=olu7fzkje4q.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.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).