OE Bug I hadn't noticed before

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mark Hurd - 28 Mar 2008 19:42 GMT

I found this when sending URLs.

Regards,
Mark Hurd, B.Sc.(Ma.) (Hons.)

Word wrap stops once it gets confused by an indented long word!

HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAtTheStartOfTheLineAndItDoesNotCauseAProblem

See these lines
are unaffected
by the bug.

HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAfterAspaceAndItCausesAProblem!See these linesare affected by the bug!

Reply to this Message

Bruce Hagen - 28 Mar 2008 20:03 GMT

True about a long word. For URLs, some wrap, and some do not. Just guessing
before I send, that this one will.

http://groups.google.com/groups/search?q=author%3Amarkhurd%40ozemail.com.au&star
t=0&scoring=d&hl=en&lr=&safe=images&

Default word wrap is 76 characters, FWIW.

Signature

Bruce Hagen
MS-MVP Outlook Express
Imperial Beach, CA

>I found this when sending URLs.
>
[quoted text clipped - 11 lines]
> HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAfterAspaceAndItCausesAProblem!See
> these linesare affected by the bug!

Reply to this Message

Mark Hurd - 30 Mar 2008 07:28 GMT

It needs to be indented to fail. I've only deleted the > in the forward
message below and you'll see it confuses the word wrapping when sending
(or saving as draft -- that's how you can test many 'on send' issues
without sending).

Signature

Regards,
Mark Hurd, B.Sc.(Ma.) (Hons.)

> True about a long word. For URLs, some wrap, and some do not. Just
> guessing before I send, that this one will.

http://groups.google.com/groups/search?q=author%3Amarkhurd%40ozemail.com.au&star
t=0&scoring=d&hl=en&lr=&safe=images&>> Default word wrap is 76 characters, FWIW.> --> Bruce Hagen> MS-MVP Outlook Express> Imperial Beach, CA>>> "Mark Hurd" <markhurd@ozemail.com.au> wrote in messagenews:OPEIHOQkIHA.4752@TK2MSFTNGP03.phx.gbl...>>I found this when sending URLs.>>>> Regards,>> Mark Hurd, B.Sc.(Ma.) (Hons.)>>>> Word wrap stops once it gets confused by an indented long word!>>>>HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAtTheStartOfTheLineAndItDoesNotCauseAProblem>>>> See these lines>> are unaffected>> by the bug.>>>>HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAfterAspaceAndItCausesAProblem!See these linesare affected by the bug!>

Reply to this Message

Bruce Hagen - 30 Mar 2008 14:49 GMT

You must have a different problem. Links in replies in this newsgroup, no
matter how many times indented, continue to work for me whether they were
wrapped, or not.

Signature

Bruce Hagen
MS-MVP Outlook Express
Imperial Beach, CA

<markhurd@ozemail.com.au> wrote in message
news:%23lQV38ikIHA.980@TK2MSFTNGP06.phx.gbl...

> It needs to be indented to fail. I've only deleted the > in the forward
> message below and you'll see it confuses the word wrapping when sending
[quoted text clipped - 15 lines]
> bug.>>>>HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAfterAspaceAndItCausesAProblem!See
> these linesare affected by the bug!>

Reply to this Message

Robert Aldwinckle - 30 Mar 2008 20:08 GMT

> It needs to be indented to fail. I've only deleted the > in the forward
> message below and you'll see it confuses the

> word wrapping when sending (or saving as draft

Then that's another bug in OE's implementation of Format=Flowed ; )

The one that has had me ready to zap it out is that it reflows quotes shorter
than my line size *after* I have composed my reply. Hence, the only way that
I can see what is going to be sent is to inspect what it puts in either the Drafts
(e.g. when I have to save it with Ctrl-a,Ctrl-c,Ctrl-s,Esc) or the Outbox
(e.g. when I have to block it with Alt-F,W, Ctrl-a, Ctrl-c, Alt-s)
Then, when I retrieve it from either location and do Ctrl-a,Ctrl-v
I can continue without further interference from F=F.

I would like F=F to be used *only* for the case in which the line size of the quoted
line is *greater* than my line size. As I use a line size of 132 and do my own
formatting F=F is unnecessary for me but I am willing to continue the indication
of it in my headers.

BTW the effect that you are commenting on has been noticed before
but I think that this is the first time it has been so clear that F=F
is responsible for doing it.

FYI

Robert Aldwinckle
---

> -- that's how you can test many 'on send' issues without sending).
>
[quoted text clipped - 8 lines]
> unaffected>> by the bug.>>>>HereIsALongSentenceWithAbsolutelyNoSpacesButStartsAfterAspaceAndItCausesAProblem!See these linesare
> affected by the bug!>

Reply to this Message