ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Keith J. Schultz" <keithjschultz@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Subjects on this list - general request
Date: Wed, 20 Mar 2013 19:46:33 +0100	[thread overview]
Message-ID: <805B64A5-56EA-49B7-B818-69A0A8879B2D@web.de> (raw)
In-Reply-To: <85341D72-ADBE-4A98-80EE-147A4F9A2EA1@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1816 bytes --]

Hi Robert,

I see no advantage in your suggestion. just search the subject.

As for the [***Spam***] that is inroduce by mail servers. A user should maybe remove
it to avoid it. But a nuisance, yes, a problem no.

regards
	Keith.

Am 20.03.2013 um 16:12 schrieb Robert Blackstone <blackstone.robert@gmail.com>:

> Dear all,
> Considering all complaints about the difficulties to find, in the Garden, or in the NTG mail archive,  answers to specific problems, wouldn't it be a good idea to ask everybody to clearly state the subject of their message, preferably starting with the most important keyword, and in particular to avoid (no subject) or [***SPAM***], and similar things as subjects.
> Also, if you forgive me,  subjects like "upto current" or "Bug in \column" are not really helpful when on tries to search in the archive for a solution to a specific problem. In the last-mentioned example, wouldn't "\column, Bug in - " or even "\column, Bug in \column" be better? 
> More specific subject titles in the mails might save some of us hours of unfruitful searching and lots of teeth grinding.
> This is probably not the first request on this topic but, if so, I thought it would do no harm to repeat it.
> 
> Thanks in advance.
> 
> Best regards,
> 
> Robert Blackstone
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 3874 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2013-03-20 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 15:12 Robert Blackstone
2013-03-20 16:32 ` Mica Semrick
2013-03-20 18:46 ` Keith J. Schultz [this message]
     [not found] <mailman.81.1363805204.2084.ntg-context@ntg.nl>
2013-03-21 11:30 ` Robert Blackstone

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=805B64A5-56EA-49B7-B818-69A0A8879B2D@web.de \
    --to=keithjschultz@web.de \
    --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).