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

41–50 of 141 posts

Re: Vico Editor (Mac text editor)

#41

Post by [deleted] »

avolcano wrote: post #23
fbuilesv wrote: post #21

Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file. Is people doing something else with tabs that…

Tabs are nice if you are programming just a couple files, or several files from different locations. Any more than that, and I agree that they're far too unwieldy. Vico also has an open files dropdown, and, of course, a folder explorer, as well as Cmd-T.

[deleted]

Re: Vico Editor (Mac text editor)

#42

Post by thaumaturgy »

thurn wrote: post #37
thaumaturgy wrote: post #36

> You need Mac OS X 10.6.6 to run it. sigh . No joy for PPC users, again. This is a huge part of why I'm not sticking with Apple hardware again once I replace my laptop.

Personally, I tend to think that an overly dogmatic commitment to backwards compatibility does more harm than the benefit produced by supporting a tiny minority of users with five year old hardware. Backward compatibility is the enemy of elegance. Just look at C++ or the x86 instruction set to see examples of that.

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 switch everything over to their new A-series hardware.

I have certain investments in my current development system, too, like the early-model SSD that has made it possible for me to haul this thing around in the car to client appointments every day for the last couple of years.

I'm just sick of having perfectly good hardware that gets aged out of being able to run text editors. Yesterday, I discovered I can't run pianobar (easily) anymore because the Pandora protocol changed, MacPorts appears to be dead, and homebrew is Intel-only. (There is a PPC fork of the Intel version of homebrew, but the documentation for it is all pulled directly from the Intel fork, and I'm completely stumped at how to actually get it to work.)

On top of all that, I get to enjoy the economics of owning a device whose secondary market is falling off a cliff.

Anybody's welcome to point out all the benefits of this kind of situation -- the longevity of Apple hardware, the supposed lower TCO -- or the fact that I should be budgeting a certain amount every year towards new hardware anyway, but it's not likely to change the fact that I've been through this one too many times now and it's just not something that, to me, is worth continuing to hassle with.

Re: Vico Editor (Mac text editor)

#43

Post by 5l »

zyfo wrote: post #25
fbuilesv wrote: post #21

Am I the only person who thinks that tabs don't scale in editors used for programming? I tend to have a lot of files opened at the same time (currently at 143 in Emacs) and I can quickly switch to any of these with a couple of keystrokes. Most of the Textmate users I've seen don't even care about the tabs in the editor, they just press Cmd-T and type the name of the file. Is people doing something else with tabs that…

Why do you have 143 files open at the same time? Personally I use some (2-7?) buffers in vim and cycle through them. When I don't anticipate editing a file for a while I close that buffer.

I've found that it's usually as fast to use the Vim Command-T plugin to switch files even once they're opened than it is to switch back to that buffer directly.

Main exception being the alternate buffer for which I have a quick shortcut - (, - being set to ,) The consequence is I usually have piles of buffers open at once.

Edit: sjs puts it better above. Having to think 'is this file already opened or not' and then using that information to determine the command you use to switch to it is rather annoying.

Re: Vico Editor (Mac text editor)

#44

Post by jarin »

beck5 wrote: post #29
jarin wrote: post #20

Earlier quoted context omitted.

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.

your right and I have seen my percentage time on vim get higher an higher over the months, but thats from persistance. Its slow progress because I mainly work in eclipse and the vim plugins aren't 100% great for me. Vim is just hard work getting going, e.g. in HTML I like to have the closing tag automatically done for me which im sure vim can do but i've just not had chance to look into. There are 100 other small thi…

Yeah, I'm sure there's something for it but I took the lazy programmer's road of just using Haml and Sass for everything.

Re: Vico Editor (Mac text editor)

#45

Post by rawsyntax »

fbuilesv wrote: post #27
zyfo wrote: post #25

Earlier quoted context omitted.

Why do you have 143 files open at the same time? Personally I use some (2-7?) buffers in vim and cycle through them. When I don't anticipate editing a file for a while I close that buffer.

My editor has been opened for 2-3 weeks now so I just keep piling the files from all the different projects. I prefer typing 'C-x b [strat]' to opening '~/dev/projects/something_else/lib/strategy.rb' but it might just be the way I'm used to working.

Leaving emacs open makes it more IDE like, the stuff you were working on last is still loaded. Instead of having to quit and then find all those files again. I work the same way as you. Tabs for any large number of buffers would be a nightmare

Re: Vico Editor (Mac text editor)

#46

Post by albertzeyer »

So sad that this is closed source. It looks very nice but I feel very uncomfortable knowing that if there are any issues which bug or annoy me or things I would like to have but which do not exist yet, I can do nothing about it.

Re: Vico Editor (Mac text editor)

#47

Post by tednaleid »

Nice start, looks like a nice bridge to Vim for textmate users.

It's missing a few of the basic vim movement commands (which I have on a wallpaper I put together http://naleid.com/blog/2010/10/04/vim-movement-shortcuts-wal...), but has most of the big ones. The ones I use quite a bit that don't seem implemented are:

C-d - half page down

C-u - half page up

ge/gE - go to the end of the previous word (you do have e/E for next word)

( - previous sentence

) - next sentence

Re: Vico Editor (Mac text editor)

#49

Post by jarin »

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

Re: Vico Editor (Mac text editor)

#50

Post by tednaleid »

hieronymusN wrote: post #13

I've already made the switch to MacVim using Janus - https://github.com/carlhuda/janus but Vico could be interesting. The biggest win here, like with Sublime Text 2, is being able to split the window into panes, which is something I've wanted in TextMate for years. However, what I really want is to be able to open a different file in the other panes, not the same file I have open. [edit] Okay just figured out how to…

I have this in my .vimrc (https://bitbucket.org/tednaleid/vimrc/src):

nnoremap vl

nnoremap sj

This makes cmd-d open up a vertical split, and cmd-shift-d open up a horizontal one. Same keybindings as in iterm2 and I find them easier than the chording that you have to do normally (which makes my hand feel like it's using emacs).

Post reply on HN