ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Product-component structure
Date: Sat, 25 Jun 2016 19:13:22 +0200	[thread overview]
Message-ID: <576EBBB2.8000508@gmail.com> (raw)
In-Reply-To: <24241387-a8a7-0b45-62a7-574bb31cb419@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 433 bytes --]

> Hans Hagen <mailto:pragma@wxs.nl>
> 25. Juni 2016 um 11:56
>
>
> i always use one main environment (that can include others) and 
> putting an \environment on top of a component is then not much 
> overhead (compared to getting the content done)
The problem with puttins \environment before \startcomponents is
that you can’t check for the *component mode which is enabled
after the environment was loaded.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1431 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-06-25 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 19:19 Aditya Mahajan
2016-06-24 22:20 ` Hans Hagen
2016-06-25  6:25 ` Wolfgang Schuster
2016-06-25  8:42   ` Aditya Mahajan
2016-06-25  9:56     ` Hans Hagen
2016-06-25 16:37       ` Aditya Mahajan
2016-06-25 17:10         ` Wolfgang Schuster
2016-06-25 17:24           ` Aditya Mahajan
2016-06-25 17:13       ` Wolfgang Schuster [this message]
2016-06-25 17:25         ` Aditya Mahajan
2016-07-11 11:01           ` Procházka Lukáš Ing.
2016-07-11 14:42             ` Alan BRASLAU
2016-06-26  9:34         ` 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=576EBBB2.8000508@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).