ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "j. van den hoff" <veedeehjay@googlemail.com>
To: "Wolfgang Schuster" <schuster.wolfgang@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: equivalent to \newcommand{...}{\ensuremath{...}}
Date: Tue, 09 Dec 2014 13:36:53 +0100	[thread overview]
Message-ID: <op.xqlpbrmnp7eajd@marco.fz-rossendorf.de> (raw)
In-Reply-To: <12173030-9C54-4287-9491-DCDA6F04D904@gmail.com>

On Tue, 09 Dec 2014 10:05:22 +0100, Wolfgang Schuster  
<schuster.wolfgang@gmail.com> wrote:

>
>> Am 09.12.2014 um 09:59 schrieb j. van den hoff  
>> <veedeehjay@googlemail.com>:
>>
>> On Tue, 09 Dec 2014 09:42:03 +0100, Wolfgang Schuster  
>> <schuster.wolfgang@gmail.com <mailto:schuster.wolfgang@gmail.com>>  
>> wrote:
>>
>>>
>>>> Am 08.12.2014 um 17:41 schrieb j. van den hoff  
>>>> <veedeehjay@googlemail.com>:
>>>>
>>>> hi list,
>>>>
>>>> new to `context' and my first question to the list: how can I achieve  
>>>> the following (`latex') behaviour:
>>>>
>>>> \newcommand{\km}{\ensuremath{K_m}}
>>>> We can now use \km\ in the body text as well as in this
>>>> \begin{equation}
>>>>  \km = 1
>>>> \end{equation}
>>>> display equation.
>>>>
>>>> in `context'? I've tried something like
>>>>
>>>> \def\km{\math{K_m}}
>>>> We can now use \km\ in the body text but get sytnax errors when
>>>> putting it in this
>>>> \startformula
>>>>  \km = 1
>>>> \stopformula
>>>> formula.
>>>>
>>>> but this fails for obvious reasons (as would using `$$' instead of  
>>>> `ensuremath' in the `latex' case).
>>>>
>>>> so what I need is a way of defining (potentially complex)  
>>>> math-expressions via some shortcuts/definitions/macros/abbreviations  
>>>> (whatever) which I can then use
>>>> in the formula environment (or whatever it's called in `context'...)  
>>>> as well as in the body text.
>>>>
>>>> any help appreciated,
>>>
>>> In ConTeXt you have to write
>>>
>>>    \define\km{\mathematics{K_m}}
>>>
>>> but there is not much to gain from this because you can enter math  
>>> mode in the text with \m{…}.
>>
>> thanks for the response. in my silly example you are right (but even  
>> there it saves more than 50% of keystrokes). but I'm thinking of course  
>> of more tedious math expressions where it rapidly is handy to use such  
>> abbreviations -- the more so, if you have, say, 20 different ones  
>> appearing repeatedly in the document. but that would work with the  
>> `\def..\math' construct in the body text. what does _not_ work, then,  
>> is to use the definition in a display (\startformula...\stopformula)  
>> equation (which it _does_ in latex when isolating the math expression  
>> with `ensuremath'). so my real question(s) are:
>>
>> 1. is there any way to achieve the same functionality in `context'  
>> (expansion of math-containing defintion/macro/abbreviation in text  
>> _and_ math environment? if yes, how would I do this?
>>
>> 2. if no, would it be sensible (and feasible) to modify `\math'  
>> behaviour and to make it aware of whether it is called from within text  
>> or from within a display equation (in which case it should do  
>> nothing...), i.e.  mkae it behave like `\ensuremath' in latex?
>
>
> 1 + 2:
>
> \define\Foo{\mathematics{f(x)}}
> \define\Bar{\mathortext {f(x)}{\m{g(x)}}}
>
> \starttext
>
> a \Foo\ \Bar\ b
>
> \startformula
> \Foo\ \Bar
> \stopformula
>
> \stoptext

feeling silly: now it works (so there was no real problem in the first  
place...), but previously I definitely got syntax errors when compiling if  
the `\def'
was used in the display equation (no idea, why, but I must have overlooked  
some dumb typo or similar). anyway, sorry for the noise and thanks again...

since I'm really new to `context': are there any potential problems with  
inserting white space in `\define' lines like `\define \Foo {  
\mathematics{f(x)} }' which I might miss? `context' seems to ignore them  
and they don't creep into the formatted output AFAICS (which is good).

j.

ps: `\mathortext' is nice. should this not be in the manuals/documentation  
somewhere? it seems it is not ...

>
> Wolfgang


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/
___________________________________________________________________________________
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:[~2014-12-09 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 16:41 j. van den hoff
2014-12-09  8:42 ` Wolfgang Schuster
2014-12-09  8:59   ` j. van den hoff
2014-12-09  9:05     ` Wolfgang Schuster
2014-12-09 12:36       ` j. van den hoff [this message]
2014-12-09 13:30         ` Hans Hagen
2014-12-09 22:11           ` j. van den hoff
2014-12-09 15:12 ` Aditya Mahajan
2014-12-09 15:25   ` j. van den hoff
2014-12-09 15:36   ` Peter Münster

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=op.xqlpbrmnp7eajd@marco.fz-rossendorf.de \
    --to=veedeehjay@googlemail.com \
    --cc=ntg-context@ntg.nl \
    --cc=schuster.wolfgang@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.
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).