I’m currently looking at a message entitled “RE: Re:[ntdev] Re:Re:Driver Verifier and non-paged pool memory leak”.
Further on, down Outlook’s list of messages there is a “RE: Re:[ntdev] Re:Driver Verifier and non-paged pool memory
leak” and, yet further on, “RE: Re:[ntdev] Driver Verifier and non-paged pool memory leak”. I’m sure if I looked some
more, I might even find the original thread.
It would be really nice if I could group all the responses together. Is it possible that some clever OSR list slave can
write something to discard all the extra “Re:Re:” crap before the message is sent out please?
Pretty Please?
Don
Don Ward wrote:
I’m currently looking at a message entitled “RE: Re:[ntdev] Re:Re:Driver Verifier and non-paged pool memory leak”. Further on, down Outlook’s list of messages there is a “RE: Re:[ntdev] Re:Driver Verifier and non-paged pool memory leak” and, yet further on, “RE: Re:[ntdev] Driver Verifier and non-paged pool memory leak”. I’m sure if I looked some more, I might even find the original thread.
It would be really nice if I could group all the responses together. Is it possible that some clever OSR list slave can write something to discard all the extra “Re:Re:” crap before the message is sent out please?
Pretty Please?
This is the fault of broken mail readers. It is well nigh impossible to
write a regular expression parser that catches all of the weird “reply”
mechanisms that some mail readers generate.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
It’s possible but to be frank, unlikely in the extreme.
Lyris, for all its advantages, has it’s own peculiar way of doing things. While it is at least theoretically possible to write a pre-processing “add-in” for Lyris to run on each message, every time we’ve tried to do this it’s turned into an annoying process. This is made worse by the fact that the dough-heads at Lyris can’t seem to provide an example – ANY example – of how to implement this sort of feature – or at least not one that works with any version of Lyris ListManager that they’ve released in the past five years.
So… Yes, it’s possible. And, yes, someday we may do it. But it’s “on the prioritized list of things to do” right after stripping HTML out of all posts after converting them to plain text.
Peter
Partner-level List Slave
Oddly, converting plain text back to html is trivial.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@osr.com
Sent: Tuesday, June 05, 2007 4:24 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] OT Can we get rid of the Re:Re:?
It’s possible but to be frank, unlikely in the extreme.
Lyris, for all its advantages, has it’s own peculiar way of doing
things. While it is at least theoretically possible to write a
pre-processing “add-in” for Lyris to run on each message, every time
we’ve tried to do this it’s turned into an annoying process. This is
made worse by the fact that the dough-heads at Lyris can’t seem to
provide an example – ANY example – of how to implement this sort of
feature – or at least not one that works with any version of Lyris
ListManager that they’ve released in the past five years.
So… Yes, it’s possible. And, yes, someday we may do it. But it’s “on
the prioritized list of things to do” right after stripping HTML out of
all posts after converting them to plain text.
Peter
Partner-level List Slave
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
What I had in mind was much simpler than “well nigh impossible”. I thought, apart from a response that began with “Re:”
(ignore case), then just delete any occurrence of “Re:” afterwards in the subject field. It might not be perfect but it
would probably deal with most of the problems.
Don
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim
Roberts
Sent: 05 June 2007 21:00
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] OT Can we get rid of the Re:Re:?
Don Ward wrote:
> I’m currently looking at a message entitled “RE: Re:[ntdev] Re:Re:Driver Verifier and non-paged pool
memory leak”. Further on, down Outlook’s list of messages there is a “RE: Re:[ntdev] Re:Driver
Verifier and non-paged pool memory leak” and, yet further on, “RE: Re:[ntdev] Driver Verifier and non-
paged pool memory leak”. I’m sure if I looked some more, I might even find the original thread.
>
> It would be really nice if I could group all the responses together. Is it possible that some clever
OSR list slave can write something to discard all the extra “Re:Re:” crap before the message is sent
out please?
>
> Pretty Please?
>
This is the fault of broken mail readers. It is well nigh impossible to
write a regular expression parser that catches all of the weird “reply”
mechanisms that some mail readers generate.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I agree. The problem isn’t the algorithm, it’s making it work from Lyris.
I’ll make you this offer, though: You write the Lyris plug-in to do it, and I’ll put it on OSR Online.
Peter
List Slave Technical Fellow
Ooh, ooh, ooh- can I be the first to post the subject “Re:” when you finish? ;->
(I know it doesn’t break anything- just the responses subject lines all look like the original post, which wouldn’t be all that bad)…
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Don Ward
Sent: Tuesday, June 05, 2007 1:49 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] OT Can we get rid of the Re:Re:?
What I had in mind was much simpler than “well nigh impossible”. I thought, apart from a response that began with “Re:”
(ignore case), then just delete any occurrence of “Re:” afterwards in the subject field. It might not be perfect but it
would probably deal with most of the problems.
Don
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim
Roberts
Sent: 05 June 2007 21:00
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] OT Can we get rid of the Re:Re:?
Don Ward wrote:
> I’m currently looking at a message entitled “RE: Re:[ntdev] Re:Re:Driver Verifier and non-paged pool
memory leak”. Further on, down Outlook’s list of messages there is a “RE: Re:[ntdev] Re:Driver
Verifier and non-paged pool memory leak” and, yet further on, “RE: Re:[ntdev] Driver Verifier and non-
paged pool memory leak”. I’m sure if I looked some more, I might even find the original thread.
>
> It would be really nice if I could group all the responses together. Is it possible that some clever
OSR list slave can write something to discard all the extra “Re:Re:” crap before the message is sent
out please?
>
> Pretty Please?
>
This is the fault of broken mail readers. It is well nigh impossible to
write a regular expression parser that catches all of the weird “reply”
mechanisms that some mail readers generate.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
> [quote]
What I had in mind was much simpler than “well nigh impossible”.
[/quote]
I agree. The problem isn’t the algorithm, it’s making it work from Lyris.
I’ll make you this offer, though: You write the Lyris plug-in to do it, and I’ll put it on OSR Online.
Peter
Nah; thanks, but no thanks (knowing absolutely nothing about Lyris). I’m happy with “we’d like to do it, but currently, it’s too hard”. It’s a minor annoyance and, curiously, the knowledge that it’s difficult to fix makes it easier to live with.
Don
Peter,
in some days of old, your mailing list were using the:
[ntdev] Re: subj
syntax for replies. The last years it uses:
Re: [ntdev] subj
for replies.
Is it possible to return the first syntax? much more convinient.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
wrote in message news:xxxxx@ntdev…
>
>
> It’s possible but to be frank, unlikely in the extreme.
>
> Lyris, for all its advantages, has it’s own peculiar way of doing things.
While it is at least theoretically possible to write a pre-processing “add-in”
for Lyris to run on each message, every time we’ve tried to do this it’s turned
into an annoying process. This is made worse by the fact that the dough-heads
at Lyris can’t seem to provide an example – ANY example – of how to implement
this sort of feature – or at least not one that works with any version of
Lyris ListManager that they’ve released in the past five years.
>
> So… Yes, it’s possible. And, yes, someday we may do it. But it’s “on the
prioritized list of things to do” right after stripping HTML out of all posts
after converting them to plain text.
>
> Peter
> Partner-level List Slave
>
>
Not to the best of my knowledge. We didn’t specifically change this, so it’s almost certainly Lyris changing its mind about the format of such things.
Peter
Senior Lead List Slave