My previous attempt to send this was itself broken into irregular line lengths. Here's another attempt after changing a registry setting...

That's interesting, but I wonder where you got it from. I have been told by various people to surround the link with exactly "< " before and " >" after. Mixed results (works for some, but not others). Also tried "<< " and " >>". Still no go. Then I tried your version, "<<< " and " >>>" and still people complain that links are coming to them broken. So I don't think there is a universal way to coax a long URL through email in "plaintext" without the possibility that it will get fragged. Send HTML format? Yuk.

--LW

> -----Original Message-----
> From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com] On Behalf Of Appert, Kevin
> Sent: Thursday, January 17, 2008 3:20 PM
> To: sftalk_at_forth.com
> Subject: [sftalk] Re: password in filename?
>
> Consider surrounding links like this: <<<yourlink>>>
>
> Most email clients are able to discern this as a contiguous link and you
> won't have to cut and paste. Alternatively, you can use
> <<<www.tinyurl.com>>> to make a tiny URL out of your long one.
>
> Here's an example.
> <<<http://home.comcast.net/~forther/DSCN0011.JPG>>>
>
> Leon, did you ever see this picture?
>
>
> -----Original Message-----
> From: sftalk-bounce_at_forth.com [mailto:sftalk-bounce_at_forth.com] On Behalf
> Of Ron Oliver
> Sent: Thursday, January 17, 2008 2:29 PM
> To: sftalk_at_forth.com
> Subject: [sftalk] Re: password in filename?
>
> Stefan Schmiedl wrote:
> > On Thu, 17 Jan 2008 17:18:46 -0500
> > Ron Oliver <ron_at_forth.com> wrote:
> >
> >> You'll be emailed a download path
> >> http://www.forth.com/downloads/SwiftForth-Win32-full-3.1.0-<a bunch
> of
> >> letters and numbers>.exe
> >
> > which, if I may add, arrived broken across two lines at my place.
> > I actually had to copy seven characters over by hand :-)
>
> No good deed goes unpunished! I'll look into that.
> --
> Ron Oliver
> Consulting Engineer
> FORTH, Inc.
> www.forth.com
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
> For list command help, send subject "help" to sftalk-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/sftalk
> ----------------------------------------------------------------------
> This list is a forum for SwiftForth users. For product support and
> bug reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------
>
>
> ----------------------------------------------------------------------
> sftalk_at_forth.com The SwiftForth programming discussion email list
> To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
> For list command help, send subject "help" to sftalk-request_at_forth.com
> Message archives are located at http://www.forth.com/archive/sftalk
> ----------------------------------------------------------------------
> This list is a forum for SwiftForth users. For product support and
> bug reports, please send email to support_at_forth.com
> ----------------------------------------------------------------------

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and
bug reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Thu Jan 17 2008 - 16:16:44 PST