![]() But I used Homesite in the very early days of the web and got used to that somewhat CUA/GUI style of editing when I moved to BeOS (really, I did for a while) I used Pe, the programmers' editor there, and then to the Mac and BBEdit, then TextMate, then Sublime. I'm competent in both Vim and Emacs, with a mild preference for Vim. This can only be answered through anecdote, so mine is: it's really tough. Has anyone succeeded in deliberately changing editors, even when not feeling like it's necessary? There is no way a small team can do good completion in tons of languages, but providing a great UI is totally doable. Look at Chocolat.app for what the completion UI should look like (a big, attractive complex popover view (not just a menu) with optional documentation display), but open up the actual dynamic completion itself to your users. Off-topic bonus tip for aspiring text editor authors: make an awesome autocompletion UI, but leave the indexing/autocompletion up to third party open source plugins. (Even so, I agree that it doesn't merit top billing in the window toolbar.) So yes, I think the barbaric text encodings of yesteryear are still a pain point for Japanese users. At work in Tokyo, I deal with email in these encoding (or worse - parts of the email in SJIS, with other parts in EUC). still abound.įor instance, whenever I download CSV bank or credit card data here in Japan, I always have to convert the file from one of those encodings before using it. Despite the fact that we now have UTF-8, which should be used whenever possible, legacy encodings like SJIS, EUC, etc. I can confirm that text encoding is still a real pain in Japan. ![]() That said, this definitely must have been a very good learning experience for the developer. I don't seem much here that would change people's text editor habits away from Vi, Sublime, Atom, etc. I think the developers need to put on a their business hats and figure out who the target audience is and tailor their pitch to them. They've rarely, if ever, caused me problems and I don't want to see them. Something's wrong upstream if you have to deal with these settings. Looking at the screenshots, I have to wonder why the developer chose to place the settings for line endings, encoding, and file content type in prime real estate: the top left corner. I see some features that seem to address some pain points of Japanese users, so maybe that demographic will be more interested. I can't say I will try as I don't see enough selling points to peel me away from Sublime. Clearly a lot of effort has gone into it. Please don't hesitate to report any bugs or feature requests to our issue tracker.Looks beautiful and well-designed. CJK Language FriendlyĮstimate various file encodings accurately, toggle to vertical text mode and keep its line height correctly. Incompatible CharactersĬheck and list-up the characters in your document that cannot convert into the desired encoding. Make your own macro in your favorite language, whether it is Python, Ruby, Perl, PHP, UNIX shell, AppleScript or JavaScript. Inspect Unicode character data of each selected character in your document and display them in a popover. Split a window into multiple panes to see different parts of your document at the same time. Outline MenuĮxtract specified lines with the predefined syntax, and you can jump to the corresponding line. CotEditor backups your documents automatically while editing. You don't need to lose your unsaved data anymore. You can access all your settings including syntax definitions and themes from a standard preferences window. There are no complex configuration files that require geek knowledge. Super powerful find and replace using the ICU regular expression engine. Colorize more than 50 pre-installed major languages like HTML, PHP, Python, Ruby or Markdown.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |