From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: What do \start and \stop mean?
Date: Mon, 30 Sep 2013 18:32:46 +0200 [thread overview]
Message-ID: <CAG5iGsARazwupOoaUEeAv3V+JfyseKijBpNVb3D=YLhbyYAahg@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsAThFhCArjEfaA4DWY7QThnK+iAR2PFDHaXBzMVvkcm3g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]
On Mon, Sep 30, 2013 at 6:00 PM, luigi scarso <luigi.scarso@gmail.com>wrote:
>
>
>
> On Mon, Sep 30, 2013 at 5:38 PM, Lars Huttar <lars_huttar@sil.org> wrote:
>
>> I found \start and \stop referenced in the context reference manual
>> (e.g. section 5.5).
>> While \startXYZ - \stopXYZ pairs are discussed earlier, I can't find any
>> place that \start and \stop (with no suffix) are described.
>> They seem to be used like \bgroup and \egroup. Is that right?
>> They are defined in core-sys.mkiv, but I can't figure out from there
>> what they actually do.
>>
>> I'll contribute documentation for them if someone can tell me what they
>> mean.
>>
>> Thanks,
>> Lars
>>
>
>
>
>
> core-sys.mkiv :
>
>
> \unexpanded\def\start
> {\dosingleempty\syst_start}
>
> \def\syst_start
> {\bgroup
> \iffirstargument
> \expandafter\syst_start_yes
> \else
> \expandafter\syst_start_nop
> \fi}
>
> \def\syst_start_yes[#1]%
> {\edef\m_syst_start_stop{#1}%
> \ifx\m_syst_start_stop\empty
> \let\syst_stop_indeed\donothing
> \else\ifcsname\e!start\m_syst_start_stop\endcsname
>
> \expandafter\let\expandafter\syst_stop_indeed\csname\e!stop\m_syst_start_stop\endcsname
>
> \csname\e!start\m_syst_start_stop\expandafter\expandafter\expandafter\endcsname
> \else
> \let\syst_stop_indeed\donothing
> \fi\fi}
>
> \def\syst_start_nop[#1]%
> {\let\syst_stop_indeed\donothing}
>
> \unexpanded\def\stop
> {\syst_stop_indeed
> \egroup}
>
>
> (it should be \let\donothing\empty)
>
> sorry, hit return too early.
\start <...> \stop without argument is
\bgroup % from\def\syst_start
\expandafter\syst_start_nop
\syst_start_nop is
{\let\syst_stop_indeed\donothing}
and \stop is hence
\syst_stop_indeed
\egroup
i.e.
\donothing
\egroup
are like \bgroup <...> \egroup
It seems that there are no examples of \start[]<..>\stop .
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 3057 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-09-30 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 15:38 Lars Huttar
2013-09-30 15:44 ` Aditya Mahajan
2013-09-30 17:53 ` Lars Huttar
2013-09-30 16:00 ` luigi scarso
2013-09-30 16:32 ` luigi scarso [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='CAG5iGsARazwupOoaUEeAv3V+JfyseKijBpNVb3D=YLhbyYAahg@mail.gmail.com' \
--to=luigi.scarso@gmail.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).