ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \doifmode and friends
Date: Tue, 4 Oct 2011 20:44:25 +0200	[thread overview]
Message-ID: <E61C8BFF-6D6A-4E16-B771-3E3D9E9086A7@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.02.1110041437070.24368@nqv-gnoyrg>


Am 04.10.2011 um 20:37 schrieb Aditya Mahajan:

> On Tue, 4 Oct 2011, Meer, H. van der wrote:
> 
>> I find that "abc \doifmode{mode}{text} more text" can introduce extra whitespace. I conclude therefore that there is no \ignorespaces at work here. As a consequence the \doifmode does not completely disappear if mode is not satisfied.
>> Is this intentional or should this behaviour be changed?
> 
> Can you provide a minimal example. I don't get any extra spaces
> 
> \enablemode[test]
> \starttext
> A\doifmode{test}{B}C
> 
> A\doifmode{notest}{B}C
> \stoptext


There is a unwanted space in the second paragraph.

\enablemode[test]

\starttext

A \doifmode{test}{B} C

A \doifmode{notest}{B} C

\stoptext

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
___________________________________________________________________________________


  reply	other threads:[~2011-10-04 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 18:19 Meer, H. van der
2011-10-04 18:32 ` Wolfgang Schuster
2011-10-04 18:37 ` Aditya Mahajan
2011-10-04 18:44   ` Wolfgang Schuster [this message]
2011-10-04 21:17     ` Meer, H. van der
2011-10-04 21:42       ` Wolfgang Schuster
2011-10-04 22:19       ` 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=E61C8BFF-6D6A-4E16-B771-3E3D9E9086A7@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).