From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: fancybreak fails in LMTX
Date: Sat, 7 Nov 2020 11:13:00 -0500 [thread overview]
Message-ID: <5784c453-8e73-32c3-5973-7d0497c6a1d1@panix.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 619 bytes --]
Hello all,
The following example produces the expected output in MkIV, but fails in
LMTX (both dated 2020-11-07). The modules directory was copied into the
LMTX tree from the MkIV tree, and the log indicates that the module is
loaded. It gives no other clues. The output has a blank line where the
break should be, as shown in the included snips.
\usemodule [fancybreak]
\definesymbol [asterisms][*\qquad fancybreak\qquad *]
\setupfancybreak[indentnext=no,symbol=asterisms]
\starttext
Before
\fancybreak
After
\stoptext
MkIV output:
LMTX output:
--
Rik
[-- Attachment #1.2.1: Type: text/html, Size: 1179 bytes --]
[-- Attachment #1.2.2: dokakjbipigijgdp.png --]
[-- Type: image/png, Size: 3371 bytes --]
[-- Attachment #1.2.3: ghfjfflmmajdddfm.png --]
[-- Type: image/png, Size: 1923 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-11-07 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 16:13 Rik Kabel [this message]
2020-11-07 16:51 ` Wolfgang Schuster
2020-11-07 17:12 ` 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=5784c453-8e73-32c3-5973-7d0497c6a1d1@panix.com \
--to=context@rik.users.panix.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).