ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Joel via ntg-context <ntg-context@ntg.nl>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Cc: Joel <uaru99@yahoo.com>
Subject: What is the proper way to define many different list types in a document?
Date: Tue, 25 Jan 2022 00:53:03 +0000 (UTC)	[thread overview]
Message-ID: <253499394.1008080.1643071983973@mail.yahoo.com> (raw)
In-Reply-To: <253499394.1008080.1643071983973.ref@mail.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 1831 bytes --]

I have about several different types of list that reoccur multiple times in my documents. Though I tried to keep things simple, by just defining the type when it appears, strange glitches appear. For instance, I have one that uses the ☞ (pointing hand) logo, and sometimes that randomly appears in the wrong lists, for reasons I cannot understand.

Below is how I'm defining my lists. I have about a dozen more, this is a sample. Is there some more robust and consistent manner in which I should be defining them, so the settings from one type don't spill over into the other types?
--Joel

%prompt

\definesymbol[bighand][{{☞}}]

\define[1]\prompt{%
    \setupitemize[symbol=bighand]
    \startitemize
        {\it #1}
    \stopitemize
}%

\prompt{What did you learn about today?}

%vocabulary

\startcolumns[n=3]\startitemize[n]
\item word1
\item word2
\item word3
\stopitemize\stopcolumns

%nested outline

\startitemize[1]
    \item some text
    \startitemize[2]
        \item some text
        \startitemize[3]
              \item some text
        \stopitemize
    \stopitemize
\stopitemize

%written answer (produces some lines after the question for writing an answer)

\define[1]\writingbox{%
    \dorecurse{#1}{%
        \hairline%
    }
}

\startitemize[n]
\item Which planet is closest to Earth? \writingbox{4}
\item What is the moon made of? \writingbox{4}
\stopitemize

%materials list

\startcolumns[n=3]\startitemize
\item crayons
\item scissors
\item glue
\stopitemize\stopcolumns

%word search clues (should be simple, but strangely this keeps getting the ☞ logo added instead of showing numbers)
\startitemize[n]
\item a type of hat worn
\item a cold season
\stopitemize

[-- Attachment #1.2: Type: text/html, Size: 2510 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
___________________________________________________________________________________

       reply	other threads:[~2022-01-25  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <253499394.1008080.1643071983973.ref@mail.yahoo.com>
2022-01-25  0:53 ` Joel via ntg-context [this message]
2022-01-25  7:15   ` Aditya Mahajan via ntg-context

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=253499394.1008080.1643071983973@mail.yahoo.com \
    --to=ntg-context@ntg.nl \
    --cc=uaru99@yahoo.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).