Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Strey <mstrey@strey.biz>
To: info-gnus-english@gnu.org
Subject: How to summarize an e-mail thread? (was: Mail layout and fonts)
Date: Wed, 15 Apr 2015 17:18:37 +0200	[thread overview]
Message-ID: <87zj698lo2.fsf_-_@strey.biz> (raw)
In-Reply-To: <CADtN0WKnbOP31a88AqbqhFLZth=9rWBjOuE-yLS15h-02hTmsw@mail.gmail.com>

Hello,

Please allow me to chime in here.

On Mi, 2015-04-15, Elias Mårtenson wrote:

[...]

> I welcome you to work in the banking industry for a while. If you do
> this there you will likely be accused of trying to hide the history
> since looking down at the email chain (which is pretty much guaranteed
> to contain tens of images, mostly screenshots of the things people
> talk about) is the only way people can get an understanding of what is
> being discussed. Messages are full of references to messages further
> down in the chain. When a new person is briefed on a case they get a
> copy of the last email in the chain with a comment "Please read this
> to get up to date on the current issue".

I do not work in such a hostile environment and therefore do not need
Elias' solution.  Nevertheless, from time to time I would like to have a
solution to summarize a lengthy e-mail thread to create a report for
somebody else.

After a short time looking around I just found the following solution
for this problem:

  In the summary buffer T #, O f <file name>.
  
The result is a text file in correct chronological order.
Though attachments are not included and so aren't other mime parts.

Elias, is your solution suited for the occasional use?

Any other proposal?

Best regards
Michael Strey

-- 
http://www.strey.biz * https://twitter.com/michaelstrey


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2015-04-15 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.628.1428993610.904.info-gnus-english@gnu.org>
2015-04-14 16:52 ` Mail layout and fonts Emanuel Berg
2015-04-15  9:42   ` Elias Mårtenson
2015-04-15 12:01     ` Adam Sjøgren
2015-04-15 13:24       ` Elias Mårtenson
2015-04-15 19:45         ` Adam Sjøgren
     [not found]         ` <mailman.771.1429127124.904.info-gnus-english@gnu.org>
2015-04-16  0:54           ` Emanuel Berg
     [not found]   ` <mailman.724.1429090944.904.info-gnus-english@gnu.org>
2015-04-15 11:35     ` invalid
2015-04-15 13:32       ` Elias Mårtenson
2015-04-15 15:18         ` Michael Strey [this message]
2015-04-16  2:30           ` How to summarize an e-mail thread? (was: Mail layout and fonts) Elias Mårtenson
2015-04-15 16:39       ` Mail layout and fonts Emanuel Berg
     [not found]       ` <mailman.738.1429104778.904.info-gnus-english@gnu.org>
2015-04-15 16:47         ` Emanuel Berg
2015-04-15 16:28     ` Emanuel Berg
2015-04-15 16:39       ` Elias Mårtenson

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=87zj698lo2.fsf_-_@strey.biz \
    --to=mstrey@strey.biz \
    --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).