From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: setupnarrower and startnarrower
Date: Tue, 6 Aug 2013 18:05:05 +0200 [thread overview]
Message-ID: <3D080671-6860-4927-85CE-4453A1899F58@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1308061151160.910@ybpnyubfg.ybpnyqbznva>
Am 06.08.2013 um 17:53 schrieb Aditya Mahajan <adityam@umich.edu>:
> On Tue, 6 Aug 2013, Wolfgang Schuster wrote:
>
>>
>> Am 06.08.2013 um 16:09 schrieb Alan BRASLAU <alan.braslau@cea.fr>:
>>
>>> 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.
>>
>> Changing the command is simple but I would drop the second
>> argument when you want to change the left/right etc. values
>> because you can say “left=4cm” etc. to get the desired margins.
>
> startnarrower has a weird interface. Ideally, it should just support keywords:
>
> \startnarrower
> [
> leftmargin=...,
> rightmargin=...,
> alternative=(left|right|both),
> spacebefore=....,
> spaceafter=....,
> indenting=....,
> indentnext=....,
> before=....,
> after=....,
> ]
That’s more or less what I use for the “narrow” alternative in the annotation module.
I would prefer such a parameter driven narrower environment myself (do we even need
the left, middle and right option when we can set absolute margins) but keeping the current
interface for backwards compatibility make things a little bit ugly.
Wolfgang
___________________________________________________________________________________
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 16:05 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
2013-08-06 14:39 ` Wolfgang Schuster
2013-08-06 15:53 ` Aditya Mahajan
2013-08-06 16:05 ` Wolfgang Schuster [this message]
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=3D080671-6860-4927-85CE-4453A1899F58@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).