Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: `A M' gives consistently wrong results
Date: Sun, 21 Oct 2001 21:06:45 -0700	[thread overview]
Message-ID: <m14ros49y5.fsf@reader.newsguy.com> (raw)


Why does:
`A M'
     List groups that match a regexp (`gnus-group-list-all-matching')

Give consistently wrong results?

In group buffer I have many groups that match this regexp:
nnml:[A-Z]

That is, nnml groups that begin with at least one capital letter.

However `A M nnml:[A-Z]' finds a conglomerate of groups
beginning with a-z and A-Z.

Apparently the alleged regexp matching is not case sensitive.

I wonder why it is necessary to spoil good regexp matching like that?
Most applications allow you to choose case insenstive with an -i flag
or similar and default to real (i.e. case sensitive regexp), or at
least have something sensible like mixed upper lower causing case
sensitivity. 

Can I make `gnus-group-list-all-matching' case sensitive without
writing 5 acres of poor trial and error lisp or crawling thru 400 meters
of hot coals and broken beer bottles?

Shouldn't case sensitive, or at least the mixed upper lower control be
the default?  Why is it considered better to make case sensisitve
difficult?  Its not that hard to write regexp so that they are case
insensitive if one wants that.  But it is impossilbe to write a regexp
that is case sensitive if case insensitive is the default.

Regexp are designed to handle that need already, why mess that up? 






             reply	other threads:[~2001-10-22  4:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  4:06 Harry Putnam [this message]
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
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=m14ros49y5.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    /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).