From: Luis Montgomery via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Luis Montgomery <monty.luis@gmail.com>
Subject: Re: Problems with itemize with several columns
Date: Wed, 23 Feb 2022 11:25:28 -0600 [thread overview]
Message-ID: <CAE+cQBydQpNqM8preKPOWWyuzabQrQpnJkk3sZJqUTx=gwV9Jg@mail.gmail.com> (raw)
In-Reply-To: <20220223095958.65d8f2755e29ae9d2f449cf7@posteo.net>
[-- Attachment #1.1: Type: text/plain, Size: 1616 bytes --]
Try joinedup option in \startitemize.
Space problem?
L. Montgomery
El mié., 23 de febrero de 2022 3:09, Xavier B. via ntg-context <
ntg-context@ntg.nl> escribió:
> Hi,
>
> I try to solve this, but I could not. Can you please help me.
> I make a math problem sheet. In "Exercici 1.2", I put a itemize with three
> columns, but the 'c' exercise jumps to second column. I want that a, b, c
> remains in the first column, d, e, f in the second and g, h, i in the third.
>
> I tried \column command but it's worse.
>
> I attached the source and generated pdf.
>
> My version of context is:
> context --version
> mtx-context | ConTeXt Process Management 1.04
> mtx-context |
> mtx-context | main context file:
> /usr/share/texmf-dist/tex/context/base/mkiv/context.mkiv
> mtx-context | current version: 2021.03.05 19:11
> mtx-context | main context file:
> /usr/share/texmf-dist/tex/context/base/mkxl/context.mkxl
> mtx-context | current version: 2021.03.05 19:11
>
>
> Thanks in advance,
>
> Xavier
>
> PS: Please CCme
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 2590 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
___________________________________________________________________________________
prev parent reply other threads:[~2022-02-23 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:59 Xavier B. via ntg-context
2022-02-23 11:28 ` Xavier B. via ntg-context
2022-02-23 17:52 ` Bruce Horrocks via ntg-context
2022-02-23 21:04 ` Xavier B. via ntg-context
2022-02-23 22:49 ` Luis Montgomery via ntg-context
2022-02-24 22:10 ` Xavier B. via ntg-context
2022-02-24 22:50 ` fv leung via ntg-context
2022-02-25 10:44 ` Bruce Horrocks via ntg-context
[not found] ` <03C9E4F5-AF8C-4815-BBE7-B076C12D2BEE@scorecrow.com>
2022-02-25 12:34 ` Xavier B. via ntg-context
2022-02-25 12:47 ` Xavier B. via ntg-context
2022-02-23 17:25 ` Luis Montgomery via ntg-context [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='CAE+cQBydQpNqM8preKPOWWyuzabQrQpnJkk3sZJqUTx=gwV9Jg@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=monty.luis@gmail.com \
/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).