unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: Reply all - issue
Date: Wed, 30 Jan 2013 22:39:40 +0100	[thread overview]
Message-ID: <20130130213940.GC434@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <00bf01cdff0d$4ecedd10$ec6c9730$@nl>

Hi,

I am a *very new* notmuch user (notmuch + mutt-kz/Emacs), but I would
like to throw in a few opinions about this topic.

On Wed, Jan 30, 2013 at 06:14:48PM +0100, Robert Mast wrote:
> Thanks for your clear explanation.
> 
> The thread-merging and breaking is in the procedure already pointed at by
> Jani: (_notmuch_database_link_message() in lib/database.cc.)
> 
> Is there a quick way to recognize those git-threads by subject-syntax, or to
> reliably tag them to exclude them from subject-breaking?
> 

I don't like this feature at all.  Threads with patches from
git-send-email are not the only kind of threads where this might be
relevant.  Often I encounter threads with sub-threads which are a little
OT hence get renamed, but they are still related to the parent thread.
Sometimes this helps in following how a topic came up while discussing
something else.  This is especially true when going through old emails
for reference.  I have encountered this in mailing lists, personal
emails and discussions with colleagues.  One of the many other reasons
for me to switch from Gmail to my present setup was to avoid this
"feature".

That said, I think this feature is indeed useful at times but it should
be implemented in the UI on user command or as a configurable (e.g. mutt
provides the <break-thread> command), not a default underlying behaviour
of the backend.  If this is pursued, implementing it as a configurable
in the Emacs UI might be more appropriate (or whatever other UIs exists
out there).

Hope this is constructive to the discussion.  :)

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2013-01-30 21:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 21:58 Reply all - issue Robert Mast
2013-01-28 15:13 ` Jani Nikula
2013-01-28 18:15   ` Robert Mast
2013-01-29  2:47     ` Carl Worth
2013-01-30 17:14       ` Robert Mast
2013-01-30 21:39         ` Suvayu Ali [this message]
2013-01-31 10:21           ` Andrei POPESCU
2013-01-30 20:56       ` Robert Mast
2013-01-30 21:49       ` Robert Mast
2013-01-31  1:12         ` David Bremner
2013-01-31  1:14           ` David Bremner
2013-02-12  7:07             ` Jameson Graef Rollins
2013-02-12 19:17               ` Carl Worth
2013-01-31 10:52 ` Michał Nazarewicz
2013-02-02 16:21   ` Robert Mast
2013-02-02 20:52     ` David Bremner
2013-02-03  0:06       ` [Spam-verdenking][english 100%] " Robert Mast
2013-02-03 15:26       ` Robert Mast
2013-02-03 18:28         ` David Bremner
2013-02-10 15:43       ` Robert Mast
2013-02-04 10:39     ` Michał Nazarewicz
2013-02-04 15:29       ` Suvayu Ali
2013-02-06 18:19       ` Istvan Marko

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=20130130213940.GC434@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).