From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Thu, 13 Oct 2016 02:23:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.OSX.2.02.1610130222190.28268@nqv-znpobbx> (raw)
In-Reply-To: <DE6A554D-E7C7-42A7-A3F6-ABE48C780D5E@fiee.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 787 bytes --]
On Thu, 13 Oct 2016, Henning Hraban Ramm wrote:
> Am 2016-10-12 um 23:27 schrieb Jonas Baggett <jonas17b@gmail.com>:
>
>>> There are ConTeXt threads on tex.stackexchange.com
>> You are confusing Stack Overflow and Stack Exchange ;-). Actually I didn't find the ConTeXt tag there : http://stackoverflow.com/tags.
>
> No, I’m not confusing them. They’re the same company, share accounts,
> reputation etc. All TeX related questions belong on
> tex.stackexchange.com, not on stackoverflow, so there *shouldn’t* exist
> any tex, latex, context, luatex etc. tags on stackoverflow. But look
> here: http://tex.stackexchange.com/tags
But the stackexchange documentation feature only works for languages that
have tags on stackoverflow, not on stackexchange.
Aditya
[-- Attachment #2: Type: text/plain, Size: 489 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://context.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-10-13 9:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 11:18 Jonas Baggett
2016-10-09 13:49 ` Yi Qingliang
2016-10-10 5:21 ` Jonas Baggett
2016-10-09 19:31 ` Henri Menke
2016-10-09 22:49 ` Jonas Baggett
2016-10-10 7:35 ` Hans Hagen
2016-10-11 21:36 ` Jonas Baggett
2016-10-09 20:51 ` Wolfgang Schuster
2016-10-10 5:43 ` Jonas Baggett
2016-10-10 7:24 ` Hans Hagen
2016-10-11 21:05 ` Jonas Baggett
2016-10-12 11:30 ` Jonas Baggett
2016-10-12 15:29 ` Yi Qingliang
2016-10-12 15:33 ` Mica Semrick
2016-10-12 17:32 ` Jonas Baggett
2016-10-12 17:45 ` Bomber K.
2016-10-12 17:55 ` Bomber K.
2016-10-10 7:57 ` Thomas A. Schmitz
2016-10-10 17:04 ` Jean-Pierre Delange
2016-10-10 17:34 ` Hans Hagen
2016-10-10 21:41 ` Henning Hraban Ramm
2016-10-11 5:20 ` Jean-Pierre Delange
2016-10-12 21:18 ` Jonas Baggett
2016-10-12 10:17 ` Jonas Baggett
2016-10-10 5:32 ` Aditya Mahajan
2016-10-10 5:43 ` Aditya Mahajan
2016-10-11 20:26 ` Jonas Baggett
2016-10-11 20:40 ` Henning Hraban Ramm
2016-10-12 21:27 ` Jonas Baggett
2016-10-13 8:15 ` Henning Hraban Ramm
2016-10-13 9:23 ` Aditya Mahajan [this message]
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.OSX.2.02.1610130222190.28268@nqv-znpobbx \
--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).