From: Mikael Sundqvist <mickep@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Line break after a Metapost picture at start of paragraph
Date: Fri, 29 Nov 2024 11:00:15 +0100 [thread overview]
Message-ID: <CAHy-LL_1ewjkeUGFf8aVrs1=adXoCTxY=vJtvQpUfFmoHjdPdg@mail.gmail.com> (raw)
In-Reply-To: <CALOhoe+m=iyUOy3+QC5n_Ko7gkPjfrgHtxtrTkm5w4V0+4g6tw@mail.gmail.com>
Hi,
If you add \dontleavehmode before the MP graphic that starts the line,
you will be fine. There is something to read about it here:
https://wiki.contextgarden.net/Unexpected_behavior
/Mikael
On Fri, Nov 29, 2024 at 10:11 AM Florent Michel <florent.m42@gmail.com> wrote:
>
> Hi,
>
> I have just encountered a (to me) slightly surprising behaviour in ConTeXt LMTX 2024.10.31: there seems to be an automatic line break after a Metapost picture if it is at the start of a paragraph. Here is a simple example showing this behaviour:
>
> ------------------------------------------------------------------
> \starttext
> % Two different lines
> \startMPcode
> fill fullcircle scaled 10pt;
> \stopMPcode
> text
>
> % Single line
> text
> \startMPcode
> fill fullcircle scaled 10pt;
> \stopMPcode
> \stoptext
> ------------------------------------------------------------------
>
> I'm not sure whether this is a bug or intended behaviour, though - maybe this is the expected output for users more familiar with TeX and/or ConTeXt than I am. I would have two question, though:
>
> 1) Is there a canonical way to get the second behaviour (multiple Metapost pictures and text on the same line) if the first Metapost picture starts the paragraph? One workaround seems to be to add \noindent (plus \hskip if I do want indentation) before the first Metapost picture, but maybe there is a better way.
>
> 2) If this is intended behaviour, is there already a description of it in the Wiki or would it make sense for me to add it?
>
> Cheers,
> Florent
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
> webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
> archive : https://github.com/contextgarden/context
> wiki : https://wiki.contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-11-29 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 9:02 [NTG-context] " Florent Michel
2024-11-29 10:00 ` Mikael Sundqvist [this message]
2024-11-29 10:53 ` [NTG-context] " Florent Michel
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='CAHy-LL_1ewjkeUGFf8aVrs1=adXoCTxY=vJtvQpUfFmoHjdPdg@mail.gmail.com' \
--to=mickep@gmail.com \
--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).