![]() I think my Vim setup is probably pretty awesome, tweaked and re-tweaked through multiple iterations. I've actually put in the effort to try and customize both Emacs and Vim with all sorts of packages that add the features I miss from Sublime and predecessors. It's the advanced features that make us love our editors, but sitting down in front of a new editor and realizing you're going to need to read a tutorial just to figure out how open a file and oh God what was the key that started the tutorial again is a hurdle which, in a world with a plethora of good editors that all use standard keys we've already known for the basics, often doesn't seem like it's worth jumping through. I think it's easy for experienced Vim/Emacs jockeys to downplay how important that is. Despite the fact that I moved across five editors and three platforms, the basics - opening and saving files, simple navigation by character, line and board, using the clipboard, search/replace, and even basic navigation - were for practical purposes identical across these editors. #Coteditor tutorial mac#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). #Coteditor tutorial download#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. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |