From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Bug with buttons in replies?
Date: 03 Jan 2001 13:02:15 +0100 [thread overview]
Message-ID: <vafu27gj12w.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vuoofxs77s9.fsf@csa.bu.edu>
On 31 Dec 2000, Emerick Rogul wrote:
> I'm using Oort gnus v0.01. I have gnus-unbuttonized-mime-types set
> to '("text/*").
I think it's supposed to be a regexp. Though this isn't documented
anywhere.
What happens if you say "text/.*" rather than "text/*"? In a regexp,
"*" means an arbitrary number of repetitions of the previous token,
and "." means any character (except newline). So "text/*" stands for
"text", "text/", "text//", "text///" and so on -- not what you want.
kai
--
~/.signature
prev parent reply other threads:[~2001-01-03 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-31 18:41 Emerick Rogul
2001-01-03 12:02 ` Kai Großjohann [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=vafu27gj12w.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).