unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ng0 <ngillmann@runbox.com>
To: "Ricardo Wurmus" <rekado@elephly.net>, "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: notmuch users: how do you filter debbugs?
Date: Fri, 30 Sep 2016 12:35:05 +0000	[thread overview]
Message-ID: <8760pd8t1i.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87vaxesdpb.fsf@elephly.net>

Ricardo Wurmus <rekado@elephly.net> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hello!
>>
>> ng0 <ngillmann@runbox.com> skribis:
>>
>>> Let's say you use notmuch as your Email sorting system, and you are
>>> subscribed to more than one projects -bug@gnu.org, how do you filter
>>> them? Currently it all ends up in inbox because they can't be
>>> categorized, which is annoying for me. It's all debbugs@gnu.org for
>>> me. Is there some other value I can look for to sort them?
>>
>> I highly recommend the emacs-debbugs package if you use Emacs.
>
> I second the use of emacs-debbugs.  It’s a reasonably convenient
> interface albeit not entirely intuitive.
>
> ~~ Ricardo
>
>

But the email still ends up in my inbox, and as I filter through tags,
I'd like to be able to throw guix related things into tag:guix::bug.
Recommending to use another interface doesn't fix this problem.
-- 
               ng0
#.endofsubmission.

  reply	other threads:[~2016-09-30 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 18:10 notmuch users: how do you filter debbugs? ng0
2016-09-29 12:33 ` Ludovic Courtès
2016-09-29 19:33   ` Ricardo Wurmus
2016-09-30 12:35     ` ng0 [this message]
2016-09-30 12:54       ` Ricardo Wurmus
2016-09-30 15:12         ` ng0
2016-09-30 16:03           ` Patricia J. Hawkins
2016-09-30 17:13             ` ng0
2016-09-30 19:35               ` Ricardo Wurmus

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

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

  git send-email \
    --in-reply-to=8760pd8t1i.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).