21–30 of 74 posts
Have you written anywhere---or would care to expand here---why you have stuck with Vim over NeoVim? I ask because I have done the same. I made a couple of attempts to switch to nvim the last of which was abandon just over a month ago. Just curious! I have a very hard time articulating what I like more about Vim other than simply it just suits me better (which isn't an interesting answer).
> sensible defaults > a tabline on top I don't have anything against all these "default configurations" for vim (even though I'm struggling to imagine, why the kind of person who doesn't want to configure vim himself would choose vim in the first place), but this line just made me chuckle.
How do you split if ctrl+w is cut word instead?
> sensible defaults > a tabline on top I don't have anything against all these "default configurations" for vim (even though I'm struggling to imagine, why the kind of person who doesn't want to configure vim himself would choose vim in the first place), but this line just made me chuckle.
I will say that the "tab" line is a super useful feature. For anyone not using it, look into it! Hint: you don't have to use it for tabs at all. It's a great place to stick any persistent info that is global to the current Vim instance. And of course you can tweak it to conditionally display whatever you want. Much like this repo does, when I did a lot of pairing at my last job, I stuck the current file name up there because that is where my coworkers were used to looking.
the whole point of vi is no key chording so no carpel tunnel. hard pass, thanks.
But yes, calling these defaults "sensible" isn't the best idea. You could certainly make a case for some sensible vim defaults, but these ain't it (even though I like some of them).
One thing that always bothers me. If I open the same file twice in Vim, how can I make Vim take over the other session?
> sensible defaults > a tabline on top I don't have anything against all these "default configurations" for vim (even though I'm struggling to imagine, why the kind of person who doesn't want to configure vim himself would choose vim in the first place), but this line just made me chuckle.
As pointed out in other comments, the vimrc isn't really the key part of this project. Of course, calling these "sensible defaults" is maybe a bit antagonistic, even if it wasn't meant that way, and draws too much attention to it. I will say that the "tab" line is a super useful feature. For anyone not using it, look into it! Hint: you don't have to use it for tabs at all. It's a great place to stick any persistent i…
It's a bit of a joke, it's intended to make you laugh like when I say to go buy an OLED screen instead of commenting out a specific line :)
But TBH it's only half a joke: I think not supporting selection with Shift and Control+Shift+Arrows may drive intermediate users away.
> I will say that the "tab" line is a super useful feature
Absolutely! Like you, I've also noticed the tabline (and the line numbers) helps when I'm showing files to other people.
Even if everything else I consider sensible defaults (rainbows! emacs/readline like chording shortcuts everywhere! selection with the arrows, shift and control!) doesn't popular, I hope the tabline with X,Y coordinates and hex position will.
Hey csdvrx, Have you written anywhere---or would care to expand here---why you have stuck with Vim over NeoVim? I ask because I have done the same. I made a couple of attempts to switch to nvim the last of which was abandon just over a month ago. Just curious! I have a very hard time articulating what I like more about Vim other than simply it just suits me better (which isn't an interesting answer).
Wow that's a very personal question! I'll try to answer the best I can!
I like retrocomputing and hacking, especially for Christmas: I want to write things I can share, that'll mix old stuff and new stuff, and that will make people smile - call it the spirit of Christmas or whatever. My 2022 Christmas project was to write a web server in perl, exposing the whole C:\ drive, just for fun.
perl, vim, bash (etc) are old, so they are stable and available everywhere: other things equal, I think doing the same with neovim might have had less impact.
Also I think it's better and more satisfying to make existing tools work the way you want (ex: I want images in my terminal without moving to another terminal!), instead of moving to other tools when your existing tools can't do something you want. I believe it's the true spirit of hacking.
> i have done the same. I made a couple of attempts to switch to nvim the last of which was abandon just over a month ago.
TBH I never really tried neovim, maybe because I like the start screen of vim? The idea of doing something for orphans may be cheezy, but I really like the message!
Also why did you attempt to switch to neovim? I don't feel any limitation in vim. I'd be curious to know why you tried.
I felt them in tmux (lack of sixel support) or bash (incomplete history file), but instead of doing the sensible thing such as using zsh within kitty like everyone else, I spent some time to have tmux intercept and transcode sixel sequences into "ascii art" (https://github.com/csdvrx/sixel-tmux/) have bash save commands start and stop time in a sqlite database (https://github.com/csdvrx/bash-timestamping-sqlite)
> I have a very hard time articulating what I like more about Vim other than simply it just suits me better (which isn't an interesting answer).
I see what you mean. I didn't like zsh when I tried it last time I tried to move to Linux on the desktop. I liked hyprland - it sealed the whole linux-on-the-desktop deal. It "suits me better", but it's new so I think (or I hope?) it's not just by weird interest in retrocomputing that makes me prefer bash+vim to zsh+neovim :)
> sensible defaults > a tabline on top I don't have anything against all these "default configurations" for vim (even though I'm struggling to imagine, why the kind of person who doesn't want to configure vim himself would choose vim in the first place), but this line just made me chuckle.
Yeah, I don't think "sensible defaults" is correct. More like "my defaults". How do you split if ctrl+w is cut word instead?
Before I tell you how, I want to tell you the 2 reasons why I don't like splitting with Ctrl-W: 1) because I think Ctrl-W should the same thing as on readline or emacs 2) because even if existing uses of Ctrl-W were removed from the picture, splitting with Ctrl-W use 3 keys. Why use 3 keys when you can use 2?
I like short sequences, and chording, and there are many 2 keys sequences that are free to use if you know where to look for: I prefer to use what can only be done with MOK sequences, because these sequences are more likely to have a degree of redundancy.
For example, Ctrl-I duplicates Tab: if you use a MOK you can have Tab do something (indent) while Ctrl-I does something else (jump in the edit history). Ctrl-I is "free to use" without limiting function, because keyboards generally have a Tab key. These are "sensible defaults", because most people do that in other editors.
My splits are mapped to MOK sequences (Ctrl-; Ctrl-' Ctrl-\ Ctrl-/ Ctrl-`) but I've thought it may not be a good idea because 1) it's more unusual and 2) I rarely use split in vim so I don't think I can make an educated choice besides having Ctrl-T start a new tab (like it does on a browser), so I've left them out: I've just left the "echo" part.
If splitting is important to you, and you want to try out these MOKs, search for "echomsg.*was hit" and bind your windows split around line 256. I would like to know what you think of these. I may trust your judgement more than mine, if only because I don't use splits much in vim.
If you think these MOKs does the job for you, and if you think splits are important, let me know and I'll add the split mappings to the defaults for the next release (EOY, it may include a CuteBash)
Earlier quoted context omitted.
Yeah, I don't think "sensible defaults" is correct. More like "my defaults". How do you split if ctrl+w is cut word instead?
> How do you split if ctrl+w is cut word instead? Before I tell you how, I want to tell you the 2 reasons why I don't like splitting with Ctrl-W: 1) because I think Ctrl-W should the same thing as on readline or emacs 2) because even if existing uses of Ctrl-W were removed from the picture, splitting with Ctrl-W use 3 keys. Why use 3 keys when you can use 2? I like short sequences, and chording, and there are many 2…
I think there probably are some things you can do in vim that the vast majority would agree with. But I think you've gone a wee bit too far into just making it your preferences. I totally get your logic by the way, I'm just not convinced it's strong enough to be considered a "sensible default" ;).
You're not wrong that it's 3 keys instead of 2, but I find it makes sense. Ctrl-w puts you in (w)indow management mode and then you split (v)ertically or (h)orizontally. I don't split often enough that it matters. I do remap ctrl-w+h/j/k/l to just ctrl+h/j/k/l since I do move around in my splits that saving a keypress does matter.
> My splits are mapped to MOK sequences (Ctrl-; Ctrl-' Ctrl-\ Ctrl-/ Ctrl-`)
They make no sense to me. I have no idea what any of those key combos do.
FWIW, I see you said that it was a bit of a joke in another comment. Maybe I'm just grumpy because I'm sick during the holiday season :(.
Also for what it's worth, the general idea is super cool. I love seeing all the cool things cosmo enables
Earlier quoted context omitted.
Yeah, I don't think "sensible defaults" is correct. More like "my defaults". How do you split if ctrl+w is cut word instead?
> How do you split if ctrl+w is cut word instead? Before I tell you how, I want to tell you the 2 reasons why I don't like splitting with Ctrl-W: 1) because I think Ctrl-W should the same thing as on readline or emacs 2) because even if existing uses of Ctrl-W were removed from the picture, splitting with Ctrl-W use 3 keys. Why use 3 keys when you can use 2? I like short sequences, and chording, and there are many 2…
OK, but as a vim user you would switch readline to vim mode and never look back ;)