ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startuserdata syntax questions
Date: Wed, 29 Aug 2018 13:29:04 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.76.44.1808291328240.25695@ervasbepr.pvz.zptvyy.pn> (raw)
In-Reply-To: <80fca181-ee5e-a059-622e-645a9c69b572@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Wed, 29 Aug 2018, Wolfgang Schuster wrote:

>> The second question: Is there the possibility to enhance the syntax so 
>> that one can write
>>>
>>>     \startMyStuff [optionalkey=value, anotherkey=value]
>>>          stuff
>>>     \stopMyStuff
>>>
>>> instead of
>>>
>>>     \startuserdata [MyStuff] [optionalkey=value, anotherkey=value]
>>>     stuff
>>>     \stopuserdata
>
> I can generated environment commands but I haven’t done this at the 
> beginning because I prefer to pass the name of the environment as 
> argument because this allows me to check if the used instance exists.

Perhaps adding a `command=yes` key, which can be set to `no` by default.

Aditya

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2018-08-29 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 20:40 Rik Kabel
2018-08-29  7:15 ` Hans Hagen
2018-08-29 15:19   ` Wolfgang Schuster
2018-08-29 16:56     ` Rik Kabel
2018-08-29 17:29     ` Aditya Mahajan [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.YAK.7.76.44.1808291328240.25695@ervasbepr.pvz.zptvyy.pn \
    --to=adityam@umich.edu \
    --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).