From: "Bjørn Mork" <bmork@dod.no>
Subject: Re: Automagic content recognition - good or bad?
Date: Wed, 10 Jul 2002 14:54:08 +0200 [thread overview]
Message-ID: <hvit3n7ngv.fsf@rasputin.ws.nextra.no> (raw)
In-Reply-To: <vaf1yab7o22.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> You can always frob mm-uu-beginning-regexp and perhaps
> mm-uu-type-alist.
Thanks. I already found mm-uu-configure-list which did what I wanted.
But my question is really whether the default makes any sense? Having
such features is great; turning them on by default is...well, not as
great. IMHO.
> M-x apropos-value RET #! RET is my friend. It helped me find these
> things very quickly :-)
Oh, I should learn to use emacs sometime :-) I usually grep for these
things in the gnus/lisp directory...
Bjørn
next prev parent reply other threads:[~2002-07-10 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 11:48 Bjørn Mork
2002-07-10 12:41 ` Kai Großjohann
2002-07-10 12:54 ` Bjørn Mork [this message]
2002-07-10 14:33 ` Josh Huber
2002-07-10 16:18 ` Frank Schmitt
2002-12-30 19:11 ` Lars Magne Ingebrigtsen
2002-12-30 19:26 ` Karl Eichwalder
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=hvit3n7ngv.fsf@rasputin.ws.nextra.no \
--to=bmork@dod.no \
/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).