Earlier quoted context omitted.
Notepad++ (Windows, 2003) / gedit (GNOME, 1998) / kwrite/kate (KDE, 2001) all existed in 2008 and are totally fine basic text editors for source code. I remember editing PHP in a more obscure editor (SciTE, 1999) on Windows in the early 2000s.
Most of all those are gui based, when running a small Slackware setup without X none of those are available.
20 Years of Vim
41–50 of 81 posts
Re: 20 Years of Vim
#42Cool tool! I had to double check because I thought Vim was much older. Indeed, Vim goes back to 1991 ( https://en.wikipedia.org/wiki/Vim_(text_editor) ). This is a great view of the last 20 years of Vim.
Vim in '95 was a breath of fresh air: improved feature set over plain vi and still zippy.
nvi and vile were two names that spring to mind, but I know there were others.
Looks like vile itself started in 1992:
Re: 20 Years of Vim
#43Can we do the same thing for X11? (Turn it into something new while maintaining its spirit.)
Re: 20 Years of Vim
#44Earlier quoted context omitted.
I really can't recommend Drew Neil's resources enough. The vimcasts¹ series are great if you're the sort of person who likes videos to learn with, and both his books are excellent²³. [The books may appear to be getting a little long in the tooth, but their contents are still very applicable to today's usage.] My own "trick" for improving my vim usage was to start mapping things to that have better replacements, it is…
Thanks! Now I'm curious what is bad about hjkl movements :)
However, my reasoning is the same as noted in echelon's reply. There are often far better ways to move around as described in ":h text-objects" and ":h motion.txt" more generally.
Re: 20 Years of Vim
#45I've been using it for 29 years now.
The last 20 years don't mean anything; the Vim codebase is too much of a dumpster fire for anything significant to happen in that time span.
They had to fork an entire parallel command set to implement "location lists" (new in Vim 7, I think) which are exactly like the "quickfix list". Most of the difference are that location list commands start with l, wheras quickfix list commands start with c. Your keybinding to go to the next quickfix item doesn't work in a location list because it uses :cn^M, but the location list wants :ln^M or whatever. The only explanation for this ridiculous state of affairs must be that it was too difficult to extend quickfix lists to do the things that location lists do. Once you get into the Vim codebase, that will not be surprising.
Vim's visual editing semantics assumes that you have a block cursor, and that that the character covered by the cursor is included in a visual selection. This is not so nice when you switch your terminal to an I-beam (or vertical line) cursor, which references between characters. If the cursor is to the left of the selection start, it includes the character to the left of the cursor too. I-beam semantics allows for a zero-length selection, whereas in block semantics, there is always at least one character in the selection, which is the one under the cursor. I-beam semantics is virtually what pretty much all GUI editors do, including the text widget in Firefox I'm using now to type this.
A bunch of years ago I looked into what it would take to have a flag in Vim to flip to I-beam semantics for selection. Gack! I estimated a month of full time work. Numerous places in the code would have to change in ways where you're not sure what side effect they will have elsewhere.
Re: 20 Years of Vim
#46Earlier quoted context omitted.
Most of all those are gui based, when running a small Slackware setup without X none of those are available.
They're all GUIs. Most people using computers in the late 2000s were using GUIs, not X-less Slackware. You asked what "normal" was -- this is normal.
Re: 20 Years of Vim
#47Earlier quoted context omitted.
Notepad++ (Windows, 2003) / gedit (GNOME, 1998) / kwrite/kate (KDE, 2001) all existed in 2008 and are totally fine basic text editors for source code. I remember editing PHP in a more obscure editor (SciTE, 1999) on Windows in the early 2000s.
Most of all those are gui based, when running a small Slackware setup without X none of those are available.
Re: 20 Years of Vim
#48Earlier quoted context omitted.
I really can't recommend Drew Neil's resources enough. The vimcasts¹ series are great if you're the sort of person who likes videos to learn with, and both his books are excellent²³. [The books may appear to be getting a little long in the tooth, but their contents are still very applicable to today's usage.] My own "trick" for improving my vim usage was to start mapping things to that have better replacements, it is…
Thanks! Now I'm curious what is bad about hjkl movements :)
Re: 20 Years of Vim
#49Re: 20 Years of Vim
#50Earlier quoted context omitted.
I’d imagine most people’s first impression would be Notepad on windows- I wouldn’t count Word or even WordPad.
I bet you are right. But, I also think there’s enough leeway in the idea of “using a tool” to not be surprised that somebody doesn’t count a one-off use of notepad. And I think there must exist at least some people who really never used notepad. Nowadays I only assume someone between, like, 30 and 50 will inherently have to have used Windows at some point. Outside that range, you might get graybeards who were around…