Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Spam despite spam header
Date: Tue, 24 Dec 2013 20:58:18 +0100	[thread overview]
Message-ID: <87vbyeyqa4.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: <mailman.10164.1387818251.10748.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

> ...

I don't think that anyone doubts that you have a very
solid understanding and uses Gnus with an expert's
touch.

Even I, compared to how people use the web GUIs,
Outlook, and even Evolution, Thunderbird/Icedove, etc.,
the way I use Emacs Gnus compared to them, it's like
the wrists of Wayne Gretzky and the speed of Usain
Bolt... And I consider myself a Gnus novice!

Instead, I merit it to 80-90% to the all text, 100%
configurable interface of Gnus and the Emacs message
mode. Fumbling around with folders and drop down menus
just can't keep up. And it doesn't matter it was a
sensation when Xerox and Apple and later even Microsoft
made a big deal out of it in the 80s.

But, back to this discussion, if you envision two
fighters at the Colosseum of paleo-Rome. If one of them
spends a lifetime perfecting the use of the sword, and
the other guy do the same with the spear, of course
neither of them could ever be convinced the other guy's
weapon is better. If one wanted an answer to that
question, one would be better off asking a
philosopher-king who fought in the archery, and had
never wielded either sword or spear. But perhaps he
would answer something else altogether.

-- 
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united:  http://user.it.uu.se/~embe8573
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2013-12-24 19:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 16:13 Emanuel Berg
2013-12-11 18:11 ` Adam Sjøgren
     [not found] ` <mailman.8951.1386785526.10748.info-gnus-english@gnu.org>
2013-12-11 19:21   ` Emanuel Berg
2013-12-11 20:04     ` Dmitrii Kashin
2013-12-11 20:26       ` Adam Sjøgren
2013-12-12  7:14         ` Dmitrii Kashin
2013-12-12  9:22           ` Peter Münster
2013-12-12 15:27             ` Dmitrii Kashin
2013-12-23 17:03           ` Adam Sjøgren
     [not found]           ` <mailman.10164.1387818251.10748.info-gnus-english@gnu.org>
2013-12-24 19:58             ` Emanuel Berg [this message]
     [not found]       ` <mailman.8965.1386793822.10748.info-gnus-english@gnu.org>
2013-12-11 22:42         ` Emanuel Berg
2013-12-11 20:22     ` Adam Sjøgren
     [not found]     ` <mailman.8961.1386792309.10748.info-gnus-english@gnu.org>
2013-12-11 22:33       ` Emanuel Berg
2013-12-12  7:27         ` Dmitrii Kashin
     [not found]         ` <mailman.8994.1386833301.10748.info-gnus-english@gnu.org>
2013-12-12 20:03           ` Emanuel Berg
     [not found]     ` <mailman.8964.1386793377.10748.info-gnus-english@gnu.org>
2013-12-11 22:40       ` Emanuel Berg
2013-12-12 23:35       ` Emanuel Berg
2013-12-13  9:13         ` Adam Sjøgren

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=87vbyeyqa4.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --cc=info-gnus-english@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.
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).