ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer <havdmeer@xs4all.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: \startmode and \ignorespaces
Date: Thu, 13 Oct 2011 17:43:54 +0200	[thread overview]
Message-ID: <A68C3FDE-E982-4CEC-8922-C462408AF7FF@xs4all.nl> (raw)

A little while ago I asked whether \doifmode and friends should have an \ignorespaces at the end. Hans Hagen answered "no" and after some reasoning (probably along the same lines as his) I agree with him. Thus one uses in a quite natural way:
   some text\doifmode{xyz}{ conditional text} following text
doing nothing else than: some text conditional text following text.
With regard to this it is understandable and correct that extra space is taken in the next construct:
   some text \doifmode{xyz}{ conditional text} following text.

But it looks different to me when using the \startmode .. \stopmode pair.
---- some text.
\startmode[xyz]
some conditional text.
\stopmode
further text.

In order to avoid here the extra space one has to code an extra %
---- some text.
\startmode[xyz]%
some conditional text.
\stopmode
further text.

or (not preferred imho):
---- some text.%
\startmode[xyz]

I think this is error prone as it is al too easy to forget the %. The situation here differs from the \doifmode-case. I tend to believe that the fact that the \startmode[] .. \stopmode construct invites one to separate the statements with newlines (whitespace thus). Therefore I would ask if this plea for an \ignorespaces effect at the end of the \startmode[xyz] should be honored.

Hans van der Meer

___________________________________________________________________________________
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:[~2011-10-13 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 15:43 Hans van der Meer [this message]
2011-10-14  8:38 ` Meer, H. van der
2011-10-14  9:26   ` Wolfgang Schuster
2011-10-14 10:09     ` Meer, H. van der
2011-10-14 13:21   ` 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=A68C3FDE-E982-4CEC-8922-C462408AF7FF@xs4all.nl \
    --to=havdmeer@xs4all.nl \
    --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).