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

Vico Editor (Mac text editor)

vicoapp.com

Post reply on HN
Print view View original

91–100 of 141 posts

Re: Vico Editor (Mac text editor)

#91

Post by nlh »

Another comment that this looks great! I've been using MacVim as my main editor and love it, but totally appreciate the polish of Vico -- looks wonderful.

My wishlist, right off the bat (note I know some of this might be unreasonable, but that's why it's a wishlist ;) Mostly centered around a quick transition from MavVim to Vico...

* Would be excellent if I could import a vim colorscheme

* Would be excellent if it could read/use my .vimrc

* Would be _excellent_ if it supported vim bundles/add-ons, but I know that's basically asking for vim :)

* In editing a Ruby file, I wrote 'def' it colored and indented my second line, but only colored my 'end' -- didn't outdent it properly. Small annoyance. Also would be great if I could configure it to auto-insert an 'end' for every 'def' or 'Class' or 'if' etc....

Keep up the great work and get an RSS feed up on your blog so we can keep track of updates...

Re: Vico Editor (Mac text editor)

#92

Post by thaumaturgy »

jarin wrote: post #69
thaumaturgy wrote: post #42

Earlier quoted context omitted.

I do agree to some extent. On the other hand, I've been using Apple hardware off-and-on again since the MC68030; I already went through this with the 68k->PPC transition, then again with the introduction of the PPC750 series processors, then again with the PPC->Intel transition. At this point, I fully expect that if I were to buy an Intel series Apple system in the next couple of years, shortly afterward Apple would…

It's understandable that you wouldn't want to buy a new Mac just before they do a hardware refresh or something, but come on. At some point you need a new computer. Somehow I doubt that Apple is going to do some kind of crazy Intel -> Atom transition anytime soon, and even if they do they'll support Intel for at least a few years. You sound like my friend who won't upgrade to an HDTV "because the price keeps dropping…

Like I said, it's not necessarily a rational decision, it's just that the pain of being invested into a platform only to have it become completely unsupported way before I'm ready to spend money on the Next! Great! New! Thing! has been burned into my brain. It's just not a hassle I need to deal with, not when I'm equally comfortable in Windows, Debian, or Mac.

It might be understandable if this was some kind of resource-hungry multimedia application, but a text editor? Like you say, "come on".

Also, Apple is notorious for wanting to own as much of their vertical as possible. They hate dealing with other companies for critical components, especially processors. They've become quite good at the processor transition at this point, and now that they own their own microprocessor and are using it in all of their mobile devices -- and touting the superior benefits of their processor every chance they get -- I'd be willing to make a pretty big bet that moving at least their entire laptop line over to the A series processors is already on their development roadmap.

I think the writing's on the proverbial wall and, like I said, I'm just tired of getting caught by it every time it happens.

Re: Vico Editor (Mac text editor)

#93

Post by wyclif »

jpcx01 wrote: post #75

Looks great. I try just about every one of these new options. Kodapp was my last one, but it didnt last (back on textmate). I'll give this a try as well. It looks like it has even greater potential. TextMate is a joke. Nothing worse than missed opportunity. Such a huge community behind it and MacroMates seems completely incapable of providing a new release.

http://wastm2released.com/

MacroMates totally dropped the ball. What a shame. Everybody was suing TextMate, everyone was talking about it a few years ago, and they didn't capitalise on that.

Re: Vico Editor (Mac text editor)

#94

Post by deffibaugh »

navs wrote: post #90
deffibaugh wrote: post #34

I really want to try out vim and tiling wm setup. Is this a good place to get my feet wet? I was going to just set up VM of ArchLinux.

I experimented with an Archbang + wmii setup on my netbook for a few months. I don't see how this app comes close to emulating that experience. I suggest a VM setup.

I think I am going to setup a VM with this. I really want to try the real thing. If it runs well enough in the VM I might just do all my development in and use the host OSX for everyday tasks.

I am looking into getting into Android development. Is it worth doing it without using Eclipse?

Re: Vico Editor (Mac text editor)

#95

Post by mdemare »

jarin wrote: post #20
beck5 wrote: post #3

This could be very good, I am still trying to find my perfect editor Vim's learning curve & interface means occasionally I just open up sublimeText2/TextMate. Great to see split views are there from the start.

I don't want to take anything away from Vico (because so far it is pretty rad), but if you stick with MacVim you eventually start using TextMate less and less until you just stop altogether. For me, it took a good 3 months or so. The last holdout was using TextMate for formatting JSON output, but I found a Chrome plugin for that.

That has never happened to me - I only use MacVim when I need the power features. I'd love to have vim-style modal editing, but my eyes overrule my hands. MacVim is simply too ugly.

Re: Vico Editor (Mac text editor)

#96

Post by nickmerwin »

jarin wrote: post #49
jarin wrote: post #40

Ok, so playing with this for a bit I just realized how much I miss TextMate's tab triggers. I hope this project goes forward, especially if it either a) gets open sourced, or b) gets other developers on board. I'd hate to see it go the TextMate route of getting popular and then taking forever for new releases to come out because the sole developer gets burnt out. A few things that would be nice: - Command line launch…

One down, 4 to go :) ln -s /Applications/Vico.app/Contents/MacOS/vicotool /usr/local/bin/vico

Close! It'd still be great to be able pass to a file or directory path to have opened...

Re: Vico Editor (Mac text editor)

#97

Post by wahnfrieden »

pakeha wrote: post #83
llimllib wrote: post #58

:q in a split should close that split, not kill the whole app. I can't use this app until he fixes that, because that shortcut is hardwired into my brain. There's definitely some neat stuff in there, though.

It took me a while to figure out that the way to close a split is ^Wc Probably because I'm not a huge vim user, and was only previously aware of the :q syntax you mentioned.

Funny, I use ^Wq for that.

Re: Vico Editor (Mac text editor)

#98

Post by jarin »

nickmerwin wrote: post #96
jarin wrote: post #49

Earlier quoted context omitted.

One down, 4 to go :) ln -s /Applications/Vico.app/Contents/MacOS/vicotool /usr/local/bin/vico

Close! It'd still be great to be able pass to a file or directory path to have opened...

It works for me:

  vico .

  vico ~/projects/jarinudom.com

Re: Vico Editor (Mac text editor)

#99

Post by defroost »

jsprinkles wrote: post #62
thirtyseven wrote: post #35

Earlier quoted context omitted.

Because learning new editors takes away from time we could be coding.

Learning new tools to use, new techniques to employ, new languages to express yourself, new environments to deploy in, new projects to hack on ... and for devops, new daemons to configure, new setups to benchmark ... these are the vast majority of a working programmer's time so switching editors is trivial in comparison. Arguing against something because it takes away coding time is a sign that you probably need to b…

I am primarily a Textmate user as I do a lot of Ruby, Rails, and web work, but a while back when I started learning Lisp I felt compelled to use Emacs. I was some of the most fun I've ever had. And I would contend that extending, customizing Emacs with .el files is a form of coding.

Re: Vico Editor (Mac text editor)

#100

Post by ujeezy »

Love it! I was seriously considering wrapping MacVim in some sort of Cocoa app with a file drawer, and I'm glad I didn't have to go down that rabbit hole. Very excited to watch this develop :)
Post reply on HN