From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
mf <massifr@fastwebnet.it>
Subject: Re: strange behavior with \groupedcommand in recent versions of LMTX
Date: Tue, 1 Sep 2020 19:22:02 +0200 [thread overview]
Message-ID: <52d0b918-3405-83f9-c186-ba6612bd5486@xs4all.nl> (raw)
In-Reply-To: <a71113df-56aa-f476-0125-a3ae9314be0d@fastwebnet.it>
On 9/1/2020 5:47 PM, mf wrote:
> \unexpanded\def\groupedwordorparagraphright{\dosingleempty\dogroupedwordorparagraphright}
>
> \def\dogroupedwordorparagraphright[#1]{\groupedcommand{\setbox\scratchbox\hbox\bgroup}
>
> {\egroup\ifdim\wd\scratchbox < \hsize
> \wordright{\unhbox\scratchbox}
> \else
> \par\penalty10000
> \startalignment[flushright]\unhbox\scratchbox\stopalignment
> \fi}}
>
> \unexpanded\def\wordorparagraphright#1{%
> \setbox\scratchbox\hbox{#1}
> \ifdim\wd\scratchbox < \hsize
> \wordright{#1}
> \else
> \par\penalty10000
> \startalignment[flushright]\unhbox\scratchbox\stopalignment
> \fi}
>
> \starttext
> \type{\wordorparagraphright} should use \type{\wordright} if its
> argument
> is narrower than \type{\hsize}, or make a right-aligned paragraph
> with it
> when it's wider.
>
> Below, \type{\wordorparagraphright} is tested with a short text, that
> has enough room on the same line.
> \blank
>
> Reference:
>
> \input ward\wordright{same line, right}
>
> \blank
>
> Implementation as a grouped command (it doesn't work):
>
> \input ward\groupedwordorparagraphright{same line, right}
>
> \blank
>
> Normal implementation, not as a grouped command (it works):
>
> \input ward\wordorparagraphright{same line, right}
> \stoptext
> ----------------------------------------------------
>
> Unfortunately the grouped version is the one I need, because it's used
> in a register, and it would give an error if not defined through
> \groupedcommand:
>
> \setupregister[myregister]
> [pageleft=\wordorparagraphright\bgroup,pageright=\egroup]
fortunately there is a solution that takes less code:
\unexpanded\def\whatever
{\dosingleempty\dowhatever}
\def\dowhatever[#1]%
{\dowithnextbox
{\ifdim\wd\nextbox<\hsize
\wordright{\box\nextbox}%
\par
\else
\par
\penalty10000
\startalignment[flushright]\unhbox\nextbox\stopalignment
\fi}\hbox}
\starttext
\input ward \whatever{same line, right}
\blank
\input ward \whatever{\input tufte }
\stoptext
-----------------------------------------------------------------
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-09-01 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 15:47 mf
2020-09-01 17:22 ` Hans Hagen [this message]
2020-09-02 9:10 ` mf
2020-09-02 11:24 ` 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=52d0b918-3405-83f9-c186-ba6612bd5486@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=massifr@fastwebnet.it \
--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).