From: Pavneet Arora <pavneet_arora@waroc.com>
To: Sietse Brouwer <sbbrouwer@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: simpleslides help needed
Date: Tue, 24 Jul 2012 08:19:15 -0400 [thread overview]
Message-ID: <500E92C3.1010207@waroc.com> (raw)
In-Reply-To: <CAF=dkzwbU3jt2tG64BZOFjvkt6RF=mttbTw4sJgB2H6tY=W8kQ@mail.gmail.com>
Yes, indeed the information is there. What makes the wiki sometime impenetrable
is that doing a search, even a Google search, with keyword based or topic based
queries rather than command based queries leads to varying results. You know
what you want to do; you just don't know which commands will lead you to the result.
Also just to clarify, as is my habit, I did search the wiki, and in this case I
had even looked repeatedly at the hints. I just didn't catch the distinction in
my own coding.
I guess the trick is to know what commands one should hone in on ;).
Regards.
On 12-07-24 07:44 AM, Sietse Brouwer wrote:
> On Tue, Jul 24, 2012 at 12:51 PM, Pavneet Arora <pavneet_arora@waroc.com> wrote:
>> Now, I don't know whether there should be a difference in behaviour,
>> [between \quotation and \startquotation], but there definitely is.
>
> This is deliberate: \quotation is for inline quotations, while
> \startquotation is for block quotations. Compare \math and \startmath.
>
> I completely understand that people have gotten into a habit of not
> looking up commands on the wiki; there was So Much Blankness on the
> command pages, so why bother? By now, though, we have reached the
> stage that looking up a basic command, at least, has a good chance of
> success. So perhaps people could slowly start looking at the wiki
> command reference again? The answer to quotation/startquotation, at
> least, was sitting right there. :-)
>
> http://wiki.contextgarden.net/Command/startquotation
> http://wiki.contextgarden.net/Command/quotation
>
> Cheers,
>
> Sietse
> Sietse Brouwer
>
--
-----
- Pavneet Arora
Waroc Fine Audio + Custom Home Cinema
www.waroc.com 416.937.WAROC (9276)
___________________________________________________________________________________
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:[~2012-07-24 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 0:41 Pavneet Arora
2012-07-18 3:33 ` Wolfgang Schuster
2012-07-23 21:21 ` Pavneet Arora
2012-07-24 4:22 ` Wolfgang Schuster
2012-07-24 10:51 ` Pavneet Arora
2012-07-24 11:44 ` Sietse Brouwer
2012-07-24 12:19 ` Pavneet Arora [this message]
2012-07-18 7:42 ` Hans Hagen
2012-07-18 11:23 ` Pavneet Arora
2012-07-18 12:13 ` Hans Hagen
2012-07-18 15:09 ` Aditya Mahajan
2012-07-18 15:18 ` Aditya Mahajan
[not found] ` <50080097.4030107@waroc.com>
2012-07-21 18:06 ` 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=500E92C3.1010207@waroc.com \
--to=pavneet_arora@waroc.com \
--cc=ntg-context@ntg.nl \
--cc=sbbrouwer@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).