Live data from Hacker News

CotEditor – Text Editor for OS X

coteditor.com

61–70 of 198 posts

Re: CotEditor – Text Editor for OS X

#61
post #55
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.

I'd put money on that being a data file.

Re: CotEditor – Text Editor for OS X

#62
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.

This sed substitution thing seems to be a cute trend to express "fixed that for you". It goes nicely with programmer's propensity to express themselves in needlessly arcane ways.

Re: CotEditor – Text Editor for OS X

#63
post #8

Not sure why the site advertises "Just for OS X" as if it's a feature.

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?

Re: CotEditor – Text Editor for OS X

#65
post #58

Earlier quoted context omitted.

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.

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.

Re: CotEditor – Text Editor for OS X

#66
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.

Vim and Emacs are quite well-suited for textual manipulation of very large data files. Use of a macro is a very pleasant alternative to piping the file through sed/awk/etc. for a once-off transform.

Re: CotEditor – Text Editor for OS X

#67
post #55
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.

Whenever possible, the machine should accommodate the human rather than vice versa. Viewing a 200MB file in a text editor is not an outrageous request on a modern computer. Maybe he's not working optimally, but why should he change if his approach should work, and does work fine with other tools?

Re: CotEditor – Text Editor for OS X

#68

Earlier quoted context omitted.

I'm not really sure how practical it is to sell an open-source desktop application; anyone can compile and run it for free and the 'sell support' model usually isn't viable for something as simple as a text editor.

How about releasing the source without any of the art assets or interface nibs? Full benefit of open source while still providing high value for money. (Sure, the geeks will go and create their own assets, but it won't be the same.)

Interesting idea, but I suspect that the first quality fork that provides a 'good-enough' version of those missing assets out of the box would start to steal the limelight from the main project, especially because the fork could pull in all the bug fixes and new features from upstream.

Re: CotEditor – Text Editor for OS X

#69
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…

It's pretty easy actually. Just get drunk one night and bash your head against a wall few times. This will make you forget all the keyboard shortcuts and you're free to learn a new text editor.

Since learning VIM I have got (with no addition effort) better at learning keyboard shortcuts for all kinds of different apps I use. Vim (or Emacs etc.) literally makes you smarter.

I now use Ctrl-V or "+p depending in gViom depending on what mood I am in. Nice to have a choice.

Re: CotEditor – Text Editor for OS X

#70
post #29

Earlier quoted context omitted.

Atom is strange to me, it seems like a less familiar Sublime Text with no real distinguishing features.

The distinguishing feature is it's horribly slow with large files. The performance is an order of magnitude slower than sublime text. And it doesn't auto-save unsaved work if it closes. Both deal breakers for me.

unfortunately you are right. Hopefully these issues will be solved soon, I liked the core ideas of atom.
Post reply on HN