But I love both vim and milk 🥺🥺🥺

alias vim=nvim
alias vi=nvim
alias nano=nvim
alias emacs=nvim
alias code=nvim

export EDITOR=nvim
export VISUAL=nvim
export PAGER=nvim

Huh? Mod creator removed their own mod? I heard that Nexus Mods removed their mod.

Build from source

Same error for me

genZdong is two blocks down, pal

Pop!_OS is a good idea 😁 to get a call from the top of the stairs 🙀 a little trollsorting 💀 Fucking FBI honeypot 🍯

Hi

Anything that can be used for illegal activities will be used for illegal activities

AHAHAHAH

I made a comment about how “neovim” doesn’t fit in 8 across but found right after that there was a comment like that already

deleted by creator

I’m ok with paying for quality foss software, as long as the payment method is available from any country in the world. PERIOD. no exceptions. Not even North Korea should be prohibited from paying.

Ads are a hard turnoff though. There is no place for ads in my world.

Dialogue with my friends, we were contemplating about how we first met. Funny that none of us remembered how we met.

Sorry if it comes out robotic, since I don’t use stow myself I just opened the manual and parsed it for you.

You manually create the repo of packages ONCE and then use stow to deploy them without having to link stuff manually every time.

As for “what’s it doing for me”, stow is just a generic deployment script that somebody else has written for you. You can just as well create your own and do it your way.

I personally used to have a bash script with one custom function “symlink” that error checked the linking process and a list of target/destination under the function.

Now I’m trying to code a python script similar to stow that works with packages of configs but instead of recreating paths inside the package you just provide a json file with target/destination for each file in the package.

Both of my ways have same shortcoming as stow: you have to do some manual work before the script can kick in.

Hopefully my messages have been helpful.

Recreating a path to original locations is a way to configure stow.

You can utilize bash to automate it. Mkdir can create entire trees in a single command.

After links were created you start using your configured software.

It’s a link farm built using a packaging system. You put your configs into a “package” and then link said package where it belongs.

Git is useful not as a combination for stow, but a standalone way to version control your configs.

For nonidentical devices you create additional packages prefixed with specific device name. You don’t need to link all packages at once with stow, pass a name of a package to link it alone.

😭😭😭

Idk I’m so used to working in terminal I don’t really notice that. For my eyes, it’s smooth enough

Fair

But… Neovim is smooth, fast and snappy 😭

There are gpu accelerated terminal emulators… Not sure what you mean by remote development though.