From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New Member Introductory Rant
Date: Mon, 31 Mar 2008 11:33:16 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0803311128430.10612@nqv-yncgbc> (raw)
In-Reply-To: <E09EB236-E723-49AA-B9CB-B926DD270E64@di.unito.it>
On Mon, 31 Mar 2008, Andrea Valle wrote:
>>
>> By reading the source :)
>> Joking of course ... but not entirely.
>>
>
>
>
> Yes, that's an important point. Many times the options I'm searching for are
> not documented: so, or I'm able to find an example in wiki/mailing list or
> probably it would be easy to take a look to the sources, I guess.
> I know it's far from being polite, but really I'd like to have a
> "How-to-find-your-way-thru-the-source Tutorial for total newbie".
The first thing that you need to know is the file where a particular
command is defined. You can search the source tree on contextgarden; or
grep the files in your computer. After a while you will remember which
file defines a particular command.
> On my mac,
> they are hidden: so, first step, change your visualization preferences thru a
> googled script form Terminal.
Sorry, I have no idea of how things work on a Mac, but it seems strange to
hide the entire tex tree.
> Second, the (in)famous tex tree structure is
> far from being clear for me.
Almost all of ConTeXt files are in $TEXMF/tex/context/base (fonts, are of
course a different issue)
> Third, and most important, how to extract infos
> from sources?
This is the easiest. Most of ConTeXt commands are written in a consistent
manner. Hans uses verbose variable names, which makes it easy to "read"
the code. Also in most cases the source files have lot of comments.
Aditya
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-03-31 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 8:01 Corin Royal Drummond
2008-03-30 14:09 ` Idris Samawi Hamid
2008-03-30 14:50 ` Mojca Miklavec
2008-03-30 21:03 ` David
2008-03-31 8:08 ` proverb (was: New Member Introductory Rant) Marcin Borkowski
2008-03-30 22:56 ` New Member Introductory Rant Andrea Valle
2008-03-31 15:33 ` Aditya Mahajan [this message]
2008-03-31 15:46 ` Andrea Valle
2008-04-01 0:29 ` Mojca Miklavec
2008-04-01 7:24 ` Andrea Valle
2008-04-01 10:17 ` Hans Hagen
2008-03-31 20:23 ` Henning Hraban Ramm
2008-03-30 18:07 Corin Royal Drummond
2008-03-30 19:22 ` Marcin Borkowski
2008-03-31 15:40 ` 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=alpine.DEB.1.00.0803311128430.10612@nqv-yncgbc \
--to=adityam@umich.edu \
--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).