The tiny ESC key on the MBA 11 keyboard is just a bit harder to hit than might be desired for a vi user.
the professor uses Ubuntu and he uses XEmacs.. but cant seem to find any way of getting that install on OSX, will try port in a bit
XEmacs runs in OSX without Ubuntuthe professor uses Ubuntu and he uses XEmacs.. but cant seem to find any way of getting that install on OSX, will try port in a bit
the professor uses Ubuntu and he uses XEmacs.. but cant seem to find any way of getting that install on OSX, will try port in a bit
emacs-app @23.3, Revision 4 (aqua, editors)
Description: GNU Emacs is a self-documenting, customizable, extensible real-time display editor. This is a port of the latest GNU Emacs source to the OpenStep (or NeXTstep) APIs, as implemented by Cocoa on OS X. It differs from Carbon ports of GNU Emacs in that it makes a more concerted attempt from the ground up to follow OS X desktop and UI conventions.
Homepage: http://www.gnu.org/software/emacs/
Library Dependencies: ncurses
Platforms: darwin
License: GPL-3+
Variants:
fullscreen: Add fullscreen patch
inline: Add inline patch from MacEmacsJP
jpfont: Add Japanese font patch from MacEmacsJP
patches: Add all patches: fullscreen, inline and jpfont * requires fullscreen inline jpfont
universal: Build for multiple architectures
If you're going to install emacs via port, you don't want xemacs, you want emacs-app.
but still not sure which one should i learn...
continue to use what makes you productive
If there was a definitive answer that one is better than the other, then one would have faded off into history.
i been using nano for a while and it works fine.. so not sure why to switch
If it works fine for you, then there is no reason to switch.
There's no reason to solve problems that don't exist. If you were having some problem with nano, such as you ended up on a Unix system that didn't have ncurses, then learning to use vi would be worthwhile. Or as an exercise in broadening your perspective, learning vi might be worthwhile. But as a problem that needs a solution, for you, there isn't a problem, so you already have the solution.
The most efficient software design possible is none at all.
The fastest and most bug-free code is the code you don't write.
The shortest learning curve is the one you don't have to go through.
which one is easier to learn?
which one is easier to learn?
I used Northgate Omnikey keyboards for years with Windows PCs, and later essentially the same thing now branded as Avant Stellar, made by Creative Vision Technologies. And, having learned to type (as it was called back then, not "to keyboard") on a manual typewriter, I swore I'd only give up the manual feedback of such mechanical-switch keyboards when they were pried out of my cold, dead hands.Which is why I assign the useless caps lock key to be a CTRL key. I also normally use a 23 year old Northgate Omnikey keyboard which has CTRL to the left of the A and also has an easily reachable ESC key for VI users.
Do the following:
- Open terminal
- Type vimtutor
- Go through the whole tutorial (couple of hours?)
- Type emacs
- Type C-h t (hold ctrl, press h, release both, then type t)
- Go through the tutorial
That will give you a feel for the basics of each one, and I think at that point, you will probably form your own opinion about which you prefer to use.
I do agree with you that having the Ctrl key next to the 'A' is the sensible location. (It was one of IBM's several redesigns of their keyboards that forced everybody to follow suit.) But on the Mac, the Cmd key is essential. Where do you map that on your Omnikey?
But both vim and emacs are included in OS X.
And, IMHO, those both suck.
That is why I download/compile/install the original vi code and/or nvi.
If you like the built in editors, thats great. I don't, so I look to other options. That is what makes Unix great IMHO, choices.