 as part of a series, be sure to check out the link in the description to the full playlist. And we've been working with Vim here, just going over some, not necessarily beginner stuff, not necessarily advanced stuff, somewhere in the middle stuff. And today we're gonna be looking a little bit more at auto-completion. So let's go ahead and again, this is our file structure here. Again, index file, JavaScript folder with some JavaScripts and then some subfolders, blah, blah, blah. I'm going to go into the Vim index file. Again, be sure to watch previous videos before you watch this one, because we're going to be glossing over some stuff that we've already gone over. But you may remember that we worked on some auto-complete stuff. So right now I'm in this file, so I should be able to do something like type in sc and hit ctrl N, and it'll auto-complete based on words that have already been typed inside this folder or this file. And if there's a more than one match, it will give you this dropdown menu, like if I did s, you can see it says script and also source for the script source there. That's great, but lots of times, especially when you're working with programming, whether it be c and you have a bunch of library files or Python or you're working in an HTML file and you're gonna be writing some JavaScript and you're gonna have some functions you're gonna be calling from another JavaScript file, even though this is the wrong link here since we moved it. Let's go ahead and open up our main.js file. So I say find main.js and I get to enter. Oh, I gotta save what I'm working on here before I switch files. And now both will be open. At the same time, they're both being Vim's buffers. And so again, main.js. This is our main.js. So you can see we have the cool function, the bad function and the better function. Let's go ahead and do B and go back to our index. So now both are open. If I call an LS down here, you can see that it lists both those files as being open. It also lists where I am in each file. So let's say that we're working in here and I want to use that bad function or the better function. Well, now that they're both open in the buffer, I can. I can come in here and I can type in BE control N and it will type out that function for me because it's auto completing based on all files I have in buffers. I can type in BA and hit control N and it'll be bad function. And again, if there's more than one option, if I just hit B and I hit control N, it tells me body, it tells me better, it tells me bad function. So I can pick which one I want and body's just because it's, you know, that's not a function. That's a tag here in my HTML file. There's also the cool file or cool function. And if I was to go back, backspace a bit, you'll see that it's showing me options here, CO, which I just typed, but it shows me the cool function and also inside that file, I call the console function for JavaScript. But it also lists what file you're pulling it from, which is convenient if there's more than one file. Maybe I have, you know, some words used in different files and I wanna make sure I'm grabbing from the right one for this project. But that's it. I just wanted to show you that that once you have files opened up in a buffer, in fact, let's just open up another one. So I'm gonna say find JS and I'm gonna hit tab and I'm gonna choose this test.js, that's right. You do have to save, whoops, save what you're working on before you move to another one, which is a good idea. You don't wanna accidentally close out without making your changes. Find JS and we will call our test JS file. And here I have a Linux function. I'm just giving these functions random names. So let's go ahead and move back and there's different ways to move back and forth between these files. We'll get into in future tutorials. I'm just gonna type in the name and autocomplete for tab index. And again, if I list out all the open buffers, you can see them all listed there. And now I'm coming here and I can type in L control N and you can see log from main JS or the Linux function from test JS. And again, it doesn't know that this is a function. It's just looking for words that have been typed previously, strings I should say. So I'm gonna go ahead and choose that. So I hope you found this useful. So yeah, it's the same autocomplete we used before, except for instead just searching the current file we're in, it's autocompleting based on all files we have open in the current buffers. I do thank you for watching. If you did enjoy this video and you enjoyed my videos regularly, think about becoming a supporter over at patreon.com. That's patreon.com forward slash mail x1000. There's a link in the description of that as well as a link to my website, filmsbychrist.com. That's Chris the K. You can also support me there with my PayPal link at my site. You can also search through all the videos from both my YouTube channels. And if you can't support financially, be sure to like, share, subscribe and comment. I really do appreciate it. And I thank you for watching. As always, I hope that you have.