I wonder why the headline and other gradient title are images. Why not a text with linear-gradient and background-clip?
I'm not really good at css though, so there's that.
81–90 of 265 posts
I wonder why the headline and other gradient title are images. Why not a text with linear-gradient and background-clip?
I'm not really good at css though, so there's that.
I love projects that popularize vim. But I think this one might be in a way too early stage to justify the pricing (assuming those 8 lessons are all there is).
There are actually 34 lessons right now (you can see the lessons if you click on the chapters to expand them).
Please let me know if there are topics that you want to see, I wanna add what people want to learn!
This is the wrong way to go, if the UI is so bad it requires a course, then the problem is clearly the tool.
If you're using a tool for 8 hours a day, everyday, for years, you won't be a beginner for very long.
The program must be optimized for the people who are going to use it for thousands of hours. Not for the users who are heard about vim yesterday.
I tried out vim for a month or so. I did enjoy using it, although I'm not sure if using vim just feels more productive because you press more keys to do the same thing. However multi-cursor editing and cutting whole lines in modern editors is way more conducive to my workflow and eventually stopped using vim. Do vim users know if there was anything like Select next occurrence in vim? Feature discovery is not one of v…
I tried out vim for a month or so. I did enjoy using it, although I'm not sure if using vim just feels more productive because you press more keys to do the same thing. However multi-cursor editing and cutting whole lines in modern editors is way more conducive to my workflow and eventually stopped using vim. Do vim users know if there was anything like Select next occurrence in vim? Feature discovery is not one of v…
Type : and write `%s/user/account/g`.
Although you won't get a real-time preview and will only see the changes after they've happened, unless you use a bunch of extensions(I use nvim).
I tried out vim for a month or so. I did enjoy using it, although I'm not sure if using vim just feels more productive because you press more keys to do the same thing. However multi-cursor editing and cutting whole lines in modern editors is way more conducive to my workflow and eventually stopped using vim. Do vim users know if there was anything like Select next occurrence in vim? Feature discovery is not one of v…
I really want to like vim and I love some things about it, like the ability to move chunks about with only the keyboard. But so many things about it kill me. Like, why can't I hit right at the end of a line, and move to the next line? Who thinks that is a good idea? Also, why do I have to have a special mode to insert things? Having to change modes just seems so complex and unintuitive. And why does the help system n…
> why can't I hit right at the end of a line, and move to the next line? I know this is probably something that sounds like someone too far down the rabbit-hole to see where they came from, but I'm not sure why you'd want to do that. The horizontal movement is probably adjacent to the vertical movement on your keyboard. Just use the appropriate movement to get where you want to go? > Also, why do I have to have a spe…
You're absolutely right. You do sound far down the rabbit hole! I am used to being able to hold down the right key and traverse my entire document, as far as I like. Why would I want to stop at the end of a line? Any time I'm editing multiline text - like, say, English - that is essentially arbitrary.
The regular keyboard... right... but what if there were some kind of special key that could be pressed to issue controls? Why is that worse than having a special key that goes into control mode? This is analogous to having caps lock, but no shift key.
Again, you're right, I don't want to do anything new. Why would I? I want to get on with my job. If the response to my complaints is "the problem is with you, my son", without any idea of the ultimate benefits I might gain from changing, then yeah, I'll pass. Honestly, this applies not just to you, but to all the responses below... they're all like "if you try it, one day you will understand". That's probably what people say about Morris Dancing.
Earlier quoted context omitted.
This article might go a bit over your head if you just started using vim, but I found it to be very helpful for typical multiline/multifile editing tasks in vim: https://bluz71.github.io/2019/03/11/find-replace-helpers-for...
I am aware that I could extend vim with all the missing features, but that seems error-prone and not worth the time investment, since other editors have them out-of-the-box.
But I remember having your stand point when I first started to try to get into vim and getting to where I am now definitely took a lot of invested time. Wether the advantages of vim are worth your time you have to decide for yourself and it seems like you did that already.
*interactive paid course. That should be disclosed above the fold, methinks.
I used vimtutor and openvim to get started, and they're fantastic free resources.
It was only when I couldn't find something to fix my specific problem that I stated in the top comment, did I start building this.
This is the wrong way to go, if the UI is so bad it requires a course, then the problem is clearly the tool.
It can also be a boon. One of the things some vim users like is always being able to discover something new, after using it for years. I'm not really in this camp though, I would prefer vim commands to somehow be more "discoverable". Much easier said than done, though.