how would i go about transitioning from vs code to vim for website development? it's like going from being an ipad baby to using a 1980s terminal. any advice?things i am currently dependent on in code:>the file manager on the left-hand side>the terminal on the bottom>live preview>pushing to git and staging changes with the git extension>autocomplete and being able to preview hex codeseverything else is neither here nor there. this is entirely hobby-based and i do not work as a web developer btw.
>>109071718Use case for the file manager on the left-hand side?
>>109071718Learning to use a terminal multiplexer can solve a lot of these issues. I use tmux, personally. I'd recommend neovim over vim or vi as well.Also I'd recommend you just learn to use git in a terminal, it gives you more control and information than a mouse based GUI. It's not difficult, it's basically just going from riding a bike with training wheels to riding a bike with no training wheels.Idk about hex code color previews though. There might be a neovim plugin for it?There are neovim plugins that will do syntax checking and LSP (code highlighting) for you as well.
>>109072019when you're used to doing things that way it's just quicker to click tree item -> click tree item -> open file. you don't even have to know the exact directory off by heart. so no typing vs typing basically. i'm not opposed to typing and finding directories/files but it seems much slower...?
I've seen plugins for filemanager, but I've never seen the appeal.:term will bring up a terminal. There's some config you can do to specify size and location. I don't know what live preview means. There are also git plugins, but again, I don't use git. There are multiple autocomplete plugins as well.
>>109071718So fucking tired of this> vim> emacs> transitioningCan you fuck off? Can you not shill this garbage meme software that nobody uses?
>>109071718>file manager>terminal on bottom>live preview>autocomplete>hex codesUse a neovim distro. I chose AstroNvim which has all of those included.>pushing to git and staging changes with the git extensioninstall lazygit. Every distro integrates it well.>it's like going from being an ipad baby to using a 1980s terminalit's absolutely worth it. I was going to suggest Vim Adventures to learn it, but the pirated site I used is offline. I heard vimgolf is a good alternative.
>>109071718>being able to preview hex codesthere's a vim plugin for thathttps://github.com/ap/vim-css-color
>>109071718rtfm
>>109071718LazyVim
All you need is GNU Screen with few .screenrc presets, and your shitty (obsolete) choice of text editor. It's not that difficult to setup.If you can't handle being without "file manager" and "live previews" I don't think these 1970's text editors are for you anyway.
>>109073444>If you can't handle being without "file manager" and "live previews" I don't think these 1970's text editors are for you anyway.What a retarded thing to say considering Vim literally has a built in file viewer like VS Code. And it takes 2 lines of code to get the live previewer up.
>>109073481I don't understand this screenshot. Is that an ui for people with learning difficulties?
>>109073489Not my screenshot btw you can just say you didn't know Vim has had tree view since the 90s and move on.
>>109071718For website development, you are going to need a fair bit of shit to transition to vim or neovim. You have to treat it like a learning project you do on the side. Start simple. The more niggerlicious the software, the more complicated it is to not use VS COOOOOOODE
>>109071718With a few plugins you can make Vim function any way you want. You don't even need neovim or anything like that.
>>109071718>the terminal on the bottom>live preview>pushing to git and staging changes with the git extensionyou literally can open a terminal window as a separate program, right below vim and use git from it. You can also open a browser window and there's your live preview. You don't need to switch to Vim, but holy fuck man your points are retarded.Fuck, I don't understand kids these days, it's like they don't know world outside vscode actually exists and actually works.
>>109073974And it's not even an inconvenience, I'd kill myself if I had to use terminal, git and browser from within the text editor.
>>109072055It depends. Fuzzy finder is pretty good, you type a few letters and it find you just the right files or a few likely candidates, I use both NERTree and fzf finder in vim.
>>109071718Just use emacs. It can do everything you asked (sometimes out of the box without external plugins, for others like muh tree you will need a plugin. Ask an LLM for plugins to install), it's 100 times easier to configure compared to vim and can do everything vim can do (but not viceversa). Emacs has also one of the most powerful git clients ever (magit).You can use emacs both in a terminal and as a gui if you prefer.Also, look up tramp, fired and one of the fuzzy finding packages (I use the built in incomplete, but there are others. Again, ask an LLM)
>>109074827*dired instead of fired, I mistyped
youre asking how to go from vscode to vim and turn it back in to vscode, what youre looking for is the vim extensions for keybinds thats it
>>109072055if you think the way vs code operates is superior, why would you "transition" to vim? if you don't think the value proposition of vim/nvim/emacs has any value, why bother?
>>109072085I still genuinely don't see the utility in terminal buffers in (Neo)vim. They screw with colors for no reason and needing to enter input mode fucks with what I think of when I see a shell prompt.I think they're only there because people don't know how to use ^X^E or a terminal multiplexer, the latter of which comes with its own set of problems. It's great to be able to yank scrollback into a file, sure. But there are aspects of the overall command line workflow that have been largely unchanged since early shells and physical terminals which I think are restricting innovation (a statement which sounds incredibly gay now that I type it)t. does everything in nvim and tmux if I can help it
>>109071718>how would i go about transitioninghttps://vimuser.org/
>>109071718by using vim more. that's literally it. that's how you do anything. just do it more.the real question is why? what do you think you're getting out of vim?
>>109071718I've been trying to do this lately. My biggest issue is a lack of "jump to definition". Its probably built-in or configurable somehow, but I haven't figured it out yetUse neovim instead of vim. Vim is good to know the absolute basics so you don't shoot yourself in the foot somehow, but for a daily driver you should be on neovim
>>109078634neovim is for trannies that want to use vim but are too lazy to actually
>>109071718>>the file manager on the left-hand side I would always just map F7 to netrw (:Ex), but I think nerdtree is a plugin for just that.>>the terminal on the bottomYou don't need a terminal multiplexer for this. Modern vim pretty much is a terminal multiplexer. Just do:vs:term
>>109071718>using vibecoded slop
>>109071718>>the file manager on the left-hand sidethere are plugins for that>>the terminal on the bottom? just use another window or a tab>>live preview??>>pushing to git and staging changes with the git extensionwhat's wrong with the git command? at work where I'm forced to use an IDE, I just use git in the console because it's faster to do stash/checkout juggling. also I can use custom aliases and scripts>>autocompleteworks great>being able to preview hex codesmy terminal emulator (Konsole) supports that
