From: Bernard D. <bde...@us...> - 2019-06-23 08:07:43
|
I can restore the old behaviour and have Alpha ask whether spurious eols should be fixed. If they are not, I can't guarantee that the Cocoa text engine or the AlphaTcl editing procs will function properly. And anyway at saving time, all eols are eventually converted to some type. Or should I introduce some sort of warning too to warn the user and offer to save *as is* instead of silently converting the eols. Concerning the accidental inclusion of foreign eols during a paste operation, there is this old bug report (posted by you in 2009) in the AlphaX Bugzilla: [Bug 1836](http://alphatcl.sourceforge.net/bugzilla/Bug_1836.html). The fix mentionned there is currently disabled in the new Alpha. Do you think it is right to systematically convert foreign eols contained in a pasted text or is that also a potential data loss ? --- ** [tickets:#216] Alpha No Longer Warns about Inconsistent Line Terminations (Line Endings)** **Status:** open **Created:** Sun Jun 23, 2019 02:15 AM UTC by jwq **Last Updated:** Sun Jun 23, 2019 07:24 AM UTC **Owner:** nobody I have files which *somehow* have mixed line ending markers. When these are opened in Alpha: 1. Alpha does not display the inconsistent line termination warning (it does display a wrap paragraph warning). 2. Alpha's window substitutes '\n' for '\r' so that a regexp search fails to find the '\r' characters which are present in the file. It would be great to have this fixed. --- Sent from sourceforge.net because alp...@li... is subscribed to https://sourceforge.net/p/alphacocoa/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list. |