ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: next space
Date: Mon, 29 Nov 2010 10:29:13 +0100	[thread overview]
Message-ID: <5CC43937-9006-4D18-9E98-FE320C79FF4D@st.estfiles.de> (raw)

Hi,

please have a look at this:


\definestartstop[redimportant][before={\startcolor[red]\bf\penalty10000\hskip\zeropoint},after={\/\stopcolor}]

\starttext

This is normal, but this\startredimportant one\startfootnote at least \stopfootnote is bold\stopredimportant style.

This is normal, but this\startredimportant one\startfootnote at least \stopfootnote is bold\stopredimportant.


This is normal, but this\startredimportant{} one\startfootnote at least \stopfootnote{} is bold\stopredimportant{} style.

This is normal, but this\startredimportant{} one\startfootnote at least \stopfootnote{} is bold\stopredimportant.

\stoptext


Is the missing \autoinsertnextspace back in the meantime? 
Or does someone has a good substitute ... other then {} braces?

Steffen
___________________________________________________________________________________
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:[~2010-11-29  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29  9:29 Steffen Wolfrum [this message]
2010-11-29 13:39 ` Wolfgang Schuster
2010-12-03 16:21   ` next space (problematic example!) Steffen Wolfrum
2010-12-04 14:12     ` Steffen Wolfrum
2010-12-04 14:56     ` Wolfgang Schuster
2010-12-04 16:16       ` Steffen Wolfrum

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=5CC43937-9006-4D18-9E98-FE320C79FF4D@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).