I like mini.files: it does EXCTLY what oil does (I mapped it to - too) PLUS it gives better visual context of where you’re at in new/unfamiliar projects by listing all the parent directories from the current file up to cwd / project root. It’s cool that both plugins have the same navigation and file operations patterns!
Mini.files is a godsend. It behaves exactly as i thought oil would before i used it. For some reason i would some weird errors using 'caw', the hidden file ID would appear editable in the buffer, instead of it being just the filename
Yes, I love mini.files as well. The only time I prefer to use oil is when I want to have multiple windows open to different directories so I can easily move files around. Mini.files recently added bookmarks which helps, but sometimes it’s just better to have actual windows open to edit.
File management tools and text editors are trying to solve the same problem: batch editing of text. the text just happens to be file paths in the case of file management. so if you have a powerful text editor, you automatically have a powerful file manager that's the genius insight oil.nvim and others relies on
I'm currently using NeoTree since I switched to Neovim not too long ago, and having a file tree on the left is pretty standard. But a few months back, I saw Oil on the Typecraft channel, and it feels way more Vim-like. Every time I use NeoTree, I think, "It would be easier to edit as a buffer in Oil." Definitely planning to swap NeoTree with Oil when I update my config (hopefully in 2024, hehe).
I tried oil, and it's excellent, but I'll stick with mini.files, basically the same functionality, and it uses h-j-k-l to navigate OOTB. Also, I'm using more plugins from mini library, so it fits better IMO.
I always use telescope for quickly move between files. But when i have a huge deeply nested project. I still need a file tree to frist get a general idea of the project structure, then to create a file in a deeply nested folder. I use nvim-tree and it's working great for me.
I've never understood the aversion people have to a file tree. Are there good reasons I'm missing? Personally I love Vinegar and usually have it in a popup window where I can do my filesystem modifications, then use fuzzy for navigating between existing files.
Hey TJ, Can you please move the bottom line of the NVIM up by 20-25px so, when I pause to read what you typed, TH-cam player won't bother? Plus, could you please explain `:e %:b` + TAB (I guess). What is this and how I should search these in help?
Really nice video! The bitrate was horrible, tho, not sure if it's on your side or TH-cam's side (you can see your background going crazy). Maybe you could upload in, so 4k we get better bitrate?
huh ya, that's really weird - i will see if I messed something up on my side. it looks like it happened to the last few videos, but I don't remember seeing it locally like that. Thanks for point it out
I switched back and forth a while, but it really clicked when I mapped oil to back space, so navigation is the same as Vimwiki. I use Vimwiki a lot and now navigating between files feels the same as navigating between links in my notes. It feels great to me.
Hi, huge fan and new to neovim. I think it is kind of difficult to find an updated guide for a golang specific setup, or in general, what are best practices when setting up neovim for specific languages?
i would put them in separate lua files like lua/config/mini/files.lua, and then require them indidividually in the setup with lazy that would probably work
1 question, why not use a nice startup screen like alpha.nvim or dashboard? just curious. (I agree that oil.nvim is better but, i need to learn all the keys used for actions)
IDK if Oil has preview options or not, didn't use it for a long time. If it did then I'll dump miniFiles in no time. Also Telescope-File-Manager is nice with it's TJ vibes.
it does have both directory and file previews. but the file preview it also starts the lsp which lags. havent found a way to turn that off. it also has a floating mode in which the preview still works
I also like nvimtree but I feel like I'm slow with it. I switched to oil recently and I'm finding myself using fzf and spelunk more often. Hopefully overtime I'll actually build better habits. No clue though, it could all be in my head and I'm not saving any time lol. I find myself struggling to remember file names quickly which is the biggest thing holding me back from fzf.
Maybe this helps. If the filenames you struggle with are files you opened recently you can use telescopes recent files picker to get a list of them. Or if you remember at least the folder(s) you can fuzzy search for the folder first to list its contents and then add to the fuzzy search to select the file.
What is your proposed method of file navigation in neovim? I use telescope but it can become cumbersome to keep having to fuzzy find when I am switching between 3 files.
@@aviagarwal3011 fuzzy finding through open buffers might be a good solution. I am aware of the normal behaviour of control O and I - do you have them remapped to work with marks?
@moussaadem7933 dired was originally made in 1974, and was integrated into emacs in the 80s. I have no idea what pipe rename is but seems nascent compared to the OGs
you start with s mix of fuzzy finding and using a file manager (such as oil.nvim). the more familiar you are with the code, the more you rely on the fuzzy finder
YOU ARE SO WELCOME FOR BEING THERE LIL BRO
I like mini.files: it does EXCTLY what oil does (I mapped it to - too) PLUS it gives better visual context of where you’re at in new/unfamiliar projects by listing all the parent directories from the current file up to cwd / project root. It’s cool that both plugins have the same navigation and file operations patterns!
same, it is just a better version ...i for some reason have some lag when saving buffer with oil, in mini.files its always instant
Mini.files is a godsend. It behaves exactly as i thought oil would before i used it. For some reason i would some weird errors using 'caw', the hidden file ID would appear editable in the buffer, instead of it being just the filename
mini.files fan here too!
Yes, I love mini.files as well. The only time I prefer to use oil is when I want to have multiple windows open to different directories so I can easily move files around. Mini.files recently added bookmarks which helps, but sometimes it’s just better to have actual windows open to edit.
Does mini.files allow you to fill up the entire screen? I don''t like the default small popup and prefer to use the whole screen
File management tools and text editors are trying to solve the same problem: batch editing of text. the text just happens to be file paths in the case of file management.
so if you have a powerful text editor, you automatically have a powerful file manager
that's the genius insight oil.nvim and others relies on
Hi teej, please one of these days, I'd love if you talk about debugging.
+1
I think he already did
@@Temet79 just check again couldn't find it. If he did, then it's probably not in this series because I have been following.
It is not in this series but he definitely made a cool video about debugging on neovim.
@@user-ek8cd1gg3f I want him to make another. 🥹
I'm missing something, when you made video for floating terminal
He just posted it like 3 hours ago. I imagine he wanted the videos to go out in the opposite order.
@brodacious1313 I thought the same
i will NEVER give up my nvimtree. your blackmagic has no power here.
that's the nice thing about being able to make your own config!! :)
LETS GO TJ! always looking forward to this series every day 💪 these be my real christmas presents this year
Using ONLY fuzzy finder for navigation would be great, if only I didn't struggle to remember how named things...
This is incredible, how have I never heard of this before? Excellent video.
thanks :)
I'm currently using NeoTree since I switched to Neovim not too long ago, and having a file tree on the left is pretty standard. But a few months back, I saw Oil on the Typecraft channel, and it feels way more Vim-like. Every time I use NeoTree, I think, "It would be easier to edit as a buffer in Oil." Definitely planning to swap NeoTree with Oil when I update my config (hopefully in 2024, hehe).
I tried oil, and it's excellent, but I'll stick with mini.files, basically the same functionality, and it uses h-j-k-l to navigate OOTB. Also, I'm using more plugins from mini library, so it fits better IMO.
I always use telescope for quickly move between files. But when i have a huge deeply nested project. I still need a file tree to frist get a general idea of the project structure, then to create a file in a deeply nested folder. I use nvim-tree and it's working great for me.
ya, i'm mostly just jokin around. you should use what you like
I've never understood the aversion people have to a file tree. Are there good reasons I'm missing?
Personally I love Vinegar and usually have it in a popup window where I can do my filesystem modifications, then use fuzzy for navigating between existing files.
nice, been using it for a while now
Same
I will die on the hill that filetrees are the best way to view and navigate your file structure next to a live grep
Oiling my neo till I vim
....
Hate the trees, love the oil
Looks really good, I gonna swap neotree for this
Nice. I use a combination of yazi.nvim and mini.files. I don’t remember why I ditched Oil
mini.files and many other mini.nvim components are incredible.
Hey TJ,
Can you please move the bottom line of the NVIM up by 20-25px so, when I pause to read what you typed, TH-cam player won't bother?
Plus, could you please explain `:e %:b` + TAB (I guess). What is this and how I should search these in help?
hmm, i will see if I can move it up a bit or do something to make that a little easier to read.
the %:h is from filename-modifiers!
Really nice video!
The bitrate was horrible, tho, not sure if it's on your side or TH-cam's side (you can see your background going crazy).
Maybe you could upload in, so 4k we get better bitrate?
huh ya, that's really weird - i will see if I messed something up on my side. it looks like it happened to the last few videos, but I don't remember seeing it locally like that. Thanks for point it out
Am i the only one who doesn’t wanna move away from NvimTree😅
No, there's lots of ppl with bad opinions on the internet 🤣 🤣
@😬🤣🤣🤣
I switched back and forth a while, but it really clicked when I mapped oil to back space, so navigation is the same as Vimwiki. I use Vimwiki a lot and now navigating between files feels the same as navigating between links in my notes. It feels great to me.
nvimtree has two benefits: shift the code to the middle, and my colleagues can see where am I when I share my screen
skill issue
I am a huge fan of oil.nvim, we need more buffer first approaches. Wait... "Everything is a buffer"... this reminds me of something.
Hi, huge fan and new to neovim. I think it is kind of difficult to find an updated guide for a golang specific setup, or in general, what are best practices when setting up neovim for specific languages?
Streams full time on Twitch btw
very good point geek. good to see ya in the comments
I was wondering how do you setup multiple mini plugins ? I do not want to have all in the same files but I can’t find a solution for Lazy
i would put them in separate lua files like lua/config/mini/files.lua, and then require them indidividually in the setup with lazy that would probably work
What are these icons for the files? Looks really nice
they are from mini.icons I think, you have a few options in the setup for oil
3:10 wouldn't :e %:h do the same?
1 question, why not use a nice startup screen like alpha.nvim or dashboard? just curious. (I agree that oil.nvim is better but, i need to learn all the keys used for actions)
Goodbye netrw. This is how I always wanted things to work.
ya, netrw kept tricking me thinking i was back in oil.nvim throughout the series. finally had to make a video so i could update it haha
Oil seems awesome. I still use nvimtree, but it would be awesome if I can open oil on the side.
what are these --@module annotation things in the config, first time I see them
It imports type information from that module
it's like jsdoc for lua
can your emacs do that
I don't fukin think so
Apparently yes. Called dired or something from the 80's
@1Caja thanks for ruining the joke 😅
@@ami_rza82 Oh, sorry xd
LOL nice one
IDK if Oil has preview options or not, didn't use it for a long time. If it did then I'll dump miniFiles in no time. Also Telescope-File-Manager is nice with it's TJ vibes.
it does have both directory and file previews. but the file preview it also starts the lsp which lags. havent found a way to turn that off. it also has a floating mode in which the preview still works
Without using a file tree, what's your typical workflow for getting used to the directory structure of a larger code base?
Telescope..he built it.
I also like nvimtree but I feel like I'm slow with it. I switched to oil recently and I'm finding myself using fzf and spelunk more often. Hopefully overtime I'll actually build better habits. No clue though, it could all be in my head and I'm not saving any time lol.
I find myself struggling to remember file names quickly which is the biggest thing holding me back from fzf.
Maybe this helps. If the filenames you struggle with are files you opened recently you can use telescopes recent files picker to get a list of them. Or if you remember at least the folder(s) you can fuzzy search for the folder first to list its contents and then add to the fuzzy search to select the file.
wow, was literally thinking about something like emacs Dired
What is your proposed method of file navigation in neovim? I use telescope but it can become cumbersome to keep having to fuzzy find when I am switching between 3 files.
tabs or start using the buffer list
Harpoon
Like others said, you can fuzzy find through an open buffer list, or my preferred versionis to use ctrl O and ctrl I with marks for such a use case.
@@aviagarwal3011 fuzzy finding through open buffers might be a good solution. I am aware of the normal behaviour of control O and I - do you have them remapped to work with marks?
Harpoon plugin from Primeagen
This looks good, but what about a huge project? If you are new to it, a file tree is super helpful
i think fuzzy finding through the project is generally more useful, but you gotta use what makes the most sense to your own brain haha
Please make a video on debugging too
i'll see what i can do - not sure i'll be able to fit it into the series but i will try
Trigger warning: i use neotree and oil... 90% oil, 10% neotree. How you like them apples internet man.
so its dired for nvim?
yup!
Seems like the creator took the idea from dired (flle manager inside emacs). Very nice tho!
there are a lot of projects doing the same thing, there's pipe-rename for example.
I assume they just converged to the same solution
@moussaadem7933 dired was originally made in 1974, and was integrated into emacs in the 80s. I have no idea what pipe rename is but seems nascent compared to the OGs
That may be quite usefull 🤔
Big fan of oil. Epic
I use yazi
But thanks for the video
Oil.nvim is for those stills stuck on phossil phuels?!?
mini.files = oil.nvim BUT BETTER
mini.files is also good, I think basically all of the mini plugins are awesome
Is it better than neotree? 😢
Real
Booted my machine just to install it.
does fuzzy finder really work for people onboarding into a new company with a messy codebase?
you start with s mix of fuzzy finding and using a file manager (such as oil.nvim). the more familiar you are with the code, the more you rely on the fuzzy finder
File trees are good, actually
that's like, just ur opinion man!!!! haha
What's up with hoodies in videos? Has Prime really created a trend?
it's christmas time and i just bought this hoodie on sale, so i was feeling good
any telescope-file-browser users?
i also like telescope file browser, but i like that i can have oil in a split. i don't have super strong opinions about it though
nahh i would rather know what my dir tree looks like and i doubt you have to add so many file changes in your daily use.
I use windows explorer
wdired
ya, emacs has lots of good stuff
Always asking is always bad. Just sudo
ummmm 🤔 na
haha ok :)
Nobody gives a good cahoots where you put your files,OR how you get them there
I gives a good cahoots where you put your files
False
True
!false
NOT very cool!
Very cool
lmao tf is your problem 😂
hate to be that guy on the internet, but, objectively, you're wrong
NOT super cool either!