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

81–90 of 141 posts

Re: Vico Editor (Mac text editor)

#81

Post by johncoltrane »

thaumaturgy wrote: post #42
thurn wrote: post #37

Earlier quoted context omitted.

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…

I have a 2004 G5 with only one of the two processors working and I've had to replace my burned 512Mb ATI 9600 with the original 64 Mb GeForce FX 5200. I won't put this thing to the trash until its last breath.

On its left, there is a low end Dell PC running an up to date Ubuntu that cost me 350 € two years ago waiting for this day to come.

That said, MacPorts is still alive and kicking, the latest update was a few months ago.

Re: Vico Editor (Mac text editor)

#83

Post by pakeha »

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.

Re: Vico Editor (Mac text editor)

#85

Post by brimpa »

hieronymusN wrote: post #18
brimpa wrote: post #17

Earlier quoted context omitted.

You can use the standard vim commands to create split panes with different files. :e :vsp " for vertical split :sp " for horizontal split

Very cool. Does it have the equivalent of a .vimrc file so I can modify the leader char and make it more like my MacVim setup?

As of now it doesn't look like Vico supports the `let` command so setting with `let mapleader=','` wouldn't work.

Like so many others, I'll be keeping my eyes peeled.

Re: Vico Editor (Mac text editor)

#86

Post by losvedir »

adriand wrote: post #77
johncoltrane wrote: post #66

Earlier quoted context omitted.

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?

I suspect the reason is the same as on emacs: scrolling always occurs line by line (i.e., there is never a partial line visible at the top or bottom of the screen), whereas on most modern text editors it scrolls by pixel, so it's more of a continuous transition.

I love emacs, but this is one of the sticking points that's really been bothering me of late.

On a side note, it looks like with emacs's set-window-vscroll command, you can actually make it display a fraction of a line. Has anyone had any luck hacking this into a way to do smooth, continuous scrolling?

Re: Vico Editor (Mac text editor)

#88

Post by eykanal »

Very nice! I'm a vim novice, but I use it a lot to make quick changes to config files. Is there a good vim help resource that could be integrated in to this program for newbies like me? There are many things I like about vim, but I'm always forgetting keybindings.

Excellent program, though! I look forward to watching it as it develops further!

Re: Vico Editor (Mac text editor)

#89

Post by thaumaturgy »

daxelrod wrote: post #51
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…

I hope I'm not veering too far offtopic, but I've gotten the Homebrew PPC fork working, what problem are you having?

Sweet! I'm completely unfamiliar with Ruby, which I think is half the problem (edit: and git/github, which is probably the other half). If there's a different file(s) to download for that fork, I can't find them -- everything in the github project seems to link back to https://gist.github.com/323731, which is the Intel build (edit: e.g., the Readme.md file). I tried replacing my copy of brew with https://github.com/sceaga/homebrew/blob/powerpc/bin/brew, but that complained that it can't find brew.h ("no such file to load -- brew.h" on line 77) ... at that point, I decided that I'd spent too much time trying to get pianobar upgraded and moved on to other things.

Re: Vico Editor (Mac text editor)

#90

Post by navs »

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.
Post reply on HN