- COTEDITOR 2.O UPDATE
- COTEDITOR 2.O MANUAL
- COTEDITOR 2.O CODE
Toggling comment-out/uncomment Selected text can now be comment-outed/uncommented via short-cut (⌘/) or Typing or opening files in particular with large files.
Drastic performance improvements In this change, we made efforts to identify a bunch of performanceīottlenecks and to resolve them. You can also export & distribute your own themes. Highlights on CotEditor 2.0 Coloring theme feature You can now store your color settings in themes and switch them easily. Fix an issue that new added row in file drop setting occasionally disappear immediately.Fix an issue that navigation/status bars are shown for a moment on window creation even they are set as hidden.
COTEDITOR 2.O UPDATE
Fix an issue that current line highlight didn't update after font size change. Fix an issue that word selection didn't expand correctly under the specific conditions. Fix an issue that contents property of document property could’t be set via AppleScript. Fix an issue that text view scrolls to the opposite side when line number view is dragged. Fix an issue that text kerning was too narrow with non-antialiasing text (thanks to tsawada2-san). Fix an issue that quoted texts and block comments at the end of document weren't highlighted. Fix an issue that syntax style mapping conflict tables were always blank. Fix an issue that syntax style validator didn't warn about keywords duplication that were newly added. Fix an issue that some objects couldn't be handled via JavaScript for Automation on Yosemite. Fix an issue that the application could crash after closing split view. Fix an issue that new documents couldn't occasionally be saved with an extension that is automatically added from syntax definition. Update documents for scripting with AppleScript. Change default value for “Comment always from line head” option to enable. Display an alert if the opening file is larger than 100 MB. Add “Create Bug Report…” action to the Help menu. Hint: Use #!/usr/bin/osascript -l JavaScript for shebang to run script as Yosemite's JavaScript for Automation. Add “js“ extension to CotEditor script type. Introduce new AppleScript commands comment out and uncomment for selection object. Currently, there is no way to replace with line endings other than the document line ending and this is the same behavior as the previous CotEditor.What’s new on CotEditor 2.0.1 - CotEditor CotEditor CotEditor 2.0.1 On the other hand, regarding the text replacing with, all line endings even ones defined as a metacharacter like \r are assumed as the document line ending. If you want to handle line endings strictly on search, use the regular expression instead. That is, for example, if you search a document in which the line endings are LF for a string containing the CR line ending as a (non-regular expression) text search, all line endings in the search string will be assumed as LF. COTEDITOR 2.O CODE
In the normal textual search and replace, the line endings contain in the search or replace string are assumed as the same as the line ending code used in the document being searched for.
The line ending handling in user scripts for the Script menu. Custom definitions in the syntax style definitions. Replacement definitions for the multiple replacements. The following user settings require attention to the line ending handling: Those user settings require change by the user. Scripts and regular expression patterns that assume only LF as line endings may not behave as intended in documents with other line endings than LF on CotEditor 4.2.0 and later. \R is the metacharacter defined in the CUI regular expression engine, which is used in CotEditor and matches any of a newline character, such as U+000A (LF), U+000B, U+000C, U+000D (CR), U+0085, U+2028, U+2029, or the sequence of U+000D U+000A (CRLF). If you want your documents to match any line endings regardless of the line ending character, use \R instead of \n. From CotEditor 4.2.0 on, \n matches only the line endings of which document actually uses LF as the line ending. Whole Release Notes for CotEditor 4.2.0 Line ending code in the regular expression patternīecause the previous CotEditor handled all line ending codes as LF internally, \n could be used in regular expression patterns to recognize newlines, regardless of the actual line endings in the document. You can find the same information in the Help bundled to CotEditor 4.2.0. This page summarizes points that users should be aware of regarding this specification change. COTEDITOR 2.O MANUAL
Therefore, users, especially those who have used earlier versions, require awareness of this change and may need manual migration for some settings. From version 4.2.0, the actual line ending codes in document files are treated as they are. Prior to version 4.2.0, all line ending codes were internally treated as LF ( U+000A). Important changes on CotEditor 4.2 - CotEditor CotEditor
0 kommentar(er)
