From: "Peter Münster" <pmlists@free.fr>
Subject: Re: AW: AW: Re: Line break after unit or \cite command
Date: Mon, 14 Mar 2005 19:10:53 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.58.0503141908560.6447@gaston.free.fr> (raw)
In-Reply-To: <4234A57D.1080809@wxs.nl>
On Sun, 13 Mar 2005, h h extern wrote:
> >>Possible workaround: XXXXXXX~\EVolt\hbox{} wurden...
>
> the \hbox{} will introduce a space
Really? I've tried
\starttext
XXX\hbox{}XXX
\stoptext
But I can't see any space...
Cheers, Peter
--
http://pmrb.free.fr/contact/
prev parent reply other threads:[~2005-03-14 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 15:11 Michael Fuchs
2005-03-10 15:16 ` Adam Lindsay
2005-03-10 15:36 ` AW: " Michael Fuchs
2005-03-10 17:10 ` Patrick Gundlach
2005-03-10 17:47 ` AW: " Michael Fuchs
2005-03-10 19:42 ` Peter Münster
2005-03-10 22:15 ` AW: " Michael Fuchs
2005-03-11 8:41 ` Patrick Gundlach
2005-03-11 10:34 ` AW: " Michael Fuchs
2005-03-11 18:24 ` Peter Münster
2005-03-11 19:15 ` AW: " Michael Fuchs
2005-03-13 17:48 ` Patrick Gundlach
2005-03-13 20:41 ` AW: AW: " h h extern
2005-03-14 9:59 ` Patrick Gundlach
2005-03-14 18:10 ` Peter Münster [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=Pine.LNX.4.58.0503141908560.6447@gaston.free.fr \
--to=pmlists@free.fr \
--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).