Two weeks with Vim
soledadpenades.com
Two weeks with Vim
1–10 of 37 posts
Re: Two weeks with Vim
#2> I was more of an Emacs person
Are there really any benefit of switching from Emacs to Vim? I was under the impression that both editors were pretty much interchangeable.
Re: Two weeks with Vim
#3I am a wordstar guy, I started with CP/M...
For years I enjoyed Borland products, they used Wordstar key bindings.
And then one day it stopped working. I simply had to use the mouse.
I was shocked.
It took me years to recover. I hated it.
Call me a masochist, a few years ago I tried Emacs, it was the only editor with syntax enlighting for Ruby at the time.
Except it was not working, or at least it was not working for me.
I had learned a little bit of lisp however, so it was not a total waste of time.
A few ago I was so frustrated with my editor (Notepad++), that I decided to give Vim a try.
Well... I am french. I can tell you that using Vim with a french keyboard is hell. That, plus copy/paste with the mouse working erratically (that is: more or less depending on the current "mode")... I quickly got frustrated again.
And then, boom, my netbook's hard drive goes back to his creator and I am forced to switch to my Linux netbook. No more Notepad++ there. I am back with SciTe.
Now my friends, may be you will understand it better when I will tell you a little secret I am sligthly ashamed of:
My project is mainly ONE big file, almost 12 000 lines of code, even the CSS that I used in in it.
Just one big file.
Heaven.
I wish I had seen the ligth before.
All I miss is a little post processor tool, with which I could define "sections" in my big file. Sections that it will dispatch into their own little files.
And when I will move to git, I will write it, and I will make it "bidirectortional", so that I can fetch back changed files, fetch them back into my BIG file that is.
One big file. Simplicity.
Don't worry, be happy.
Re: Two weeks with Vim
#4I am a wordstar guy, I started with CP/M... For years I enjoyed Borland products, they used Wordstar key bindings. And then one day it stopped working. I simply had to use the mouse. I was shocked. It took me years to recover. I hated it. Call me a masochist, a few years ago I tried Emacs, it was the only editor with syntax enlighting for Ruby at the time. Except it was not working, or at least it was not working for…
Uh? I thought the purpose of splitting code between different files was simplicity.
Re: Two weeks with Vim
#5> I was more of an Emacs person Are there really any benefit of switching from Emacs to Vim? I was under the impression that both editors were pretty much interchangeable.
We were taught basic programming with Emacs, connecting to an HP-UX machine. So we really didn't know much Emacs anyway :-)
Re: Two weeks with Vim
#6I am a wordstar guy, I started with CP/M... For years I enjoyed Borland products, they used Wordstar key bindings. And then one day it stopped working. I simply had to use the mouse. I was shocked. It took me years to recover. I hated it. Call me a masochist, a few years ago I tried Emacs, it was the only editor with syntax enlighting for Ruby at the time. Except it was not working, or at least it was not working for…
Uh? I thought the purpose of splitting code between different files was simplicity .
It's a lie.
The true reason is purely historical.
Editor where just TOO SLOW to handle big files (on DOS they often were limited to 64kb, if not less)
Please note that I love "modular code", hence the notion of "sections" in my big file.
To clarify: I love to edit one big file, but for other purposes I definitely need small ones.
What I am basically proposing is that it is easier to edit multiple files from within a single window/buffer. But there exist no editors that do that AFAIK
I am not the only one, see this Python tool for Vim: http://coliveira.net/software/editing-multiple-files-in-a-si...
Re: Two weeks with Vim
#7Earlier quoted context omitted.
Uh? I thought the purpose of splitting code between different files was simplicity .
It's a lie. The true reason is purely historical. Editor where just TOO SLOW to handle big files (on DOS they often were limited to 64kb, if not less) Please note that I love "modular code", hence the notion of "sections" in my big file. To clarify: I love to edit one big file, but for other purposes I definitely need small ones. What I am basically proposing is that it is easier to edit multiple files from within a…
I too like to have code from multiple logical sections of my projects visible on the same screen at times.
Splitting windows in vim works nicely for this purpose.
Re: Two weeks with Vim
#8Earlier quoted context omitted.
It's a lie. The true reason is purely historical. Editor where just TOO SLOW to handle big files (on DOS they often were limited to 64kb, if not less) Please note that I love "modular code", hence the notion of "sections" in my big file. To clarify: I love to edit one big file, but for other purposes I definitely need small ones. What I am basically proposing is that it is easier to edit multiple files from within a…
I too like to have code from multiple logical sections of my projects visible on the same screen at times. Splitting windows in vim works nicely for this purpose.
I can see how that would be useful, but I have a question. If you do edits in both windows, how do you save them? Do you just save in one window and reload the other?
Re: Two weeks with Vim
#9Earlier quoted context omitted.
I too like to have code from multiple logical sections of my projects visible on the same screen at times. Splitting windows in vim works nicely for this purpose.
I can see how that would be useful, but I have a question. If you do edits in both windows, how do you save them? Do you just save in one window and reload the other?
In vim, when you have the same file open in different windows any changes immediately appear in the other window. They are the same buffer, there are just two windows to it.
You can see this by opening a file, and hitting " " to split the window. Do some editing and you'll see it in both places. ":ls" will show only one buffer. And if you have display of the buffer state visible, when you ":w" all the windows will update to say they were saved.
Re: Two weeks with Vim
#10I am a wordstar guy, I started with CP/M... For years I enjoyed Borland products, they used Wordstar key bindings. And then one day it stopped working. I simply had to use the mouse. I was shocked. It took me years to recover. I hated it. Call me a masochist, a few years ago I tried Emacs, it was the only editor with syntax enlighting for Ruby at the time. Except it was not working, or at least it was not working for…
Upvoted because it's in interesting idea. But man, you're crazy :)