Learn Emacs/Slime the Hard way (from 10 years of Vim) [closed] - vim

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
This is a genuine question, not intended to start a flame war.
I've used Vim for over 10 years; watching people use Emacs/Slime ... has made me decide to learn Emacs/Slime.
I want to get up to speed as fast as quickly:
there are a bunch of "finger macros" I instinctively do -- I want to figure out the equivalent in Emacs/Slime & retrain myself
Since I'm familiar with Clojure, writing elisp config won't be a problem (minus the dynamic vars sometimes)
What should I be reading / memorizing?
EDIT: note, I have tried VimClojure, and decided I like Slime/Swank more.

When I learn a new editor (or tool of any kind), the moment I don't know how to do something (e.g. Save a File), I google up the answer, then do it, 3x over.
In Emacs, save a file is C-x C-s. Every time you cannot remember what it is, do it three times. It'll become second nature VERY quickly.
Never "cheat" because you're in a rush, or feeling lazy. Research each command as you need it, and repeat it until it becomes a "finger macro".

Related

How to select the programming language? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I have a navigation providing interface, where in given the starting and destination points, and somehow the map of the street maybe, then the path is chosen based on the map, i.e. if a way is found then move in the direction, or if some blockage is found, or if the path will not lead to the desired destination then check for some other path maybe.
Now what programming language will be the best for it? I have worked with C only till now. Will it be all right for me to code in C only?
Is there anything else I need to take care before I take up this project? (Apart from the implementation issues).
Thanks.
Look, the best thing to do is to just start coding and find out. If you are not experienced, it's better to use the language you're familiar with rather than learn a new one. At the end of the day, you can achieve most tasks with most languages.
It's not so much what you use but how you use it.
In terms of the path-finding implementation, you might want to start by looking at A-star or Dijkstra's algorithm.

How do I become proficient with the terminal? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
As a programming novice, I often run into trouble when trying to install packages, use virtualenv, and basically do anything even mildly complex using the command line.
What are some good references out there to help me UNDERSTAND things like my path, environment, shell scripts, etc?
Basically, I'm tired of copying and pasting. I want to really understand what's going on.
Thanks!
I used Linux in a Nutshell by O'Reilly. It helps you get past the initial beginners stage. Obviously there are a ton more links and tutorials, lists of keystrokes online, easily found with a Google search, but this will help you get going, and nice to read when you are on the bus or at lunch or whatever, to give you some ideas you might not just happen on in normal everyday life.

for nothing but editing and navigating text as quickly as possible: is there any reason to prefer vim over vim emulations in emacs? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
EDIT:
1. Let's not make this a general vim/emacs debate. I know some people prefer standard emacs, I want a modal input system.
2. When I say Vim emulation, I mean something like http://www.emacswiki.org/emacs/Evil or http://www.emacswiki.org/emacs/Vimpulse
I edit a lot of text (as in notes, mail etc.), I want to do it as quickly as possible. It seems like a good idea to learn how to use something more complicated than text edit. Is there any significant difference between the potential speed of an experienced user of either vim or vim emulation X in emacs?
I suggest you pick one of them (VIM/emacs), mixing them (with a plugin) isn't something that great since I wouldn't expect all the functionality to be there.
Besides that, I don't see any reason why you would need such a thing. VIM or Emacs are pretty fast without one emulating the other, so you wouldn't need such a plugin.
If you really want to be extra fast, I know VIM has a really nice plugin called EasyMotion (watch a quick video of it in action from nettuts).
Edit: #Daimrod said Emacs has a similar plugin called ace-jump-mode
Go for Emacs. You'll have the VIM keys if you prefer that and you'll also have the power of Emacs at your disposal.

Is Vim really that good? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I had to see what all the fuss was about Vim so tried it out for a little while; built a whole site in it. In the end I decided I was less productive.
So my question is: is Vim really that good or is it just one of those ultra-nerdy things people want to use so they can say: "I use Vim". Vim seems a little cumbersome to me. I know it's supposed to be lean but I think the years development and the mass of contributes has left it untidy. Am I wrong? Should I stick it out with Vim? What are the advantages of Vim?
How I learn to stop worrying and love VIM
Hope this helps.

What modal editors are available aside from vi/vim? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Another question asked why there are so few non-vi modal editors. A few of the comments in that question mentioned other modal editors in passing, but I think that it would be useful to develop a more comprehensive list. Searching for this information on Google is difficult, as vim-related information tends to drown out everything else.
A few items to get things rolling:
Divascheme (From the previously mentioned question)
Ed (According to this)
There have been many Non-vi modal editors over the years. Many of them tied to a single operating system.
WordStar, edlin, and ISPF come to mind. Also EDIT from the HDOS system. There are probably at least a dozen others named EDIT or it's variants.
I've never tried it, but AFAIK Emacs has a plugin to emulate vi's modal editing.
Elvis is one of these editors.
Also, nvi could count as one.

Resources