5 ms·

A .vimrc is literally one file, and we've come up with lots of solutions for moving dotfiles around easily. Some jank, some not. But it is a hundred million mil

A .vimrc is literally one file, and we've come up with lots of solutions for moving dotfiles around easily. Some jank, some not. But it is a hundred million miles out of scope for vim to implement some kind of sync. That would require accounts, databases, all kinds of tedious details an OSS project does not have the resources or volunteers to do.

amelius 4y ago
I was thinking that perhaps SSH should do this the way they also pass X11 credentials around.
the_cat_kittles 4y ago
an option to have vim use a url for the vimrc?
- simplotek 4y ago
  > an option to have vim use a url for the vimrc? Is copying .vimrc whenever logging in for the first time too much work?
  - sneak 4y ago
    Yes, plus you’d need to update it on all machines on each change. Computers are perfect automation machines. Why embrace useless toil?
- rthomas6 4y ago
  git clone https://my-dotfile-repo ln my-dotfile-repo/.vimrc ~/.vimrc Done.
sneak 4y ago
> But it is a hundred million miles out of scope for vim to implement some kind of sync. This doesn’t hold true in 2022. People expect their settings to follow them around automatically.
- jrumbut 4y ago
  I don't disagree, but some of the great parts about vim are its self-sufficiency and reliability. It's awful when your editor won't open because it's trying to write a log message to a drive that was disconnected or checking for updates but the network is extremely congested. One could make a command to check some central registry (or, what the hell, maybe a .vimrc blockchain) but typing that command would be about as much work as the curl/wget/git solutions proposed elsewhere.
- jstanley 4y ago
  Not the kind of people who use vim.
  - sneak 4y ago
    This is a tautology. By this logic vim is “done” and should forever remain in stasis.
dredmorbius 4y ago
Vim can edit files over SSH. Invoke your local editor and edit the remote file. Additional benefits: no lag or delay in your buffer and editor, and you can save locally should the remote session crash. (This presumes a direct SSH connection, e.g., no bastion host, though that can be addressed via tunnelled connections.)

amelius 4y ago

I was thinking that perhaps SSH should do this the way they also pass X11 credentials around.

the_cat_kittles 4y ago

an option to have vim use a url for the vimrc?

simplotek 4y ago
> an option to have vim use a url for the vimrc? Is copying .vimrc whenever logging in for the first time too much work?
- sneak 4y ago
  Yes, plus you’d need to update it on all machines on each change. Computers are perfect automation machines. Why embrace useless toil?
rthomas6 4y ago
git clone https://my-dotfile-repo ln my-dotfile-repo/.vimrc ~/.vimrc Done.

sneak 4y ago

> But it is a hundred million miles out of scope for vim to implement some kind of sync. This doesn’t hold true in 2022. People expect their settings to follow them around automatically.

jrumbut 4y ago
I don't disagree, but some of the great parts about vim are its self-sufficiency and reliability. It's awful when your editor won't open because it's trying to write a log message to a drive that was disconnected or checking for updates but the network is extremely congested. One could make a command to check some central registry (or, what the hell, maybe a .vimrc blockchain) but typing that command would be about as much work as the curl/wget/git solutions proposed elsewhere.
jstanley 4y ago
Not the kind of people who use vim.
- sneak 4y ago
  This is a tautology. By this logic vim is “done” and should forever remain in stasis.

dredmorbius 4y ago

Vim can edit files over SSH. Invoke your local editor and edit the remote file. Additional benefits: no lag or delay in your buffer and editor, and you can save locally should the remote session crash. (This presumes a direct SSH connection, e.g., no bastion host, though that can be addressed via tunnelled connections.)