ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: ecashin@coe.uga.edu (Ed L. Cashin)
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: text vs command at end of itemize
Date: 12 Sep 1999 22:23:08 -0400	[thread overview]
Message-ID: <m3n1ura6sz.fsf@kali.coe.uga.edu> (raw)
In-Reply-To: <37DADAD4.3ECA10F3@wxs.nl>

Hans Hagen <pragma@wxs.nl> writes:

> "Ed L. Cashin" wrote:
> 
> > I've noticed a strange effect at the end of an itemized list.
> > Beginning the line that follows the list with a command seems to
> > conflict with the "after" option:
> 
> > \stopitemize
> > 
> > \in{Item}[nomotion2] is a bit hard to accomplish.
> 
> This is not so much with the after option, but more a side effect of
> indentation, everypar, etc etc. and the moment when tex decides to enter
> horizontal mode. 
> 
> Some solutions are: \indent \noindent \strut \leavevmode
>
> The problem is that all of hese have unwanted side effects,
> especially \leavevmode can badly interfere with vertical spacing
> (which is one reason why so many tex documents have sub optimal
> vertical spacing.

I've been getting by with "\null".  Would null have those side
effects?  I suppose so.

> You can precede the \in by \dontleavehmode. This is a rather funny
> macro: {\ifmmode\else$ $\fi} with not so many side effects. 

That *is* pretty strange. :)  "Don't do anything if we're in math
mode.  If we're not in math mode, do nothing in math mode.  Is that
the gist of it?

-- 
--Ed Cashin							
  ecashin@coe.uga.edu


  reply	other threads:[~1999-09-13  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-11  1:49 Ed L. Cashin
1999-09-11 22:42 ` Hans Hagen
1999-09-13  2:23   ` Ed L. Cashin [this message]
1999-09-13  7:36     ` 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=m3n1ura6sz.fsf@kali.coe.uga.edu \
    --to=ecashin@coe.uga.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).