Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: `A M' gives consistently wrong results
Date: Mon, 22 Oct 2001 07:13:28 -0700	[thread overview]
Message-ID: <m1wv1npxxh.fsf@reader.newsguy.com> (raw)
In-Reply-To: <87snccw7n6.fsf@inanna.rimspace.net> (Daniel Pittman's message of "Mon, 22 Oct 2001 15:44:45 +1000")

Daniel Pittman <daniel@rimspace.net> writes:

> Ah, yes, but does it work? It occurred to me, just after sending this,
> that I hadn't actually tested it...
>
> So, I am curious. Did it fix the problem?

Yes it did Daniel.  And the sad thing is I knew about that variable
but assumed it applied to `other' things.  I also broke the first rule
of a query/reply... I didn't try first either.

I still think case sensitive is a better default though.  With that
default at least the normal means inside regexp allow for case
sensitivity.



  reply	other threads:[~2001-10-22 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  4:06 Harry Putnam
2001-10-22  4:37 ` Daniel Pittman
2001-10-22  4:49   ` Harry Putnam
2001-10-22  5:44     ` Daniel Pittman
2001-10-22 14:13       ` Harry Putnam [this message]
2001-10-22  8:14 ` Kai Großjohann

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=m1wv1npxxh.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    --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).