From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupnarrower and startnarrower
Date: Tue, 6 Aug 2013 16:09:46 +0200 [thread overview]
Message-ID: <20130806160946.7526a314@sole> (raw)
In-Reply-To: <C195415E-6594-4940-9C06-4D1B2E31D82D@gmail.com>
Thank you Wolfgang, but I was wondering about the standard \startnarrower.
Many (some) commands allow setup assignments, the use of which overides but does not change the default. This is a very useful feature of ConTeXt that suggest could be generalized. \startnarrower is but one example.
Alan
On Tue, 6 Aug 2013 15:27:16 +0200
Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>
> Am 06.08.2013 um 15:11 schrieb Alan BRASLAU <alan.braslau@cea.fr>:
>
> > Hello,
> >
> > Could (should) startnarrower be modified to accept setup assignments?
> > As in:
> >
> > \startnarrower [before=\blank,after=\blank]
> >
> > or
> >
> > \startnarrower [left=3cm] [left]
> >
> > etc.
>
>
> \usemodule[annotation]
>
> \defineannotation[NARROW][alternative=narrow]
>
> \starttext
>
> \input ward
>
> \startNARROW[leftmargin=3cm]
> \input ward
> \stopNARROW
>
> \input ward
>
> \startNARROW[rightmargin=2cm]
> \input ward
> \stopNARROW
>
> \input ward
>
> \stoptext
___________________________________________________________________________________
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:[~2013-08-06 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:11 Alan BRASLAU
2013-08-06 13:27 ` Wolfgang Schuster
2013-08-06 14:09 ` Alan BRASLAU [this message]
2013-08-06 14:39 ` Wolfgang Schuster
2013-08-06 15:53 ` Aditya Mahajan
2013-08-06 16:05 ` Wolfgang Schuster
2013-08-06 16:14 ` Aditya Mahajan
2013-08-07 20:59 ` Hans Hagen
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=20130806160946.7526a314@sole \
--to=alan.braslau@cea.fr \
--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).