Re: (no subject)
Re: (no subject)
- Subject: Re: (no subject)
- From: JollyRoger <email@hidden>
- Date: Sun, 26 Nov 2000 19:25:14 -0600
on 11/26/2000 4:57 PM, Paul Berkowitz at email@hidden wrote:
>
On 11/26/00 2:33 PM, "JollyRoger" <email@hidden> wrote:
>
>
> on 11/26/2000 4:25 PM, Paul Berkowitz at email@hidden wrote:
>
>
>
>> For some reason, some people have started to post scripts here using commas
>
>> to represent the continuation character (made by option-L), which gets
>
>> mangled by server, as does SE's soft-wrapping if you simply leave it out.
>
>
>
> It's not that people are purposefully using commas in scripts - it's due to
>
> the way the list server processes special characters. The option-L
>
> character is changed to a comma when it is encountered in a message.
>
>
>
> , <-- see?
>
>
>
Aha - I didn't know that. Sorry, everyone. For some reason, I thought I'd
>
only started seeing that recently.
Hey Paul,
You are correct in that it started happening when Apple changed to the new
servers.
>
Oh well, now that everyone knows ... (maybe you could remember to say
>
something when pasting option-Ls in?)
The only reason for using option-L is to shorten line length to prevent line
wrap. Given that the server now makes the situation worse by changing
option-L to a comma, maybe we should stop using option-L in posts, unless it
is something the admins are willing to fix.
Or maybe the server can be configured to allow these characters like the
good old days? List admin(s) what say ye?
JR