[squeak-dev] support of various line ends in trunk

Jimmie Houchin j.squeak at cyberhaus.us
Tue Nov 17 16:47:27 UTC 2009


On 11/17/2009 8:47 AM, Juan Vuletich wrote:
>
> I never talked about control chars. We were talking about line ending 
> conversions. A typical scenario is needing to edit ini files for real 
> users that are stored in a server. I need to support users with 
> Windows and Mac. And I want to leave the files as they need them. The 
> best way to do that is with the Cuis editor. Then, I'm in control.

You are doing this from Squeak?

It would seem to me to be more natural for the editing in Squeak to be 
of a single consistent line ending and then the export to your server 
into the line ending type required there.

Neither Mac nor Windows or anyone to my knowledge desire/require any 
line ending outside of their native default line ending. So I fail to 
see why this would be important in the editor and done better in the 
editor than in the export mechanism saving the edited text to a file 
whether local or network?

And in a previous email you wrote:
On 11/16/2009 4:10 PM, Juan Vuletich wrote:
 >
 > I think you got this one wrong. In Cuis, in a workspace you can tell the
 > line ending of each line (cr, lf or crlf) and you can actually type all
 > three. Please try it! Use <Enter>, <Shift-Enter> and <Cmd/Alt-Enter>.
 > This way you can edit a text file, and keep it consistent. Otherwise, if
 > you edit an existing file that was edited with a Unix or Windows editor
 > and add CRs to it it will use more than one convention, without you
 > realizing. Showing all in the same way is misleading. Different Strings
 > should look different in the editor!

I still fail to see a purpose in having more than one line ending type 
in a single document or file. It isn't natural.

And if only one type of line ending in a document/file/string.
Editing (internal) line endings does not necessarily equal export or 
external line endings.

If you have a purpose for multiple line endings in a single 
file/document/object/... I would like to know what that is.

If not, then it would seem that simply having the ability to export to a 
platform explicit version (regardless of the platform of current use) is 
a valuable thing. But should be an explicit decision not a default one.

Jimmie



More information about the Squeak-dev mailing list