Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Filtering out calendar invites?
Date: Thu, 28 Oct 2021 07:53:29 -0700	[thread overview]
Message-ID: <87sfwlgpzq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <22ilxhimln.fsf@hiptop.liman.net>

Lars-Johan Liman <liman@netnod.se> writes:

> Whooa!
>
> I'm backing up! My hack actually seems to work! ;-)
>
> In case anyone googles this thread: this seems to work for me. Happy to
> hear feedback from others.
>
> I put this as one of the entries in my nnmail-split-fancy variable. It's
> a bit crude as it doesn't assert that the string is actually a MIME tag
> and not just part of the text in the message, 

If you really want to go down a rabbit hole, you can call the function
`gnus-article-mime-handles' while gnus-article-buffer is current. That
ought to give you a full list of the actual mime attachments on the
message.



      reply	other threads:[~2021-10-28 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 15:24 Lars-Johan Liman
2021-10-28  8:23 ` Lars-Johan Liman
2021-10-28 14:53   ` Eric Abrahamsen [this message]

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=87sfwlgpzq.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).