Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CotEditor – Text Editor for OS X

coteditor.com

Post reply on HN
Print view View original

51–60 of 198 posts

Re: CotEditor – Text Editor for OS X

#51

Post by girvo »

Zelphyr wrote: post #21
wldcordeiro wrote: post #12

Earlier quoted context omitted.

Sublime Text has an excellent plugin called Vintageous that gives you a lot of Vim's functionality with some of the niceties of Sublime, worth a shot if you felt crippled by it.

I have never had success with these plugins. I apparently begin typing too fast after hitting Escape and invariably the plugin can't handle that and it enters things like ":w" as text instead of processing it as a command. Obviously this isn't a problem in Vi/Vim proper but all of the Vi*-style plugins for any of the IDE's or editors I've tried--from Eclipse to Sublime--always break.

The best one I've used that has worked near-perfectly for me is Vi-emulation mode in Komodo IDE. It's really impressively done, to be honest.

Re: CotEditor – Text Editor for OS X

#52

Post by archagon »

agilebyte wrote: post #41
archagon wrote: post #35

This is awesome, but I wish developers would charge for polished, full-featured software like this. The people who made this probably have full-time jobs; meanwhile, independent developers who want to break into this niche now have to compete with "free". This results in a market ruled by large corporations that can "subsidize" free software via the spare time of their employees. Maybe I'm just being too grouchy. Thi…

Well maybe that is the point. The developers get paid, somehow, so why do they need to get even more money? This way more people can use their software because it is free. (I don't know the developers)

Yeah. I can definitely see the point. I also realize that open source software is often a political statement, and good for that. But at the same time, I want to see a world where a developer could earn money from making cool applications like this without relying on a large corporation for the bulk of their paycheck. It's what the free-to-play app store model is coalescing to, and I don't like it.

Re: CotEditor – Text Editor for OS X

#53

Post by grmarcil »

Retra wrote: post #22
cdata wrote: post #18

Earlier 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.

You can also remap Esc to jj by adding the following to your vimrc

inoremap jj

The hjkl thing feels weird for a long time but it becomes natural after a while. I used Sublime for a long time with the Vintage plugin (vim like movements and some other vim features) before moving to Vim and that made the transition much easier for me. I still like Sublime, but Vim's full integration with the terminal environment is hard to beat.

Re: CotEditor – Text Editor for OS X

#55

Post by VieElm »

mholt wrote: post #54

Nice, but in the kind of dev work I do, I need to be able to work with text files that are hundreds of MB, even over a GB, in size, and CotEditor chokes on 200 MB text files...

Why do you have text files that are 200MB? Why don't you separate that into multiple files? 200MB of text? Moby Dick is 1MB in plain text. The Holy Bible is like 4MB in plain text. What is in your files? I think you may be doing something wrong.

Re: CotEditor – Text Editor for OS X

#56

Post by jackmaney »

VieElm wrote: post #55
mholt wrote: post #54

Nice, but in the kind of dev work I do, I need to be able to work with text files that are hundreds of MB, even over a GB, in size, and CotEditor chokes on 200 MB text files...

Why do you have text files that are 200MB? Why don't you separate that into multiple files? 200MB of text? Moby Dick is 1MB in plain text. The Holy Bible is like 4MB in plain text. What is in your files? I think you may be doing something wrong.

    s/I think you may be/You are/
No single file of source code should ever be even close to 200MB, and no data file (CSV, XML, etc) of that size should be manually edited in a text editor.

Wrong tool for the wrong job.

Re: CotEditor – Text Editor for OS X

#57

Post by agilebyte »

archagon wrote: post #52
agilebyte wrote: post #41

Earlier quoted context omitted.

Well maybe that is the point. The developers get paid, somehow, so why do they need to get even more money? This way more people can use their software because it is free. (I don't know the developers)

Yeah. I can definitely see the point. I also realize that open source software is often a political statement, and good for that. But at the same time, I want to see a world where a developer could earn money from making cool applications like this without relying on a large corporation for the bulk of their paycheck. It's what the free-to-play app store model is coalescing to, and I don't like it.

Sure, but what is a right price? Shall all code editors cost the same and differentiate on features? Otherwise it seems to me like a race to the bottom where CotEditor people charge $30 and indie developer charges $25. So what about the next indie developer then? $20?

And yes you are right, as developers we tend to publish useful stuff more often for free than not. But maybe it stems from our inability to market cool applications so that we get money for them.

Re: CotEditor – Text Editor for OS X

#58

Post by weavie »

bbcbasic wrote: post #50
fdsary wrote: post #5

I'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…

RE: Has anyone succeeded in deliberately changing editors? I am currently learning Vim and using it with the NERDTree plugin as a fairly nice environment to write Ruby on Rails code in my spare time. It is also nice as I have a low power PC running ubuntu in a virtualbox. So Eclipse is a no-no anyway. At work I use Visual Studio but have a Vim open all the time for where the Vim advantages outweigh the visual studio…

You may find vsVim (https://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3...) useful. I can't use Visual Studio without it.

Re: CotEditor – Text Editor for OS X

#59

Post by mholt »

VieElm wrote: post #55
mholt wrote: post #54

Nice, but in the kind of dev work I do, I need to be able to work with text files that are hundreds of MB, even over a GB, in size, and CotEditor chokes on 200 MB text files...

Why do you have text files that are 200MB? Why don't you separate that into multiple files? 200MB of text? Moby Dick is 1MB in plain text. The Holy Bible is like 4MB in plain text. What is in your files? I think you may be doing something wrong.

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 same size ranges, and it's out of our control. But when the service bombs, we need to be able to prove to them that their file is malformed, and if it isn't, we have to fix our data or our code. That usually requires inspection of text files.

But that's all beside the point. This looks like a fine source editor for basic needs, but I wouldn't consider it a tool for general "plain-text" editing like it says on the site.

Re: CotEditor – Text Editor for OS X

#60

Post by mholt »

jackmaney wrote: post #56
VieElm wrote: post #55

Earlier quoted context omitted.

Why do you have text files that are 200MB? Why don't you separate that into multiple files? 200MB of text? Moby Dick is 1MB in plain text. The Holy Bible is like 4MB in plain text. What is in your files? I think you may be doing something wrong.

s/I think you may be/You are/ No single file of source code should ever be even close to 200MB, and no data file (CSV, XML, etc) of that size should be manually edited in a text editor. Wrong tool for the wrong job.

I never said it was a source code file.
Post reply on HN