From 460f49b70f7099ada0fa73362e5cb40b6e19e95b Mon Sep 17 00:00:00 2001 From: Zoe Roux Date: Fri, 5 Apr 2024 17:17:27 +0200 Subject: [PATCH] Fix typos --- content/blogs/vim/index.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/blogs/vim/index.md b/content/blogs/vim/index.md index 5c0f475..997242d 100644 --- a/content/blogs/vim/index.md +++ b/content/blogs/vim/index.md @@ -56,11 +56,12 @@ Vim also has a great built-in way of learning its binding called `vimtutor` whic In a traditional editor, you are probably used to have a few dozen tabs/file open. When you start having too much of them, how do you find back your file? For me this was a huge pain point for a while, I tried every possible workflow: - Close a tab as soon as I finished with the file. This proved to be a bad method for me since I often jump around files a lot and find myself lost in my tabs before cleanup time. - - Use "Close other tabs" or "Close tabs on the right/left" features to simply close everything when there is too much. This was efficient after a small debug/coding time but I needed to use this during coding sessions a lot when writing bigger features. - - Embrace the "too much open" and use tabs on two lines, keep 3/4 most important/used tabs of the time pinned to find them quickly. I really liked having tabs pinned because it reduced the amount of time/mental strain needed to jump back to the most important files. Having items on two lines on the other hand was really bad, I needed twice as much time to look for the file I wanted to use before clicking on it. - - Abandon open tabs and rely on the file tree. Since I found it hard to search for the unorganized tabs, I thought maybe having them organised in a tree would help ; it was okay on small projects but when files were too nested or too many it was a nightmare to find them. + - Use "Close other tabs" or "Close tabs on the right/left" features to simply close everything when there is too much. This was efficient after a small debug/coding time, but I needed to use this during coding sessions a lot when writing bigger features. + - Embrace the "too much open" and use tabs on two lines, keep 3 or 4 most important/used tabs of the time pinned to find them quickly. I really liked having tabs pinned because it reduced the amount of time/mental strain needed to jump back to the most important files. Having items on two lines on the other hand was terrible, I needed twice as much time to look for the file I wanted to use before clicking on it. + - Abandon open tabs and rely on the file tree. Since I found it hard to search for the unorganized tabs, I thought maybe having them organized in a tree would help ; it was okay on small projects but when files were too nested or too many it was a nightmare to find them. ### How vim deals with this? +The first thing you will notice about tabs in vim is their absence. There is no such things as a tab per file on vim.