On Tue, Mar 01, 2016 at 11:13:18PM +0900, Stephen J. Turnbull wrote:
> Adam McGreggor writes:
>
> > Or could we meet user expectations (real users, not geeks), [and
> > allow glob syntax].
>
> Definitely worth discussing, but my initial reaction is negative for
> the reasons discussed below.
>
On Tue, Mar 01, 2016 at 09:26:13AM -0500, Barry Warsaw wrote:
> globs make sense for file system operations, and we've been using them for
> decades in shells. I think globs make less sense for header value pattern
> matching.
Looking at my sieve/procmail recipes, I rarely use globs (except in
On Mar 01, 2016, at 11:13 PM, Stephen J. Turnbull wrote:
>In theory we could use globs as well (some of the modern VCSes permit
>glob or regexp syntax), but it's not a serious data loss issue for a
>VCS if a mistake is made. You just run the add command again with -f,
>or uncommit, or whatever.
Adam McGreggor writes:
> Or could we meet user expectations (real users, not geeks), [and
> allow glob syntax].
Definitely worth discussing, but my initial reaction is negative for
the reasons discussed below.
> Simples:
> *@mail.ru
> *@*mail.ru
> ?@mail.ru
Are those
On Tue, Mar 01, 2016 at 04:37:16AM +0900, Stephen J. Turnbull wrote:
> Barry Warsaw writes:
>
> > IBan would need to have a flag which indicate whether the `email`
> > is a literal address or a pattern. I don't think it's worth having
> > two separate interfaces/models, but we might want to
Barry Warsaw writes:
> On Mar 01, 2016, at 04:37 AM, Stephen J. Turnbull wrote:
> >Or we could continue to have the core representation be "leading '^'
> >iff regexp", and once again have Postorius prepend "^.*" or whatever.
>
> In which case, the core's model wouldn't have to change,
On Mar 01, 2016, at 04:37 AM, Stephen J. Turnbull wrote:
>Are regexps sufficiently slow that *always* using a regexp would hurt
>performance?[1] The model I really had in mind was to always use
>regexps, and have a flag in the UI (Postorius) to regexp-quote when
>the user wants a literal.
I
Barry Warsaw writes:
> IBan would need to have a flag which indicate whether the `email`
> is a literal address or a pattern. I don't think it's worth having
> two separate interfaces/models, but we might want to rename `email`
> to something more generic (`pattern` would be fine, with the
On Feb 27, 2016, at 02:02 PM, Stephen J. Turnbull wrote:
>I hope we haven't propagated this rather user-unfriendly interface
>(the convention of accepting both regexps and literals, distinguishing
>by "^" in column 0) to Mailman 3.
Sadly, it's true.
Mostly this is historical since we've
Mark Sapiro writes:
> I agree it's confusing, and I've been caught in this confusion myself
> and neglected to put the leading ^ in what I clearly intended to be a
> regexp, but the convention goes back a long way in MM2.
Oh, of course I'm -1 on changing "regexps start with '^'" convention
in
On 02/26/2016 09:02 PM, Stephen J. Turnbull wrote:
> On Mailman-Users, Mark Sapiro writes:
>
> > Further, in the ban_list (and many other places in Mailman) if an
> > address is intended to be a regular expression pattern, it must begin
> > with '^', so you really want
> >
> >
11 matches
Mail list logo
