L.A. based web developer slowly parsing through Stack Overflow. If you like hot web dev tips or stories about being a freelancer, check out my newsletter: https://codenutt.substack.com/p/coming-soon
I've not used MacVim as I was using Neovim with Linux before getting an MBP. But I like being in one terminal when I'm working (All the applications I used daily is usually on full screen (small screen)). It's easier for me to focus on one thing that way (I was using a tiling window manager on Linux). I close and reopen Neovim multiple times throughout the day. Let's say I need to change branch to fix a bug. I suspend the current vim session (ctrl-z), switch to the branch (gco <new-branch>, open a new neovim instance (nvim .), fix the bug, close the recent instance of neovim (:qa), go back to the branch I was (gco <old-branch>) and resume my work where I left it (fg). I don't say you can't do the same process using MacVim, but I don't like switching applications when I'm working.
L.A. based web developer slowly parsing through Stack Overflow. If you like hot web dev tips or stories about being a freelancer, check out my newsletter: https://codenutt.substack.com/p/coming-soon
I enjoy keeping up on all of the changes in technology, especially on the web front. My passion is for developing web-based applications and backend services to help businesses get more done.
@tnolte
. I tried it before, but it felt a little strange. I'm already in a terminal so I just used that instead. I can't run longstanding command in it as I close and reopen Neovim a lot (mainly for reloading file (have to make a script for that or find one). I don't copy messages from the terminal and pressing suspend, command or alias, resume is more sastifying than new tab, term full-command. Or maybe I should try it again....
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
<3golang, tdd, cloud, distributed systems paradigms, clean arch, ddd, but also probabilistic learning algorithmic and analytic, some svelte, some vuejs, very few react, and angular when needed
Education
Bachelor's in CS at Sorbonne Université (Paris Jussieu)
resume is more sastifying than new tab, term full-command. Or maybe I should try it again....
I feeled the same until I've found vim-wintabs that had changed my way of dealing with tabs and buffers and helped me to reconsider tabs as helpful.
I only had to add some extra mappings to change tabs following the plugins' <C-[HL]> philosophy with <C-T>[hl] for :tabnext and :tabp respectively.
Also, one last thing to consider although but I'm used to it now, is the <C-\><C-N> to escape the terminal (but also scrolling with the mouse or clicking outside the terminal buffer does it).
Finally, thank you for sharing your experience that syntheticly.
Can't wait for the next year or two with all the communities work...
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
L.A. based web developer slowly parsing through Stack Overflow. If you like hot web dev tips or stories about being a freelancer, check out my newsletter: https://codenutt.substack.com/p/coming-soon
Pretty similar to my setup. I use MacVim though, not Neovim. What's your argument of Neovim over that?
Side note: CoC is amazing!
I've not used MacVim as I was using Neovim with Linux before getting an MBP. But I like being in one terminal when I'm working (All the applications I used daily is usually on full screen (small screen)). It's easier for me to focus on one thing that way (I was using a tiling window manager on Linux). I close and reopen Neovim multiple times throughout the day. Let's say I need to change branch to fix a bug. I suspend the current vim session (
ctrl-z), switch to the branch (gco <new-branch>, open a new neovim instance (nvim .), fix the bug, close the recent instance of neovim (:qa), go back to the branch I was (gco <old-branch>) and resume my work where I left it (fg). I don't say you can't do the same process using MacVim, but I don't like switching applications when I'm working.Makes sense. Thanks for the info!
You can also use
gco -to go back to the previous branch just like you would usecd -:)Your workflow sounds like a perfect use of the Neovim split window(neovim.io/doc/user/windows.html) and built-in terminal (neovim.io/doc/user/nvim_terminal_e...) features, instead of all of that suspending.
@tnolte . I tried it before, but it felt a little strange. I'm already in a terminal so I just used that instead. I can't run longstanding command in it as I close and reopen Neovim a lot (mainly for reloading file (have to make a script for that or find one). I don't copy messages from the terminal and pressing
suspend,command or alias,resumeis more sastifying thannew tab,term full-command. Or maybe I should try it again....Worth noting is that everything people are saying you can do better in neovim here, you can do in vim.
@skydevht
I feeled the same until I've found vim-wintabs that had changed my way of dealing with tabs and buffers and helped me to reconsider tabs as helpful.
I only had to add some extra mappings to change tabs following the plugins'
<C-[HL]>philosophy with<C-T>[hl]for:tabnextand:tabprespectively.Also, one last thing to consider although but I'm used to it now, is the
<C-\><C-N>to escape the terminal (but also scrolling with the mouse or clicking outside the terminal buffer does it).Finally, thank you for sharing your experience that syntheticly.
Can't wait for the next year or two with all the communities work...
Neovim works on other systems? I mean, not as many as Vim, but more than MacVim :)
Very true lol good point.
Never tried Windows, but it works on Mac and Linux perfectly