From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: What's the difference between \dontleavehmode and \leavevmode?
Date: Thu, 18 Aug 2016 18:39:57 +0200 [thread overview]
Message-ID: <8bad0d31-789d-41a9-0c92-2174ed2d56e7@wxs.nl> (raw)
In-Reply-To: <ffee069b-2fed-b8ce-6eb9-7154c2e6bbed@gmail.com>
On 8/18/2016 5:23 PM, Henri Menke wrote:
> Dear list,
>
> could someone please explain what is the difference between \dontleavehmode and \leavevmode?
>
> Internally, I also stumbled upon \quitvmode. Is this a synonym for \leavevmode? It seems to be primitive.
\leavevmode is kind of useless as it can interfere in spacing so we
always used \dontleavehmode in context (a macro) that later was added as
primitive \quitvmode to luatex
You sometimes need \dontleavehmode to make sure you enter hmode (esp
when you start a paragraph with a group or boxed stuff)
(the only two places in context where \leavevmode is used is in rather
plain macros that get overloaded later)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-08-18 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:23 Henri Menke
2016-08-18 15:50 ` Wolfgang Schuster
2016-08-18 16:39 ` Hans Hagen [this message]
2016-08-18 18:14 ` Henri Menke
2016-08-18 21:48 ` 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=8bad0d31-789d-41a9-0c92-2174ed2d56e7@wxs.nl \
--to=pragma@wxs.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).