From: Mike Cooper <mike@murchisondrillingschools.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: use parentheses in itemize
Date: Mon, 8 Jun 2020 19:31:09 +0000 [thread overview]
Message-ID: <SN6PR11MB2576285D150A0E3198CC50FCBD850@SN6PR11MB2576.namprd11.prod.outlook.com> (raw)
In-Reply-To: <AB844DE1-E018-445D-BB25-86C455B072BC@gmail.com>
Thanks David!
I also realized (with some help! Thanks John!) that I was completely overlooking the answers to my original question, as well as "what is stopper?" on the wiki.
-----Original Message-----
From: ntg-context [mailto:ntg-context-bounces@ntg.nl] On Behalf Of David Rogers
Sent: Friday, June 05, 2020 9:24 PM
To: mailing list for ConTeXt users
Subject: Re: [NTG-context] use parentheses in itemize
On June 3, 2020 7:01:57 a.m. PDT, Mike Cooper <mike@murchisondrillingschools.com> wrote:
>The logic in that approach is obvious. Thanks Aditya.
>
>But then, what is "stopper"? What's it for? What happens if you just
>leave it out?
When you leave it out, it's simply not used. In broad general terms, ConTeXt is set up to allow you to just ignore any features you don't need.
Stopper is for when you want
(1.)
(2.)
or
(1:)
(2:)
or any other thing that suits you, to be placed after each number. "Nothing" is certainly one of the legitimate and common choices for this purpose, and Aditya took the step of actually defining it as "nothing" by typing "stopper=". (After the equals sign comes... you guessed it.) :)
Doing such a "define it to be nothing" step would be especially helpful/important if you DID have it defined as something for a different part of your document, and then wanted to change styles part way through.
--
David
___________________________________________________________________________________
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
___________________________________________________________________________________
___________________________________________________________________________________
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-06-08 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 21:56 Mike Cooper
2020-06-02 22:23 ` Tomas Hala
2020-06-02 22:32 ` Mike Cooper
2020-06-03 4:14 ` Aditya Mahajan
2020-06-03 14:01 ` Mike Cooper
2020-06-06 3:24 ` David Rogers
2020-06-08 19:31 ` Mike Cooper [this message]
[not found] <mailman.599.1591135005.9468.ntg-context@ntg.nl>
2020-06-02 22:51 ` jkitz
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=SN6PR11MB2576285D150A0E3198CC50FCBD850@SN6PR11MB2576.namprd11.prod.outlook.com \
--to=mike@murchisondrillingschools.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).