'Bug#33973: To or Cc> doesn't contain" doesn't behave expectation conform'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Bug#33973: To or Cc> doesn't contain" doesn't behave expectation conform
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-10-31 21:30:22
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 31 October 2001 02:14, Dan Morrill wrote:
> Er... well, yes, I can see what you mean about
> it being an AND vs. OR thing.  However, KMail
> in KDE 2.1 did NOT have that behavior;  <To or Cc>
> behaved as the original reporter described.
>
> This is either an undocumented change in behavior,
> or a regression, depending on your point of view.

I agree. I'm also not very happy with this change because it obviously 
confuses a lot of people (we can't expect our users to know the rules 
of de Morgan). We'll hopefully change this before KDE 3.0. We should 
replace the <To or Cc> by something more generic like <recipients> (cf. 
<any header>, <body>, etc.).

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE74G1uGnR+RTDgudgRApRNAJ9sjlHWSPcisPEEILzcIaBkvAG8jgCg3KcZ
+epwq2V8Ue10GpLcZqvH+DE=
=RytA
-----END PGP SIGNATURE-----
_______________________________________________
kmail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread] 