From: Alan BRASLAU <alan.braslau@cea.fr>
To: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Deprecated $…$ for inline math?
Date: Tue, 16 Feb 2016 08:21:42 -0700 [thread overview]
Message-ID: <20160216082142.473508a3@cea.fr> (raw)
In-Reply-To: <56C2E3C1.9010802@wxs.nl>
On Tue, 16 Feb 2016 09:54:25 +0100
Hans Hagen <pragma@wxs.nl> wrote:
> On 2/16/2016 9:22 AM, Nicola wrote:
> > I read in the wiki (http://wiki.contextgarden.net/Math) that $…$
> > for inline math is deprecated in favor of \m{…} and more verbose
> > variants. Is that really the case? If so, what is the reason and
> > what are the differences?
>
> that page probably needs updating
>
> anyway, it's unlikely that $ will be dropped (ok, i can imagine a
> mode where dollars are dollars) because it's popular as math
> delimiter; however \m has more potential for structure (we can at
> some point even considering it an instance of a more general inline
> math mechanism)
Personally, I never use \m and remain (culturally) attached to $...$
syntax. This being said, I am not a TeX purist as I never use
$$
...
$$
to delimit display math (even in LaTeX).
I see no problem with having a few reserved characters, and since I do
not often write about money or use percentages much, I have no problem
using {\%} or {\$} when I really need them. I can imagine, though, that
a finance writer might find this annoying.
I do note that the VIM syntax highlighting routine is pretty poor and
has difficulties around $, which is a symbol that I like using
(unpaired) quite a lot in MetaPost (\startMPcode...\stopMPcode).
What sort of needs for structure could \m address for inline math?
Clearly, an equation to which one might want to have a reference
math should appear rather as displayed math.
Alan
--
Alan Braslau
CEA DSM-IRAMIS-SPEC
CNRS UMR 3680
Orme des Merisiers
91191 Gif-sur-Yvette cedex FRANCE
tel: +33 1 69 08 73 15
fax: +33 1 69 08 87 86
mailto:alan.braslau@cea.fr
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-02-16 15:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 8:22 Nicola
2016-02-16 8:54 ` Hans Hagen
2016-02-16 15:21 ` Alan BRASLAU [this message]
2016-02-16 15:59 ` Marco Patzer
2016-02-16 16:20 ` Hans Hagen
2016-02-16 19:12 ` Alan BRASLAU
2016-02-16 18:50 ` Aditya Mahajan
2016-02-16 19:18 ` Alan BRASLAU
2016-02-17 7:31 ` Otared Kavian
2016-02-17 9:44 ` Hans Hagen
2016-02-17 16:32 ` Alan BRASLAU
2016-02-17 18:24 ` Aditya Mahajan
2016-02-17 20:45 ` Rogers, Michael K
2016-02-17 22:18 ` Alan BRASLAU
2016-02-17 23:40 ` Pablo Rodriguez
2016-02-18 0:38 ` Alan BRASLAU
2016-02-18 9:22 ` Hans Hagen
2016-02-18 9:57 ` Marcin Borkowski
2016-02-18 20:37 ` Mojca Miklavec
2016-02-18 21:01 ` Hans Hagen
2016-02-18 9:16 ` Hans Hagen
2016-02-18 9:25 ` Meer, Hans van der
2016-02-16 16:16 ` Hans Hagen
2016-02-16 8:56 ` Marco Patzer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160216082142.473508a3@cea.fr \
--to=alan.braslau@cea.fr \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
/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.
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 NNTP newsgroup(s).