From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: should the mail list be splitted resp. sub-tagged ?
Date: Wed, 05 Jan 2011 10:13:25 +0100 [thread overview]
Message-ID: <87k4ijbtmy.fsf@Rainer.invalid> (raw)
In-Reply-To: pkn8vz0tqsa.fsf@this.is.really.invalid
Robert Pluim <rpluim@gmail.com> writes:
> Triage is for *computers* to do, they're much better at it than humans.
Then let your MUA strip the tag off for you and live a happier life.
> Also, those markers in the subject are obnoxious and *really* annoying,
> and take up valuable screen space. Please don't clutter up the org-mode
> emails for zero benefit.
They are very valuable when you need to quickly check things from a
computer where you don't have set up your filtering for instance. Plus
they are indispensable for everyone who decides to not filter mail into
folders or anything like that. They don't force you to not filter, so
why should you force them to change their workflow?
> org-mode list email has a List-Id header, the list software has already
> taken care of it for you. I fail to see how much can go wrong with
> filtering on that, configure it once and you're done. (or read the list
> via gmane, all nicely split out for you).
This header is there for software to see, not for humans. There is
multiple redundancy in both the headers and the tagging of the subject
line and this is what makes things resilient. And yes, I read the list
via Gmane/GNUS, but that doesn't mean everyone has to do it the same
way.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2011-01-05 9:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 8:52 should the mail list be splitted resp. sub-tagged ? Torsten Wagner
2010-12-17 12:15 ` Andrew J. Korty
2010-12-17 14:00 ` Giovanni Ridolfi
2010-12-17 15:56 ` Nick Dokos
2010-12-17 17:28 ` Samuel Wales
2010-12-17 15:40 ` Nick Dokos
2010-12-17 18:21 ` William Gardella
2010-12-17 20:33 ` William Gardella
2010-12-17 21:16 ` Eric S Fraga
2010-12-18 12:09 ` Torsten Wagner
2011-01-04 15:19 ` Bastien
2011-01-04 17:39 ` Štěpán Němec
2011-01-04 18:12 ` Bastien
2011-01-04 18:31 ` Jeff Horn
2011-01-04 19:49 ` Štěpán Němec
2011-01-04 20:43 ` Nick Dokos
2011-01-04 18:52 ` Nick Dokos
2011-01-04 19:25 ` Robert Pluim
[not found] ` <rpluim@gmail.com>
2011-01-04 20:02 ` Nick Dokos
2011-01-05 8:15 ` Robert Pluim
2011-05-05 14:05 ` Applying style to a paragraph for HTML export Nick Dokos
2011-05-05 14:35 ` Jambunathan K
2011-01-05 9:13 ` Achim Gratz [this message]
2011-01-05 9:56 ` should the mail list be splitted resp. sub-tagged ? Robert Pluim
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 9:37 Applying style to a paragraph for HTML export Robert Pluim
2011-05-05 12:05 ` Jambunathan K
2011-05-05 12:33 ` Robert Pluim
2011-05-05 12:45 ` Jambunathan K
2011-05-05 13:16 ` Robert Pluim
2011-05-05 12:51 ` Jambunathan K
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4ijbtmy.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).