unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kelly Dean <kelly@prtime.org>
Cc: emacs-devel@gnu.org
Subject: Re: Rant - Emacs mail is not user friendly
Date: Sat, 15 Nov 2014 10:27:41 +0200	[thread overview]
Message-ID: <8361eghnr6.fsf@gnu.org> (raw)
In-Reply-To: <emacs-mail-is-unusable-0@[87.69.4.28]>

> From: Kelly Dean <kelly@prtime.org>
> Date: Sat, 15 Nov 2014 06:54:07 +0000
> 
> The documentation is ridiculous, it's in the wrong place, it's outdated, the code doesn't work, it's outdated too, and there's no point in trying to fix any of it because my work is unwanted anyway. Even the worst webmail service I've ever used was more user-friendly than this, which is why I keep using them even though they routinely betray me by locking me out of my account for some stupid little thing like lying about my niece's name because it's none of Yahoo's business or logging in from a new IP address and failing to tell Google about it in advance, forcing me to create new account and lose any mail stored in the previous one that I didn't paranoidly download an offline copy of after every mail session in anticipation of their inevitable betrayal. At least Google let me back in af
 ter I traveled back to where I could log in from the previous IP address again. I'm telling you all this in order to waste your time from reading this message so you'll feel my pain, or will at leas

You are right.  The reason is probably that feedmail is used by only a
few who already know from long experience how to set it up.

I'd encourage you to file a bug report about this, and suggest there
changes for the parts that you've succeeded to unlock.  Thanks in
advance.



       reply	other threads:[~2014-11-15  8:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <emacs-mail-is-unusable-0@[87.69.4.28]>
2014-11-15  8:27 ` Eli Zaretskii [this message]
     [not found] <emacs-mail-is-unusable-0>
2014-11-15 11:46 ` Rant - Emacs mail is not user friendly Stephen J. Turnbull
2014-11-16 12:18   ` Kelly Dean
2014-11-16 17:49     ` David Caldwell
2014-11-16 22:52     ` Stephen Berman
2014-11-17  9:48       ` Kelly Dean
2014-11-16 23:22     ` Stephen J. Turnbull
2014-11-17 10:06       ` Kelly Dean
2014-11-17 13:59         ` Ted Zlatanov
2014-11-17 19:54       ` Richard Stallman
2014-11-18  5:30         ` Stephen J. Turnbull
2014-11-21 14:51           ` Richard Stallman
2014-11-21 16:07             ` Stefan Monnier
2014-11-22  5:41               ` Stephen J. Turnbull
2014-11-22 15:51                 ` Stefan Monnier
2014-11-22 16:13                   ` Stephen J. Turnbull
2014-11-22 11:08               ` Richard Stallman
2014-11-22 15:53                 ` Stefan Monnier
2014-11-22  5:40             ` Stephen J. Turnbull
2014-11-22 11:09               ` Richard Stallman
     [not found] <54670009.027ce00a.0184.ffffdfd3SMTPIN_ADDED_BROKEN@mx.google.com>
2014-11-15  7:54 ` Alexis
2014-11-15  6:54 Kelly Dean

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8361eghnr6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kelly@prtime.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.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).