why are we making another editor.
In other words, exactly what someone said as someone else started working on your preferred text editor.
CotEditor – Text Editor for OS X
81–90 of 198 posts
Re: CotEditor – Text Editor for OS X
#82Earlier quoted context omitted.
Have you tried using one of those IDEs written in Java?
This isn't an IDE. The comparable type of editor that's cross platform is probably sublime. Have you tried using that?
Sublime is the best cross-platform app I've ever used. I can count on one finger the number of times I've used something that felt native on more than one platform.
Re: CotEditor – Text Editor for OS X
#83I'm pretty effective with vim, so much that other 'normal' editors like sublime & other modern gui editors make me feel a little crippled. That is a problem, because you need to be flexible about things in life. Has anyone succeeded in deliberately changing editors, even when not feeling like it's necessary? I'm especially curious how I could start using emacs, and actually get up to speed with it instead of using it…
EditPlus to jEdit to Emacs, myself.
Re: CotEditor – Text Editor for OS X
#84Re: CotEditor – Text Editor for OS X
#85Re: CotEditor – Text Editor for OS X
#86Earlier quoted context omitted.
You may find vsVim ( https://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3... ) useful. I can't use Visual Studio without it.
I tried that, but with no easy way to turn it off (without uninstalling it) it feels a bit 'in the deep end'. Once I am happy with using Vim productively I may try it. Another concern with this is pairing, as there is no easy way to turn it off. Although staying in insert mode and keeping the default bindings for VS may be OK.
it does allow you to easily default back to visual studio handling all of the commands. In fact, it's quite nice for a tweener vim user because you can have visual studio handle all the more complex keybindings that you don't recognize and just use it for the subset of commands you're comfortable with, and move from there
Re: CotEditor – Text Editor for OS X
#87Earlier quoted context omitted.
When I first broke into web development, my editors of choice were Coda, Dreamweaver and Visual Studio (I wonder if I am dating myself here). I made a mid-career move to (non-gui) Vim, mostly out of general interest. The ramp up to Vim coming from GUI-heavy editors was a long one, but I stuck with it and it was worth it for me. So, it's definitely possible to switch, you just have to be able to deal with that ramp up…
I've been trying out vim for a while, hoping to get more productive, but the fact that "hjkl" is not "jkl;" -home keys- and that I have to reach all the way across the keyboard to hit [esc] every three seconds is not helping... I pretty much use sublime text for everything these days.
> but the fact that "hjkl" is not "jkl;" -home keys-
On American keyboards, anyway. That isn't how the keys are laid out on modern Dutch keyboards, though I don't know what they were like when Vim was created.
Re: CotEditor – Text Editor for OS X
#88Looks beautiful and well-designed. Clearly a lot of effort has gone into it. I can't say I will try as I don't see enough selling points to peel me away from Sublime. I see some features that seem to address some pain points of Japanese users, so maybe that demographic will be more interested.
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. Something's wrong upstream if you have to deal with these settings. They've rarely, if ever, caused me problems and I don't want to see them. They just work 99% of the time. Maybe not so much for Japanese users.
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. I don't seem much here that would change people's text editor habits away from Vi, Sublime, Atom, etc. That said, this definitely must have been a very good learning experience for the developer.
Re: CotEditor – Text Editor for OS X
#89I'm pretty effective with vim, so much that other 'normal' editors like sublime & other modern gui editors make me feel a little crippled. That is a problem, because you need to be flexible about things in life. Has anyone succeeded in deliberately changing editors, even when not feeling like it's necessary? I'm especially curious how I could start using emacs, and actually get up to speed with it instead of using it…
I didn't so much change editors as start using multiple editors. On OS X, I regularly use vim, TextMate, and BBEdit.
I find that TextMate looks the best. I simply enjoy typing code into TextMate more than I do in vim or BBEdit. Thus, when I'm doing a stretch of writing new code, or straightforward modification of existing code, I'll probably do it in TextMate (although some days it just feels like it is a vim day or a BBEdit day).
If I need to make a lot of related changes, I'll switch to vim, and use regular expressions or I'll record a macro to repeatedly apply.
If I'm doing something like making some modification at all places that use a particular database table, I'll probably go to BBEdit. I can do a search for that table and click "find all", and it gives a separate window showing all the matches, with an editing section in the bottom part that shows whichever search result I click. This lets me easily see all the places where the table is referenced, and easily edit them, and go back and forth as needed. It works similarly with the results of a multi-file search, which makes it nice when I'm trying to understand crusty old legacy code.
If I start a work session in TextMate, and switch to vim to do something with macros, I'll probably stay there and continue editing. When I exit the editor to test the code, then I'll probably head back to TextMate. Same if I go to BBEdit for something--I'll stay there until I need something that is better in vim.
I realize I'm not making full use of the capabilities of one or more of these editors. BBEdit can certainly do most of the things vim can do, and all of the things I use vim for, for instance, but I'm fine with simply popping into vim for those things.
Re: CotEditor – Text Editor for OS X
#90Earlier quoted context omitted.
We deal with data sets that are several GB in size, and so I'm already using just a subset of the data. These files are loaded by programs into memory and serve customers via a REST API, and it's not uncommon that we have to manually inspect or change the files from time to time. Our use of large text files isn't only internal; our software also processes delimited text files for customers, and these can run into the…
Any particular reason you're not using a database?
There are several. And even if we did, you still need a well-formed text file to parse before you can insert it into the database.