Live data from Hacker News

Vico Editor (Mac text editor)

vicoapp.com

71–80 of 141 posts

Re: Vico Editor (Mac text editor)

#71
* The Vico "blog" does not have an RSS feed, so it's not easy to track future announcements about Vico.

* Firefox's AdBlock seems to be blocking your hotlinked Twitter icon, so there is no obvious Twitter link to follow. The "Follow Vico on Twitter" text should probably be included in your .

Re: Vico Editor (Mac text editor)

#72
post #29
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…

Try SnipMate(1) for tab-completion and autoComplPop(2) for auto-completion.

(1) http://www.vim.org/scripts/script.php?script_id=2540 (2) http://www.vim.org/scripts/script.php?script_id=1879

It took me one month and a half to stop using TextMate. Once you are accustomed to oOaAiI, rR, wWeEbB or ci( or all the rest it's very hard to open TextMate and take it seriously.

Re: Vico Editor (Mac text editor)

#73
post #55

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.

vim works on mac anyway - macvim for gvim equivalent. As far as I know there aren't any decent tiling wms for mac.

You can use dwm/awesome/wmfs & co under XQuartz, installation and configuration work almost like in Linux.

That said, I use ShiftIt(1), it's free, keyboard based and does EXACTLY what I want it to do.

(1) https://github.com/iamteem/ShiftIt

Re: Vico Editor (Mac text editor)

#74
I like the editor, but I don't like the fact that it is time limited to just 5 days. Yes I understand that you want people to download the latest and greatest for testing, it just seems wrong.

Overall it looks fantastic, but I am pretty dead set on my MacVim ways with my various plugins that it is going to be hard to get me to switch.

Re: Vico Editor (Mac text editor)

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

Re: Vico Editor (Mac text editor)

#76

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.

Vico is a Mac OS X text editor with Vim-like keybindings.

If you want to try tiling window managers + Vim, your best bet is to use MacPort to install gvim and either wmii, awesome or ion3. Other WMs worth trying are wmfs, dwm, xmonad… you'll need manual compiling though.

Re: Vico Editor (Mac text editor)

#77
post #28

Earlier quoted context omitted.

I love MacVim too, and have dropped Textmate completely. The only thing that I don't like about MacVim is that scrolling through text (vertically and especially horizontally) feels choppy compared to Textmate. When I see someone else scrolling through code in Textmate, it looks unbelievably smooth and fluid compared to what I'm used to in MacVim.

That's because scrolling with the mouse was a bit of an afterthough, I think. If you use motions, word objects and Ctrl+f/Ctrl+b you don't really notice this choppiness.

Actually I rarely use the mouse and was mainly referring to Ctrl-f/b and j/k, as well as w on long lines. I don't actively notice the choppiness until I use some other editer, but I wonder why it exists in the first place - is the rendering engine slow or something?

Re: Vico Editor (Mac text editor)

#78
post #54
post #39

Earlier quoted context omitted.

I think it's a similar phenomenon to people closing windows to free up space on the taskbar (for GUIs that have such a thing like Gnome and Windows). If you remove the list of "open" things people are free to just do what they want and let the OS worry about paging if memory fills up and all that sort of thing. It's a pleasant experience if the abstraction doesn't leak, e.g. Win98 crashing if you opened "too many" pr…

Good answer. Is there no cost whatsoever to having many buffers open? I like the simplicity of just cycling through rather than searching for whats-its-name-again - seems to be easier to remember for my fingers as well. A couple of years ago I used to keep 100s of tabs open in FF. Then I went mobile and started caring about watts. Not the same situation, but I think it influenced my few-files-open habits.

For me there is no cost, but I rarely do the cycle-through-all-tabs thing (not never but rarely). For your workflow it sounds like there is a cost. If you work on multiple projects in the same editor instance then there is a significant cost as well, e.g. you may have 5 index.html files open and when you type the desired filename you then have to choose carefully. I have encountered this when leaving Emacs open for days or weeks at a time, switching between personal and work projects.

These days I use TextMate more than Emacs and for small personal projects I like quickly switching between say the readme, makefile, code, and test with Cmd-[1-9]. If there are few files to edit tabs can be advantageous. This stuff is highly personal and dependent on workflow.

Re: Vico Editor (Mac text editor)

#79
Really nice start! I've been enjoying modal editing in Vim. One of my pain points is that I feel like I don't have a lot of control over which buffer I'm closing when I :bd or what will happen when I open a new file when selecting it in Nerdtree. Sometimes it replaces a buffer, other times it splits the window. Im sure it's me not understanding how vim works, but I seem to get the mental model in Vico a little better. Bravo!

Re: Vico Editor (Mac text editor)

#80
I'm never quite sure if all these Vim commands people rave about are any better than judicious use of the alt/option, shift, command and arrow keys with the default Mac behaviour.

Although one essential change to the defaults is to remap CapsLock to be the same as Control --see System Prefs-- and then using Control-F to move the cursor forward one. Helps you get past automatically inserted closing brackets with minimal hand movement. I find that really tedious and annoying otherwise.

Post reply on HN