From: Philipp Gesang <philipp.gesang@alumni.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reStructuredText module
Date: Thu, 14 Mar 2013 18:17:35 +0100 [thread overview]
Message-ID: <20130314171717.GA16163@phlegethon> (raw)
In-Reply-To: <alpine.LNX.2.02.1303121904480.28048@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 1615 bytes --]
···<date: 2013-03-12, Tuesday>···<from: Aditya Mahajan>···
> On Tue, 12 Mar 2013, Philipp Gesang wrote:
>
> >···<date: 2013-03-12, Tuesday>···<from: Aditya Mahajan>···
> >
> >>On Tue, 12 Mar 2013, Philipp Gesang wrote:
> >>
> >>A better way to handle this is to provide macros \startRSTcontainer
> >>... \stopRSTcontainer and translate the above to
> >
> >I considered adding a generator \defineRSTcontainer with the
> >usual interface (e.g. [command=\framed,frame=on]). This won’t
> >work because the output is supposed to be a self-contained
> >document. The goal is for the output to consist of ordinary
> >Context macros only so it can be imported without loading further
> >code. (I’m undecided regarding the requirement of the “\RST...”
> >prefix, though.)
>
> Personally, I think that it is reasonable to expect the users to
> import a module.
>
> >Honestly, I have no idea. Depending on the style sheet a div can
> >be a float or aligned or have a shaded background. The current
> >approach leaves the implementation to the user.
>
> Another option is to change the generated output to
>
> \start[xyzzy]
> ....
> \stop
>
> When the environment xyzzy exists, this is (supposed to be, see
> below) equivalent to
>
> \startxyzzy
> ....
> \stopxyzzy
>
> otherwise, this is equivalent to
>
> \bgroup
> ....
> \egroup
Now that it’s fixed: Thanks for the pointer. I’ve been using
\start...\stop as a synonym for grouping for ages but never
realized it could take an argument.
Philipp
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-14 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 23:28 Bill Meahan
2013-03-12 0:31 ` Philipp Gesang
2013-03-12 12:28 ` Bill Meahan
2013-03-12 20:23 ` Philipp Gesang
2013-03-12 20:57 ` Aditya Mahajan
2013-03-12 21:42 ` Philipp Gesang
2013-03-12 23:21 ` Aditya Mahajan
2013-03-14 7:32 ` Keith J. Schultz
2013-03-14 16:02 ` Bug in \start (Re: reStructuredText module) Aditya Mahajan
2013-03-14 16:54 ` Hans Hagen
2013-03-14 17:17 ` Philipp Gesang [this message]
2013-03-14 17:40 ` reStructuredText module Marco Patzer
2013-03-14 17:57 ` Hans Hagen
2013-03-14 20:02 ` Aditya Mahajan
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=20130314171717.GA16163@phlegethon \
--to=philipp.gesang@alumni.uni-heidelberg.de \
--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).