Table of Contents 01:04 Introduction to .dotfiles 09:52 Managing .dotfiles with stow 22:04 Advanced layouts 26:56 Restoring .dotfiles on a new computer 29:54 Using .dotfiles of other people like themes 32:47 Crafting your own .dotfiles

Great tutorial, thanks for making this! I'll share a couple of notes of things I'll revisit, in case anyone else finds them useful 14:00 create folders and treat them as if they were the home directory. 15:29 stow -n (n stand for no) it is used to preview what it would do without actually doing it. 15:40 stow -v (v stands for verbose) 15:41 stow -S (S stands for stow) 15:44 stow -D for unstow for unlinking 16:00 target directory, in our case it's always home 16:10 stow t (t stands for target directory) 16:50 t ~ (means target directory) it's not usually taught since it's the default, but it's better to specify. 17:10 stow -vt ~ * (* stands for everything) 18:00 stow --adopt -nvt ~ * (running a test) since -n is still stating "no" 19:10 stow --adopt -vt ~ * 19:30 be careful with the --adopt flag, it's only needed at the beginning it's not needed later 20:00 showing how the original file becomes a symlink --------------- 23:16 stow -vDt ~ (insert directory) this would unlink the desired dot file,s yet it won't delete them. 24:05 stow has problems understanding slashes/for/paths 24:35 having 2 different directories. One for recording videos, one for normal use. 25:50 using ls -al in the terminal to see where symblinks are connected to. -------------- 27:00 simulating cloning dotfiles into new computer 30:00 testing someone elses dotfiles 30:05 guide to dotfile dotfiles.github.io 32:30 to test someone's dotfiles create a new directory, clone their repo and unlink the dotfiles you want to test and link it to theirs. 36:47 aliases for stow example

This is by far the best guide / tutorial about syncing dotfiles with stow out there. In all the other videos I watched they just briefly go over what stow actually does if at all and don't explain it nearly as good as you plus they don't show that many examples. So, thanks a lot for this video, now I finally understood everything I need to know about stow and can fully utilize it in my dotfiles repo! 😊👍

I just want to suggest using the "--dotfiles" option that is available since stow v2.3.0, which enables you to have much prettier filenames inside your git dotfiles repo. So you don't have to "ls -a" all of the time. 🙂

Best tutorial on stow ever!

What a great toturial, hanks for taking the time and sharing! Love that you brought up commonly used applications and didn't just create any random files. That way I was also able to learn more then just about the dotfiles.

If you adjust the playback speed to 0.75, this is by far the best stow tutorial out there ! Thank you.

great tutorial! I wish there was a Dev like You Inside Me!!

Thanks for the video. There are many other videos on this topic but after watching yours I finally understood how GNU stow works!

very well explained.. I was starting today to create my own dotfiles.. it helped me a lot and learned some other small stuff!

Thank you so much!! I watched so many videos about stow but they all confused me and you explained everything clearly!

Perfect 👍. Just what I was looking for. This helped me immensely. Thank you!

Thank you for this. Got everything working without any issues.

I just came across stow a few days ago in a couple other videos, but this was the perfect presentation of information to help me grok the tool. Thank you.

Excellent video. I'm going to start my repo with dotfiles and use stow to experiment. Greetings from Brazil!!

Thanks for this video! I'm now also kicking myself for not looking into this earlier...!

Subscribed. Thanks, mate. This video just blows my mind about what I can do with my dotfiles.

GREAT video full content and actual application. I learned a lot from this. Thank you very much!!!

Thanks dude, i was looking for this. I'm will try it.

Clean and precise tutorial, thank you!

The best tutorial I’ve watched on KZfaq! Thank you 🙏

This is gold! Thanks for the in depth look at this topic

Good job! Very well explained.

really amazing video, congratz bro! will check your other videos now :)

Finally someone I do not need to speed up to watch efficiently 😄 Very nice video full of information 👍

the best video ever to learn stow !! keep it up man !!

This is the best resource for saving dotfiles. Thank you.

Still the best GNU Stow video on youtube. Subscribed.

Awesome guide. Thanks much

Very good tutorial. Great teaching skills. Excellent job man, really impressed with all your explanations, and little tricks.

Great video. After trying out the bare repository and alias method for a while, I am setting on this way, as it is cleaner than dealing with aliases and branches for different hosts.

Nice video! Thank you so much! 🤓

very informative and fast pace ❤️ love from Tehran❤️

Thank you very much, very helpful, I was making the links manually, hhh now stow takes control

Thank you!!

Huge tks, man

Thank youu sir 😍👌

Great tutorial man! Thank you! Ok? ;)

3:28 I think it should be ls -al | grep ^\\. not ls -al | grep \\. Because the dot should be only at the begin of file names.

Once I unwittingly overwrote my init.nvim file and quit because of a faulty plugin. I knew at that moment that I fucked up and remember coming across config backup videos & repositories like this video and thinking to myself why didn't I take them seriously. I recommend everyone be a responsible dev and backup your shit. I had setup an undo dir fortunately and using 'strings path/to/undofile' could salvage all that was lost.

Very well explaination, it's covers things that others video/blog post don't cover. I have a question. So, if there are conflicts --adopt can be used and it will move the files in home dir to stow dir and symlink those files back to home dir, it's kinda replace files in stow dir with files in home dir right ?. Is there any way to replace files in home dir with files in stow dir instead? (reverse what --adopt do), it's useful if after installation or run it first time, the apps automatically create default config files and we want to replace it with the one in stow dir

Thanks for the video, its very helpful. But now I wonder how I could automate the syncing of my dotfiles to a git repo automatically if they were changed on one of my machines (without doing git add, git commit, git push manually all the time)

So what if the application downloads to the config directory, Like for instance the plugins for NVim. will they be put in the .dotfiles directory without a sym-link? Should I keep those outside the NVim directory?

Greate tutorial, easy to understand. I wanna manament window app with stow: terminal setting.json, powershell profile, and many more window app setting .... how WSL2 can do that? waiting next tutorial.

May i know how you switch screen(from terminal to vscode)? It seems very smoothly. Thanks.

Overall a great video. But WHY do you do the grep for file names? Try without | grep!

How do we push those symlinked dotfiles into github? I tried pushing one, it does not have the content of source file, but rather have the directory in it. So stow does not help with management in github but only local.

stow: ERROR: The stow directory D00M does not contain package README.md getting this at the first command, why that happens? I have the README.md in place

How are you running a virtual machine as a virtual desktop instance on Windows 10?

I used stow to create the file links but my dotfiles are not loaded. I have to go to ~ and execute source ./{filename} every time I open a new terminal. Any idea what is wrong?

Whats the name of the shell theme?

Great video, thanks ! If you could speak slower it would be easier to follow, especially for non-native English speakers. I really appreciate the outline with time-links in the video description.

thank you. I think it'll be more helpfull when simplify the work flow and slow down a little bit :)

I like the video a lot. But honestly, when you started to treat "work" and "record" in different folders "inside your dotfiles repository" everything inside me just screamed: "Use a dedicated git branch!".

thank you for the tutorial was helpful, if i could give constructive criticism, it was hard to follow, felt very random and had to re-watch many times to gather what i needed, but then again, i'm not too smart, so there's that.

A bit fast, but good work nonetheless.

You are a good instructor but you would be a great instructor if you could slow down your pace of speech. 😉

You should slow down a bit when speaking.