ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re:  Deprecated $…$ for inline math?
Date: Tue, 16 Feb 2016 16:59:58 +0100	[thread overview]
Message-ID: <20160216165958.32d19e22@homerow> (raw)
In-Reply-To: <20160216082142.473508a3@cea.fr>

On Tue, 16 Feb 2016 08:21:42 -0700
Alan BRASLAU <alan.braslau@cea.fr> wrote:

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

The stock vim context syntax highlighting ist terrible, indeed. I
modified the syntax files, the result is still terrible (and reflect
my personal context writing style instead of being general), but for
me they're better than the original ones. Then I contacted Nikolai
with the patches a while ago. He told me that he's not maintaining
the syntax files any longer and if I want to take over
maintainership. I declined because I know I wouldn't have much time
at my disposal the next months.

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

While I agree on that one, writing \math{x^2} clearly states what it
is. TeX tradition aside, dollar signs make no sense here and you
have to manually match beginning and end. Braces are matched
automatically (probably depends on the editor as well).

Marco
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-02-16 15:59 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
2016-02-16 15:59     ` Marco Patzer [this message]
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=20160216165958.32d19e22@homerow \
    --to=lists@homerow.info \
    --cc=ntg-context@ntg.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).