ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Table of contents, alternative d
Date: 29 Nov 2004 19:00:10 +0100	[thread overview]
Message-ID: <m2pt1wwn6d.fsf@levana.de> (raw)
In-Reply-To: <BAY23-F26F97B978109583ABA9C1FFBBD0@phx.gbl> (Dirar BOUGATEF's message of "Mon, 29 Nov 2004 17:10:05 +0000")

"Dirar BOUGATEF" <chabah5@hotmail.com> writes:

>> From the whole batch of answers i have received i could assume that
>> there is 
> no solution to this problem.

You could also conclude from the lack of answers that nobody feels to
make a working example of what you wanted to achieve.

You (and others, of course) can increase the chance of someone looking
into your problem by creating a complete and minimal example of what
you tried. It is of course not a guarantee to an answer, but let's say
the least thing that a person seeking help should do.

It is absolutely no use to publish only a few lines in case of a
problem. What the problem-solvers want is code that they can cut and
paste to their editor and run it. Then they look at the output and
then at the code and sometimes they know where the problem is. One
thing that a problem-solver will not want to do is fill in the
missing parts of posted code like in a high school exam.

I don't try to be smart here, it is just the fact how the community
works.

Patrick
-- 
ConTeXt wiki: http://contextgarden.net

  parent reply	other threads:[~2004-11-29 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-28 15:46 Dirar BOUGATEF
2004-11-29 17:10 ` Dirar BOUGATEF
2004-11-29 17:25   ` Hans Hagen
2004-11-29 21:02     ` Dirar BOUGATEF
2004-11-30  0:53       ` Patrick Gundlach
2004-11-30  8:56         ` Dirar BOUGATEF
2004-11-30  9:56           ` Hans Hagen
2004-11-30 10:59             ` Dirar BOUGATEF
2004-11-29 18:00   ` Patrick Gundlach [this message]
2004-11-29 19:35 ` Willi Egger

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=m2pt1wwn6d.fsf@levana.de \
    --to=patrick@gundla.ch \
    --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).