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

141–150 of 198 posts

Re: CotEditor – Text Editor for OS X

#141

Post by benrhughes »

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.

Out of the box, ctrl-[ is mapped to escape. It took me about a week to un-learn Esc, but it is one of the better vim decisions I've made (along with mapping j to gj and k to gk, and mapping tab to :bnext).

Re: CotEditor – Text Editor for OS X

#142

Post by veidr »

mkhalil wrote: post #138
veidr wrote: post #121

Earlier quoted context omitted.

That is great to hear! I bought Chocolat (a purchase mainly instigated by the hilarious "the demo expired so it still works, but only with Comic Sans font" gimmick). And I even sent friends screenshots[1] raving about its completion UI. But... Chocolat didn't really stick for me, with the plethora of editors I already use. Even though it's good. I would definitely revisit it, if it got extensible completion. [1]: htt…

Is there an app that does have that autocomplete in the screen shot?

Yes! That is indeed a real screenshot of an editor for OS X, called Chocolat[1].

The alextgordon fellow that replied to me upthread is one of the principal people behind it.

[1]: http://chocolatapp.com

Re: CotEditor – Text Editor for OS X

#143

Post by dunham »

Dewie wrote: post #87
Retra wrote: post #22

Earlier quoted context omitted.

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.

Vim inherited the keyboard mapping from vi. vi was designed on a QWERTY (American) keyboard, but the particular terminal that the author used had arrows printed on the hjkl keycaps.

More information at: http://en.wikipedia.org/wiki/Vi

Re: CotEditor – Text Editor for OS X

#144

Post by nodivbyzero »

tuhdo wrote: post #131
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…

You can be quickly productive with my mini manual: http://tuhdo.github.io/emacs-tutor.html . If you write C++, did you check my C/C++ guide: http://tuhdo.github.io/c-ide.html . A few demos: - code navigation: jump to anywhere instantly. DEMO: http://tuhdo.github.io/static/c-ide/helm-gtags-jump-dwim.gif . - code completion: context-sensitve completion. DEMO: http://tuhdo.github.io/static/c-ide/semantic-boost-demo.gif…

Very impressive. How long did it take to create all those demos?

Re: CotEditor – Text Editor for OS X

#145

Post by Void_ »

stormbrew wrote: post #63
Void_ wrote: post #8

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

Nooo, is it any good? Sorry pushing sarcasm too far. Of course I have to agree on that one.

Re: CotEditor – Text Editor for OS X

#146

Post by tuhdo »

nodivbyzero wrote: post #144
tuhdo wrote: post #131

Earlier quoted context omitted.

You can be quickly productive with my mini manual: http://tuhdo.github.io/emacs-tutor.html . If you write C++, did you check my C/C++ guide: http://tuhdo.github.io/c-ide.html . A few demos: - code navigation: jump to anywhere instantly. DEMO: http://tuhdo.github.io/static/c-ide/helm-gtags-jump-dwim.gif . - code completion: context-sensitve completion. DEMO: http://tuhdo.github.io/static/c-ide/semantic-boost-demo.gif…

Very impressive. How long did it take to create all those demos?

I collected them from my guides: http://tuhdo.github.io/, so it's quick if you don't account the time to write the guides.

Re: CotEditor – Text Editor for OS X

#147

Post by cooper12 »

vectorpush wrote: post #44
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…

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.

You underestimate the difficulty of compiling from source for the layman. OSX and Windows do not come with compilers out of the box. The user would have to install them and the proper environment for them first. (cygwin, etc...) Then they'd have to get and install the dependencies properly. Finally they'd have to figure out the proper incantations to make it compile, which if you've never done it before can be extremely daunting. How on earth was I supposed to know what an LPATH is or pkgconfig? Not to mention the extremely verbose and scary looking errors from gcc.

That's assuming that it's a program written in C/C++. If it's another language then you might have another huge hurdle to go through. (Properly installing Go in my PATH took me a while). That's also assuming they don't rely on IDE-specific make files. A lot of the time OSX applications rely on xcode project files. The other day I was trying to compile an Android app before realizing that it was written in a language by Adobe which required the purchase of a full suite.

Open source can be really limiting if the developer doesn't make an effort to document the build process well and doesn't use open tools to create the product.

Re: CotEditor – Text Editor for OS X

#148

Post by illicium »

kerr23 wrote: post #80
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…

I moved between being a life-long vi/vim'er to Sublime and more recently Atom. I only use Atom for coding and vim for just about everything else. The most difficult part for me is that i'll open a file in vim and then consciously go "no" and fire it up in one of the other editors. Why? because I like to keep my vim more clean. I've seen some of the really complex vim configs out there and they just didn't "do it" for…

"syntax on" is complex?

Re: CotEditor – Text Editor for OS X

#150

Post by Derbasti »

The second screen shows the search an replace dialogue, which is its own floating window. I can't tell from the screen shot whether it is modal.

Anyway, search is an incredibly crucial feature for navigation. It has to be fast, and non-modal. Even having it in a separate screen is suspect in my book.

Post reply on HN