Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: storing messages into an mbox file
Date: Sun, 10 May 2015 13:39:56 +0100	[thread overview]
Message-ID: <877fsgzjvn.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87egmpq00q.fsf@heimdali.yagibdah.de> (lee@yagibdah.de's message of "Sat, 9 May 2015 16:49:09 +0200")

On Saturday,  9 May 2015 at 16:49, lee wrote:

[...]

> Sometimes gnus is really awful

I sympathise.  I have had feelings like this in the dim past.  Every
time I did, I switched to another MUA (pine, mutt, Thunderbird, gmail,
even Outlook very briefly) only to come back when I hit the limitations
of the other MUAs.  Only mutt lasted for more than a few months, and
that was because I could use Emacs easily as the composition editor.

gnus is frustrating because it is *so* completely adaptable.  You can
tune it to your needs no matter what those needs may be, in my
experience.  The problem is figuring it all out.  This list is brilliant
for this!

But, of course, you should use what works for you!

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-4892acc
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)



  parent reply	other threads:[~2015-05-10 12:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 19:03 lee
2015-04-28 20:03 ` Andreas Schwab
2015-04-29 19:32   ` lee
2015-04-29 20:10     ` Andreas Schwab
2015-04-29 20:37       ` this group and gnu.emacs.gnus (was: Re: storing messages into an mbox file) Emanuel Berg
2015-04-29 23:02       ` storing messages into an mbox file lee
2015-04-30  0:40         ` Eric Abrahamsen
2015-05-04  5:50           ` lee
2015-05-04  6:01             ` Adam Sjøgren
2015-05-07 23:11               ` lee
2015-05-08  9:22                 ` Adam Sjøgren
2015-05-09 14:49                   ` lee
2015-05-09 15:16                     ` Adam Sjøgren
2015-05-10 12:39                     ` Eric S Fraga [this message]
2015-05-12  8:06                       ` Steinar Bang
2015-05-12  9:04                         ` Eric S Fraga
2015-05-13 20:07                       ` lee
2015-05-13 21:48                         ` Adam Sjøgren
2015-05-17  8:46                           ` lee
2015-05-13 23:17                         ` Dan Christensen
2015-05-14  6:13                           ` Steinar Bang
2015-05-17  9:02                           ` lee
2015-05-14  6:10                         ` Steinar Bang
2015-05-17  9:06                           ` lee
2015-05-17 19:42                             ` Steinar Bang
2015-05-17 20:45                             ` Peter Münster
2015-05-14  9:19                         ` e.fraga
2015-05-17  9:40                           ` lee
2015-05-17 13:04                             ` Eric S Fraga
2015-05-04  6:07             ` Eric Abrahamsen
2015-05-07 23:14               ` lee
2015-04-30  9:47         ` Andreas Schwab
2015-05-04  5:45           ` lee
2015-05-07 23:53         ` Dan Christensen
2015-05-08 22:10           ` lee
2015-05-18  2:25     ` Nikolaus Rath

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=877fsgzjvn.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=ding@gnus.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).