ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \head: broken?
Date: Sat, 12 Jul 2014 19:32:40 -0400	[thread overview]
Message-ID: <62DAE209-8620-4A58-BA3E-E9856D61D997@umich.edu> (raw)
In-Reply-To: <3ef70d57bc03e78274eaa16e26a04913.squirrel@webmail.xs4all.nl>



> On Jul 12, 2014, at 7:11 PM, "Rob Heusdens" <robheus@xs4all.nl> wrote:
> 
> Hello to all,
> 
> I don't know if it is due to -the weather- or -the Worldchampionships-
> or other but in my Context release [ConTeXt  ver: 2014.07.11 12:20 MKIV
> beta  fmt: 2014.7.12  int: english/english] \head is broken.
> 
> Is that a feature or a bug?
> 
> greetings,
> 
> Rob
> -------
> 
> \head: broken?
> 
> When the \head command is used without a following line of normal text, it
> will result in a context-error.
> 
> MNWE:
> \startitemize[n]
> \head x
> \stopitemize
> 
> MWE:
> \startitemize[n]
> \head x
> anything
> \stopitemize

\head uses \par as a delimiter. So you either need to add an empty line or an explicit \par. 

Aditya
___________________________________________________________________________________
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:[~2014-07-12 23:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 23:11 Rob Heusdens
2014-07-12 23:32 ` Aditya Mahajan [this message]
2014-07-16 11:07 Rob Heusdens
2014-07-16 12:52 ` Wolfgang Schuster
2014-07-18 11:05   ` Rob Heusdens

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=62DAE209-8620-4A58-BA3E-E9856D61D997@umich.edu \
    --to=adityam@umich.edu \
    --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).