Would Vico also have support for emacs keybindings? :-)
Vico Editor (Mac text editor)
31–40 of 141 posts
Re: Vico Editor (Mac text editor)
#32Very nice work.
I've been getting irritated with emacs'... rough edges a lot lately and am tempted to scratch my own itch with an emacs slant :-)
Re: Vico Editor (Mac text editor)
#33Excellent. A quick note: :q when in split-pane mode will close everything, not just the current active buffer.
Re: Vico Editor (Mac text editor)
#34I 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.
Re: Vico Editor (Mac text editor)
#35Earlier quoted context omitted.
Yes, but what happens when development on this closed source editor dries up? It looks like a great app, but I'm still leery of basing something as important as my editor on a closed code base again. There are also some great alternatives out there, notably Redcar, which is both open and full of Textmate like features.
If you are capable of switching editors, what does it matter if it's closed source or not? This adversity to switching editors is a common trait in programmers I can't quite understand. We programmers learn new things all the time, it's part of what makes us excel in our profession. And yet, adopting a new editor is apparently extremely hard.
Because learning new editors takes away from time we could be coding.
Re: Vico Editor (Mac text editor)
#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.
Re: Vico Editor (Mac text editor)
#37> 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.
Re: Vico Editor (Mac text editor)
#38> 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.
But there is no notion of "Apple hardware" anymore. Apple has been using the "PC architecture" for quite a few years. You can run Mac OS on "PC" hardware just fine if you wish. Many people have done / are doing this; see www.hackint0sh.org for more information.
Re: Vico Editor (Mac text editor)
#39Am 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 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" programs.
Once you free yourself from this list of things that are "open" (whatever that means) you simply stop caring about the number of items in what is effectively just a "recently visited" list. What value is there in killing those buffers if there's no list for them to clutter? (yes there are lists of buffers in Emacs but you only see them if you want to)
In that light here's my answer to your question: Because he hasn't exited his editor and the number of "open files" has no significance or impact on workflow. While you're deciding whether or not to close a file and trying to anticipate when you may edit it next he's already moved on to editing the next thing.
Re: Vico Editor (Mac text editor)
#40Ok, 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 launching (like the "mate" or "mvim" commands)
- Ability to edit tmbundles within the app
- Downloading tmbundles seems to duplicate tab triggers
- Snippets still use hard tabs even if you've selected space-based indentation (soft tabs)
- Hitting backspace when you are using soft tabs and are in the "indentation part of the line" should go back that number of spaces instead of just one
Vico is like so close to becoming my main editor, if only these things are fixed. As others have said, a .vimrc-style config would be cool (as would a :retab command), but those aren't deal breakers for me like the above things are.