Gnus development mailing list
 help / color / mirror / Atom feed
From: dick.r.chiang@gmail.com
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: how to forward a message that contains attachment
Date: Sun, 05 Apr 2020 17:25:55 -0400	[thread overview]
Message-ID: <87k12tipzw.fsf@dick> (raw)
In-Reply-To: <87ftdhx29r.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Sun, 05 Apr 2020 19:37:04 +0200")

Your opinion regarding GMail appears to have changed.  Surely, now, having
begrudgingly joined the ranks of those willing to sacrifice their
privacy for the convenience of an always-on, everywhere-accessible
big-box mail service, you'll admit my earlier desire to facilitate the path
between Gmail and Gnus more "imaginable" than you let on several months ago.

I continue to bemoan Gnus's de facto guidance, i.e., the top search results
for "gnus gmail", on the extremely common task of integrating a big-box IMAP
service -- a task mu4e and notmuch have made much easier than Gnus.

From: Adam Sjøgren <asjo@koldfront.dk>
Subject: Re: Proposed new introductory section to the Gnus manual
Newsgroups: gmane.emacs.gnus.general
To: ding@gnus.org
Date: Tue, 10 Sep 2019 22:39:36 +0200 (29 weeks, 5 days, 27 minutes ago)
Organization: koldfront - analysis & revolution, Copenhagen, Denmark

dick writes:

> I'm typical of most newcomers who merely want their cloud service, i.e.,
> Gmail, integrated into emacs.

If there is one thing I have learned about email over the past 25 years,
it is that no two people agree on how they want to handle their email.

What I want, some people think is nuts, and the other way around.

> I couldn't find anything authoritative for this pedestrian task.

See, from my perspective, I can't imagine why a user of Emacs would want
to gift all their email to Google.

To you it's "typical".

I'm sure we could go on with a looong list like that.



  reply	other threads:[~2020-04-05 21:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 14:33 Uwe Brauer
2020-04-04 14:54 ` Eric S Fraga
2020-04-04 18:57   ` Uwe Brauer
2020-04-05  2:00     ` Bob Newell
2020-04-05  6:07       ` Uwe Brauer
2020-04-05 19:31         ` Bob Newell
2020-04-05 13:18     ` Eric S Fraga
2020-04-05 17:11       ` Uwe Brauer
2020-04-05 17:37         ` Adam Sjøgren
2020-04-05 21:25           ` dick.r.chiang [this message]
2020-04-06 10:19             ` gmail setup (was: how to forward a message that contains attachment) Alberto Luaces
2020-04-07 16:42               ` gmail setup dick.r.chiang
2020-04-07 17:46                 ` Alberto Luaces
2020-04-07 18:19                   ` dick.r.chiang
2020-04-07 18:35                     ` Alberto Luaces
2020-04-08  1:53                       ` Bob Newell
2020-04-10 16:56                         ` Alberto Luaces
2020-04-06 10:19           ` how to forward a message that contains attachment Uwe Brauer
2020-04-06 10:26           ` Uwe Brauer
2020-04-07 17:03             ` Adam Sjøgren
2020-04-06 11:36           ` Uwe Brauer

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=87k12tipzw.fsf@dick \
    --to=dick.r.chiang@gmail.com \
    --cc=asjo@koldfront.dk \
    --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).