emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: should the mail list be splitted resp. sub-tagged ?
Date: Tue, 04 Jan 2011 20:25:24 +0100	[thread overview]
Message-ID: <pkn8vz0tqsa.fsf@this.is.really.invalid> (raw)
In-Reply-To: 12023.1294167155@gamaville.americas.hpqcorp.net

Nick Dokos <nicholas.dokos@hp.com> writes:

> Štěpán Němec <stepnem@gmail.com> wrote:
>
>> FWIW, I do. Having [Org] (or anything, really) prepended to the subjects
>> of _all_ mails coming from a list that is already uniquely identifiable
>> (e.g. by its address) has no information value altogether (unlike
>> [Babel], [PATCH] etc.) and only takes up the much precious Subject:
>> header space.
>> 
>> I have never understood why anyone would like anything like that.
>>
>
> Because I can scan my inbox at a glance and triage quickly. Here's what
> I see (with mh-e in emacs as my reader):
>

(disclaimer: I've been seeing this argument for the best part of 20
years, I doubt I'm bringing anything new to the table, but I feel
strongly about it)

Triage is for *computers* to do, they're much better at it than humans.

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.

>  ...
>  221+ 01/04 Štěpán Němec [Orgmode] Re: should the mail list be
> splitted resp. sub-tagged ?<<Bastien <bastien.guerry@wikimedia.fr>
> writes: > Hi Torste
>  ...
>
> If I am in org-mode mode (so to speak), I'll look at it. If not, I will
> skip it for now and get back to it later.
>
> Having the mailing list markers is indispensable to me. I belong to
> quite a few MLs and the ones that don't have a marker are a PITA.
> Shortening the marker is fine: eliminating it is not.
>
>> If you want to somehow treat the mails from this list specially, why
>> don't you filter on the presence of the mailing list address in the
>> headers, for example?
>> 
>
> Because all of that needs additional setup, both at the front end to do
> the filtering and at the back end to make sure that I don't miss anything.
> And that needs debugging and continued maintenance (and missed emails when
> something goes wrong, which inevitably it will). I'd rather have the list
> software take care of it.

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).

Robert

  reply	other threads:[~2011-01-04 19:25 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 [this message]
2011-01-05  9:13           ` Achim Gratz
2011-01-05  9:56             ` 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
  -- strict thread matches above, loose matches on Subject: below --
2011-05-05  9:37 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=pkn8vz0tqsa.fsf@this.is.really.invalid \
    --to=rpluim@gmail.com \
    --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).