Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: How to wide-reply (email) to multiple people?
Date: Sun, 09 Dec 2018 13:07:04 +0100	[thread overview]
Message-ID: <87a7leykd3.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87ftv7pd1q.fsf@portable.galex-713.eu>

Alexandre writes:

> This is a feature I’ve been using quite much, and I’d like its behavior
> to be more logical toward redundancy of subjects too.

I guess Gnus should just deduplicate the subjects?

I only tried S V on articles with different subjects, so I didn't notice
the effect.

> Some (non-standard, I guess) feature I always wanted is true multiple
> reply for emails: like, multiple message-ids in the in-reply-to,

That's what the spec says:

   The "In-Reply-To:" field may be used to identify the message (or
   messages) to which the new message is a reply, while the
   "References:" field may be used to identify a "thread" of
   conversation.

    - https://www.ietf.org/rfc/rfc2822.txt section 3.6.4

But Gnus only includes the first marked email in In-Reply-To. That
sounds like a bug to be, in S V.

> and merging the references of all messages you reply too.

I think S V does that - at least it did in my test.

> The worse that happenned until now is people interpreting it as thread
> stealing (though I changed the subject, used Was:, and both subjects
> and messages were mine).

(Why would you want the new article connected to the previous thread, if
you changed the subject?)

> I’d love to begin doing that and then making up some interface within
> Summary that would display it graph-like like in git :D

I think I've seen something like that decades ago? Yeah:

 · http://gnus.org/manual/gnus_55.html#Tree-Display


  Best regards,

    Adam

-- 
 "Darn tootin'"                                               Adam Sjøgren
                                                         asjo@koldfront.dk




  reply	other threads:[~2018-12-09 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08 21:56 Chris Marusich
2018-12-08 22:26 ` Adam Sjøgren
2018-12-09  3:42   ` Chris Marusich
2018-12-09  3:57 ` Alexandre Garreau
2018-12-09 12:07   ` Adam Sjøgren [this message]
2018-12-09 13:17     ` Alexandre Garreau
2018-12-09 13:28       ` Alexandre Garreau
2018-12-09 13:44         ` Adam Sjøgren
2018-12-09 17:31           ` Eric Abrahamsen
2018-12-09 17:56             ` Adam Sjøgren
2018-12-09 13:41       ` 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=87a7leykd3.fsf@tullinup.koldfront.dk \
    --to=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).