From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New Member Introductory Rant
Date: Mon, 31 Mar 2008 22:23:58 +0200 [thread overview]
Message-ID: <9953FA9D-142E-4D03-AC72-40C848D0CBFC@fiee.net> (raw)
In-Reply-To: <alpine.DEB.1.00.0803311128430.10612@nqv-yncgbc>
Am 2008-03-31 um 17:33 schrieb Aditya Mahajan:
>>
>> "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.
In case someone overread this:
"You can search the source tree on contextgarden"
http://source.contextgarden.net/
And besides the wiki pages, a lot of command documentation is in
texshow-web:
http://texshow.contextgarden.net/
(Even if unfortunately some groups of commands are missing completely.)
>> 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.
MacOS X hides most of its UNIX stuff from a normal user.
But you can just e.g. "open /usr/" in Terminal and continue to browse
in Finder.
>>
>> 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.
And I guess the ConTeXt sources are the only place where the Dodo
survived.
(At least every Dodo would feel at home between all those dodododos.)
;-)
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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 20:23 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
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 [this message]
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=9953FA9D-142E-4D03-AC72-40C848D0CBFC@fiee.net \
--to=hraban@fiee.net \
--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).