ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: \high and \low trouble
Date: Wed, 24 May 2000 10:54:35 +0200	[thread overview]
Message-ID: <3.0.6.32.20000524105435.0083a100@pop.wxs.nl> (raw)
In-Reply-To: <200005240647.HAA20160@holly.orc.soton.ac.uk>

At 08:10 AM 5/24/2000 GMT, Peter Jander wrote:

>I  noticed that the \high{} and \low{} commands produce some  strange
>results when they are typeset at the beginning on a line.
>For example:
>
>\starttext
>ok \low{1}
>\low{2}not good
>
>\hairline\high{3}G
>\stoptext
>
>Here the 1 will be ok, whereas there seems to be  a \crlf inserted  after
>the 2 and 3.
>
>Does this happen to anyone else or is it just my installation of  Context?
>I am running ver 2000.3.30 fmt 2000.5.9 english.

This is related to the way tex enters hmode. One way out is prefixing with
\noindent or \indent or (dangerous) \leavevmode. Long ago it has taken me
quite some time to find out that \dontleavehmode is the most acceptable,
since it still obeys indentation, and does not spoil whitespace. 

For the moment, add this to your local cont-new.tex file: 

\let\normalhigh\high \def\high{\dontleavehmode\normalhigh}
\let\normalhigh\low  \def\low {\dontleavehmode\normallow }
\let\normalhigh\lohi \def\lohi{\dontleavehmode\normallohi}

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


      reply	other threads:[~2000-05-24  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-24  8:10 Peter Jander
2000-05-24  8:54 ` Hans Hagen [this message]

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=3.0.6.32.20000524105435.0083a100@pop.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).